Support

June 12, 2020 at 10:28 am

Hi there,

Just to note, Event Espresso already outputs schema data for your events:

https://github.com/eventespresso/event-espresso-core/blob/master/core/templates/json_linked_data_for_event.template.php

Can you send me a copy of Schema Pro I can install locally so I can take a look? I’m fairly certain most of the fields that plugin will need won’t be available without custom development as EE data isn’t stored within post meta, a lot of it is in custom tables.

July 1, 2020 at 1:27 pm

Hi Mads,

So I spent some time comparing Schema Pro’s output to what Event Espresso outputs and whilst Schema Pro looks great and does some awesome stuff it doesn’t really output anything different from what Event Espresso does already for the events so won’t help with what you are trying to do.

After checking out Schema Pro and seeing very little differences with our output I found the site you linked to so I could check out what they are doing to show those details and it turns out its a bit a grey area. Google recommends that each ‘instance’ of an event is separate and has its own URL which is a little odd but that’s what they have.

With the site in question it’s simply outputting multiple event schema’s for the same event, changing nothing but the date of that event, that’s not something Google document (in fact as mentioned that state that each event schema should use a unique URL) and so not something we’ve implemented within EE.

This isn’t something that can be done easily within EE, you’ll need to load your own template file for the structure data and loop over each datetime on the event outputting the same data but changing the dates for that datetime.

There are some details on how you can unhook the current template here:

https://eventespresso.com/topic/ldjson-customization/#post-302211