• Basically the title. When Redis Object Cache is enabled and running, editing events seems to follow this loop:

    1. Published event: Clicking “Update” changes the published event to a Draft.
    2. Draft event. Clicking “Publish” publishes the event.
    3. Back to 1 and repeat, alternating between published (button: update) and draft (button: publish)

    If I disable Redis Object Cache, then it seems to follow the expected route of simply updating the already published post, and keeping its published status. I tried clicking “update” 10 times in a row and it always remained published, and re-enabling Redis immediately ran into the original problem loop again.

    Any help?

Viewing 1 replies (of 1 total)
  • Thread Starter Kipex

    (@kipex)

    As we tried to investigate the issue further, it seems we found a bug you should probably fix.

    When event time is overlapping with other events, it’s set as draft, but when Redis is on, the “other events” would also include the current one, and when comparing, it doesn’t rule out that. So it uses current event to compare with current event, and of course it overlaps.

    wp-content/plugins/events-manager/classes/timeslots/timeranges.php
    The function “has_overlapping_timeranges()”, when checking time overlaps, it doesn’t rule out if $Timerange and $Timerange_2 are actually the same event.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.