Support » Plugin: Events Manager » Adding tag to a published recurring event

Viewing 6 replies - 1 through 6 (of 6 total)
  • angelo_nwl


    NetWebLogic Support

    I tried this one and seems to be working fine, can I know what is your current EM version please? and/or just to narrow down the problem can you to temporarily:

    – deactivating all other plugins to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s).

    – switching to the default theme to rule out any theme-specific problems

    I deactivated one of the plugins (one that I wrote) and fixed that problem. Now I am seeing a different annoying behavior, however this one is fairly well documented.

    When I add a tag, it drops the booking. This is because the booking is only for the first event.

    It doesn’t seem like it should be so hard to fix. Why not identify the fields that changed when a recurring event is published and only change those fields before propagating to the child events?

    Hmmm … that does seem like kind of a pain from a coding perspective. How about checking only the bookings fields, since they are more typically different in recurring events?


    Can you be more specific about what you mean by “When I add a tag, it drops the booking.” please?


    As I said earlier in this thread, I am asking about how changes to recurring events propagate to (can be observed in) the child events. I observed that most changes propagate with no issue, but when I add a tag to the recurring event, it does not appear in the child events.

    So on advice of angelo_NWL I deactivated the plugins and I found that adding a tag now propagates to the child events, but the booking that I created in one of the child events got dropped (is no longer there).

    As I said above, it seems like this is something that can be improved, for example, by propagating only fields that change. In other words, if I change a tag field in a recurring event, then only the tag field of the child should change.


    If you make changes to a recurring event, it deletes and republishes the sequence of events and all bookings are lost because the events are new. That sounds like what’s happened here.

    You should see a warning notice about that before making changes to recurring events.

    To make edits to recurring events while preserving bookings and other settings for individual events, you need to detach those events from the sequence on the Events > Events page.

    All I am saying is that there is room for improvement here.
    The current algorithm is inelegant, counter-intuitive and frustrating.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Adding tag to a published recurring event’ is closed to new replies.