Jack Arturo

Hi all, this was fixed in yesterday’s 3.47.11.1 update. Apologies again for the inconvenience and thanks for your patience.

Edit: still something not right— working on it now.

Edit: All good, it was just a caching issue on a couple of our test sites 🫡

• This reply was modified 3 weeks, 6 days ago by Jack Arturo.
• This reply was modified 3 weeks, 6 days ago by Jack Arturo.

Thanks @li-an !

It’s a good point. EXIF warnings like that are pretty common and don’t usually indicate a problem.

We’ll add some extra logic to the next update to filter out “noise” notifications like that.

In the meantime you can suppress this error notification on your site using the fen_ignore_error filter. Either add this code to your theme’s functions.php, or with a snippet manager:

add_filter( 'fen_ignore_error', function( $ignore, $error ) {
	if ( empty( $error['type'] ) || empty( $error['message'] ) ) {
		return $ignore;
	}

	// Ignore common noisy EXIF warning from malformed APP1 metadata.
	if (
		E_WARNING === (int) $error['type'] &&
		false !== strpos( $error['message'], 'exif_read_data(' ) &&
		false !== strpos( $error['message'], 'Incorrect APP1 Exif Identifier Code' )
	) {
		return true;
	}

	return $ignore;
}, 10, 2 );

More info and examples are at https://fatalerrornotify.com/documentation/developer/hooks-and-filters/

Thank you so much for the kind words @hhenrytac !! 😊🧡

Hey @joshkern ,

Yup that’s the idea 🙂

The function doesn’t exist, so it triggers a fatal error. This should send a notification. Did the notification arrive? If so then everything is working.

Jack

Oh wow, 8.4 already 😳

Thanks @jeremyjsimmons , fixed for thw next release ✅

We do have an update planned that adds a couple of small new features, but we don’t want to fill this up with a bunch of extra clutter, integrations, etc.

It’s designed to be a really simple, fast, no-fuss plugin.

It still works fine. We use it every day, on every site we own.

It works with the latest versions of WordPress. But yes, we will have an update out sometime within the next month.

Hey @bernardberry646 ,

This should have been fixed in v3.45.8 at the end of April. Are you running the latest version, 3.46.3.1? If so can you let me know your WordPress version? We will see if we can reproduce it. So far we haven’t had any reports of this problem since we released the fix.

Thanks
Jack

Hey Natascha,

It’s not possible to change the post’s actual status (like “private”) when a tag is deleted or added. However you can control whether or not users can access a post based on their tags. We have a guide on that here https://wpfusion.com/documentation/getting-started/access-control/

Let me know if that answers your question 🙂

Jack