Franky

The problem was in the latest version of EME that did some sanitizing in an incorrect manner, a new version has been released to rectify this. Also a new version of EMEFS has been released to provide more error feedback in case event validation fails.

Captcha is only mandatory if you indicated it to be used.
Concerning a demo: I’m not allowed to ask for admin rights (and I can understand that). You can provide me with the site url so I can subscribe (or you do that) and you can give me the needed minimal rights to create an event temporary.

“sometimes” is a weird thing in ict 🙂 Can you reproduce this reliable?

The move of a booking only does 1 thing and that is changing the event id related to the booking. So if anything else gets emptied, it is maybe because the target event doesn’t have the same definition for its rsvp fields. So compare the RSVP definition for the 2 events.
If all is the same, please provide a simplistic reproduction scenario (custom field definition etc) so I can try it too.

Well, currently it is not possible to simplify this, but I liked the question so I changed the code so “incsv” can do it:
https://plugins.trac.wordpress.org/changeset/2515924/

If implementing the code (and provided I didn’t make any mistake), this should then work

[eme_if tag='#ESC_CATEGORIES' incsv='Category-A,Category-B']
Do stuff
[/eme_if]

Without a page example and based on your info, I can only say that the code is correct (as google indicates too) and you experience some kind of caching.
Edit: but to be sure I didn’t miss anything: I’ll try it out here too on some test events (maybe some escaping is happening …).

• This reply was modified 5 years, 1 month ago by Franky.

Ok, I’ve dived a bit in my own code and you can just use placeholders there, resulting in easier coding. Also the performer-part should be an array (according to json-ld), so for example:

function eme_3cs_google_headers($current_headers, $event) {
        $performer=array();
        $performer["@type"]="Person";
        $performer["name"]="#_FIELD{performer}";
        $current_headers["performer"]=$performer;
	$current_headers['eventStatus']="#_FIELD{eventState}";
	return $current_headers;
}
add_filter('eme_extra_event_headers_json_filter','eme_3cs_google_headers', 10, 2);

Because performer can be so many things (group, person, …) it didn’t match the notion of an event where e.g. you have different groups performing (and EME isn’t currently cut out for asking that info). Also json-ld value for event status differs according to the doc you’re consulting (e.g. you find Rescheduled and EventRescheduled, while google examples say ” https://schema.org/EventReScheduled “, see https://developers.google.com/search/docs/data-types/event). Since it is not always clear I’m currently not adding those 2 (which are not really required anyway).
I could include a default performer (and point it to the contact person), but that’s not really the truth, and for school classes that’s not really true either. Also I find no real example on how to add multiple performers or groups, so it is not an easy one.

• This reply was modified 5 years, 1 month ago by Franky.