Franky

What is the complete definition of your custom field?

no reply, marking as resolved

The way I do it: create 1 event for the first day with all rsvp etc …, then create recurrent events on specific dates and link the RSVP part to the first event.

Ok, found the problem. This should fix it:
https://plugins.trac.wordpress.org/changeset/2458458/events-made-easy/trunk

The bookings have nothing to do with the booking form, but with the event they registered for.
On another page, either use [eme_bookings] with the event id (see https://www.e-dynamics.be/wordpress/category/documentation/6-shortcodes/eme_bookings/ ), or use the same shortcode for events as you use on your other page, but use as event template something that doesn’t include the booking form (the #_ADDBOOKINGFORM placeholder).

You should only see that as a possible issue during plugin update, but I found the source of the problem: random_id is a tinytext and adding an index on those is not supported without adding a key length to the index. I’ve fixed it in trunk now (changed tinytext to varchar(50), and then the index creation works fine) so on the next upgrade of the plugin the index will get created.

There is also the possibility to use ical to fetch events, see the shortcode eme_ical_link: https://www.e-dynamics.be/wordpress/eme_ical_link/

If you use the option to create a wp user when someone becomes a member, then you can use the action hook eme_insert_member_action to do whatever you want afterwards. Use the function eme_get_person($member[‘person_id’]) to get the eme person info in your created function and that will give you the wp id too. Then you can do whatever you want with that id.
Now, there are some eme shortcodes that also allow you to hide parts of a page based on membership, see the doc on [eme_if] and the _IS_USER_MEMBER_OF placeholder: https://www.e-dynamics.be/wordpress/conditional-tags/