Franky

There is no possibility for seating arrangements in EME for now. I started working on that in the past but since there was not enough demand for it, I abandoned it. This would require substantial amount of work: allowing people to design seating plan, people book on such a plan, take concurrent bookings into account etc …

Try resetting your WordPress permalink settings. For that, go in your wp settings, section permalinks. In there, just press save.

Also, it is against the EME recommendation to use the calendar directly via the special events page. You should create a regular page and put the calendar shortcode in it.

Then something else is interfering with the wordpress cron settings. EME only changes the cron on 2 occasions: when (de)activating EME or when saving the EME options concerning queueing.

I’m still baffled by this. EME calls eme_plan_queue_mails at the end of plugin update, which takes care of all that. I really don’t understand why in your case the schedule keeps disappearing. I even added code in case no schedule is set but queueing activated, to set it to “hourly” then. I’ll go over all that again … but feel free to evaluate that code too and challenge me on how I do it 🙂
What I do know is that the wordpress cron system is inherently unreliable (due to the way they store cron entries: all in 1 option value, meaning several accesses to the same option can override changes made by another). But that doesn’t help you of course …

Can it be a caching plugin is causing issues with cron?

You can use that placeholder in the list of events, then you can show an ical link per event. There’s also the [eme_ical_link] shortcode.

It seems 2 plugins use the same Mollie libs, so only one can win. In your case this seems to be woocommerce, but it seems not the whole Mollie class is included.
This is the code from EME:

   if (!class_exists('Mollie\Api\MollieApiClient')) {
           require_once 'payment_gateways/Mollie/2.39.0/vendor/autoload.php';
   }
   $mollie = new \Mollie\Api\MollieApiClient();

meaning that only if the class “Mollie\Api\MollieApiClient” doesn’t already exist, EME tries to load its own. Since woocommerce seems to win (bsed on your error), EME won’t create the class again and thus uses the one from woocommerce. You can see in EME that it provides the needed files, in payment_gateways/Mollie/2.39.0/vendor/composer/ca-bundle. But apparently the woocommerce implementation does not but still refers to it. I don’t have woocommerce, so you should probably talk to them (or the woocommerce mollie plugin) about this issue … I checked that plugin and the required cabundle files are not provided, so mayb there’s a reason for that …

The attendees tag is much more limited, so if you replace that with [eme_attendees id=#_EVENTID] , you have the full eme_attendees shortcode with all possible options.