Franky

Maybe another reason: EMEFS uses the openstreetmap api (and thus loads some javascript files to do so). There might be an issue (I need to test this) if you have disabled the map-option in EMEFS. Can you tell me the value of that option?

You don’t need to backup your entire site but only the database (which is recommended by WordPress before any update).
The EME update itself should be just fine.

All 3 choices are viable to me (of course it depends on what you want, but I’d say a “View all Events” is more interesting). But indeed, you need to put the link on it yourself. Putting it in template (to be used as single event format template that you can reuse in all events) seems the best way to me.

Thanks, I updated the faq. Maybe it would work like this too?

add_filter( 'the_seo_framework_query_supports_seo', function( $supported ) {
	if (eme_is_single_event_page() || eme_is_single_location_page()) {
			$supported = false;
	}
	return $supported;
} );

But I’ll leave that up to you for testing 🙂

Your theme is causing the layout to be rendered before the full page is loaded:

Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content.

Try using the default theme first.

That is a good question. I’ll see how wordpress handles this and how to get a better take on it (maybe some sync operation between the linked persons and their wp counterparts).

Either use the shortcode eme_events to show all events with optional use of the paging option, or use the calendar (small in widget or big version). See the documentation:
https://www.e-dynamics.be/wordpress/category/documentation/6-shortcodes/eme_events/
When in an event, there’s no “previous” or “next” event on its own, but even then you can show a list of e.g. all events in the same location (by using the eme_events shortcode in the single event format with the location_id param as explained in the documentation).

EME overrides that description per event with its own meta-tag. So maybe you should try to make sure the SEO framework doesn’t interfere there …