Schedule conflict notification caching?

  • Resolved fendove

    (@fendove)


    5 years, 2 months ago

    Hiya!

    I’ve been playing with the plugin and came across an odd issue.

    I had 2 shows that conflicted causing the administration notice that “will persist until the conflicts are cleared”. I cleared the conflict by changing the shift schedule. But the notice didn’t clear. I then completely deleted one of the shows but the notice did not clear.

    I’m hoping to clear this issue up before I recommend the plugin to my clients.

    Thanks!

    • This topic was modified 5 years, 2 months ago by fendove.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Tony Hayes

    (@majick)

    5 years, 2 months ago

    @fendove The conflict checking runs on the cached schedule transient. So clearing the schedule transient by either checking the “Clear Transients” option on the plugin settings page (this is persistent), or adding ?rs-debug=1 one-time to any URL, should also reset the shift check data and thus also clear the admin notice.

    There are two cases you mention, the first where you have changed a shift and the second where you have deleted a Show.

    In the first case, normally changing a shift would clear the notice as the schedule is changed, so if it is possible to reproduce these conditions somehow by providing more details on exactly what happened, then we can look at this further.

    As for the second, this does highlight some missing conditions in the plugin, to clear the schedule when a Show is deleted (or trashed or set to another post status that Publish) so I have added a new Github issue for this:
    https://github.com/netmix/radio-station/issues/320

    Plugin Contributor Tony Hayes

    (@majick)

    5 years, 1 month ago

    @fendove Hopefully this has resolved the issue for you, I’m going to close this as resolved here, if there are any further related problems, you can add them to the Github issue.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Schedule conflict notification caching?’ is closed to new replies.