Draft events are not accessible

[Robert Trevellyan]

I’ve read through an earlier thread related to this (https://theeventscalendar.com/support/forums/topic/draft-events-not-accessible-after-upgrade/#post-56899).

My case is different, though I expect it’s caused by the same bug. The only reason I have any draft events is that I began entering information for an event, then WordPress auto-saved it, then I navigated away from the page because I decided not to publish the event. In other words, there is no Community or third party add-on involved in creating the draft event, it’s just a WordPress auto-save.

I’ve checked the boxes below for testing with other plugins deactivated and using the default theme because I’ve tested this behavior on a sandbox site with nothing else installed. You’ll be able to reproduce it immediately if you do the same. The client existing site is not yet live, but I can give you a URL and Subscriber login if you need to view it.

In what may be a related issue, changing the date of the first instance of a recurring event to be earlier, then deleting that event, results in the number of published events being off by one (too high). There is no way to access this extra event either.

[Barry]

Hi trevellyan – I believe I can indeed replicate this but I just want to be absolutely clear we’re experiencing the same thing:

* You are creating a new event but are not saving it as a draft or publishing it, etc
* A WP autosave is taking place
* When you navigate away and return to the events admin page, you see an increased count for draft posts (in the subsubsub menu, where it reads something like All (501) | Published (450) | Drafts (9) … )
* And when you try to view those drafts the autosaves are not included

Does that sound accurate?

[Robert Trevellyan]

Yes, that sounds correct.

[Barry]

OK, that’s definitely a bit annoying. I’ll get that reported and we’ll hopefully see a fix in the next maintenance release.

Thanks for reporting 🙂

[Kelly]

Hi, trevellyan. This is just a note to let you know that we didn’t get a chance to look at your issue for our maintenance release this time around.

While it’s possible we may have inadvertently fixed it in addressing another issue and welcome your feedback to confirm or deny this once you’ve updated, we want to set your expectations.

Rest assured getting this resolved is still a priority for us. We look forward to addressing this as soon as we’ve got bandwidth/resources to allow it.

Thanks for being part of the TEC community!

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Author]

Posts