Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support angelo_nwl

    (@angelo_nwl)

    Thread Starter bluerobot

    (@bluerobot)

    No difference – still outputs the conditional control text “{has_att_foo_&_foo}”.

    Plugin Support angelo_nwl

    (@angelo_nwl)

    can I know where did you pasted it? and can you share the actual code or conditional placeholder you used? also, the above snippet might not work out of the box sometimes however it should be something similar.

    Thread Starter bluerobot

    (@bluerobot)

    Using the shortcodes, actions and filters plugin. My conditional code for another custom #_ATT is working as expected. Here’s the code:

    // #_ATT{More Information & Registration Link}
    case ‘has_att_more_information_&_registration’:
    if (is_array($EM_Event->event_attributes) && !empty($EM_Event->event_attributes[‘More Information & Registration Link’]))
    $replacement = preg_replace(‘/\{\/?has_att_more_information_&_registration}/’, ”, $match);
    else
    $replacement = ”;
    break;

    I think it’s got something to do with the ampersand in the preg_replace().

    It’s highly likely. Have you tried replacing that with and?

    Thread Starter bluerobot

    (@bluerobot)

    ‘and’ works fine – the first thing I tried. Unfortunately I have 100 events that use the #_ATT with the ampersand. I don’t think they’ll get updated when I change my #_ATT from ‘&’ to ‘and’ – but I have to ask.

    I should ask what happens when you change an #_ATT. I expect that the #_ATT will stay with the event as they were originally created?

    Plugin Support angelo_nwl

    (@angelo_nwl)

    hmm, let me try and confirm if ampersand causes this.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Ampersand in event attribute’ is closed to new replies.