markburton52

Thank you. I looked at the documentation and am not sure what to do.

The data I have is in this format:
Monday 11 May, Afternoon, Monday 11 May, Evening, Friday 15 May, Morning, Friday 15 May, Afternoon, Friday 15 May, Evening, Saturday 16 May, Morning, Saturday 16 May, Afternoon, Saturday 16 May, Evening, Sunday 17 May, Morning, Sunday 17 May, Afternoon, Sunday 17 May, Evening
It needs to be in this format to be uploaded and then populate the database:
“a:11:{i:0;s:24:”Monday 11 May, Afternoon”;i:1;s:22:”Monday 11 May, Evening”;i:2;s:22:”Friday 15 May, Morning”;i:3;s:24:”Friday 15 May, Afternoon”;i:4;s:22:”Friday 15 May, Evening”;i:5;s:24:”Saturday 16 May, Morning”;i:6;s:26:”Saturday 16 May, Afternoon”;i:7;s:24:”Saturday 16 May, Evening”;i:8;s:22:”Sunday 17 May, Morning”;i:9;s:24:”Sunday 17 May, Afternoon”;i:10;s:22:”Sunday 17 May, Evening”;}”

Is there away to make that conversion? I would do it via spreadsheet formulae but don’t understand how the encoding works.
Thanks for any help / clues.

• This reply was modified 3 months ago by markburton52.

Thank you for this. I’ve tried separating each date slot in the list with :: but it is only accepting the last term. So for Saturday 9 May, Morning ::Saturday 9 May, Afternoon ::Saturday 9 May, Evening ::Sunday 10 May, Morning ::Sunday 10 May, Afternoon ::Sunday 10 May, Evening it only accepts ‘Sunday 10 May, Evening’.
The other possibility is that it needs serialised data (that seems to be what is in the database for this field), but I don’t know if there is a way to convert a list like the above into the appropriate serialised data.

Many thanks Jon, I didn’t think to look there – these settings are a bit scattered around the settings area – I was looking in formats and then trying to use the search parameters.

Too late for this year’s events but it will improve things a lot next year!

Just to confirm: the problem wasn’t with the shortcode but with the uploaded events. Both old and new version work: I actually prefer the way events are formatted in the original version.

Thanks – very helpful. I’ve got it working now. Note that there should be no ‘-has’ in the expression for the null case:

{has_att_link_to_book}
<a href="#_ATT{link to book}">link to book</a>
{/has_att_link_to_book}
{no_att_link_to_book}
no booking needed
{/no_att_link_to_book}

Thanks – not your mistake but mine, but I’m getting this output on the front page.

{has_att_link to book} link to book {/has_att_link to book} {no_has_att_link to book} no booking needed {/no_has_att_link to book}

The template formatting is identical to that used for the previous location one (with the obvious changes).

@joneiseman I’ve tried to clone and edit your code to do similar with a link in the event posts:

add_filter('em_event_output_show_condition', function($show_condition, $condition, $key, $EM_Event) {
    if ($condition == "has_link_to_book" && !empty($event->event_attributes['link to book'])) {
        return true;
    }
    else if ($condition == "no_has_link_to_book" && empty($event->event_attributes['link to book'])) {
        return true;
    }
    return $show_condition;
}, 10, 4);

and in the single event page template

{has_att_link to book}
		<a href="#_ATT{link to book}">link to book</a>
		{/has_att_link to book}
		{no_has_att_link to book}
		no booking needed
		{/no_has_att_link to book}

But the link isn’t coming through to the front end. Can you spot an error in the code?

(We aren’t using the inbuilt EM booking functionality but rather links to external sites for that.)

Thanks