Steve,
I’ve spotted this, too. Seems like a bug to me. I have found a workaround, if your problem is urgent, but otherwise I’d wait for a fix.
The workaround is to rename the “Pending Review” status to “Pending”. It seems that the slug has been shortened and the mismatch causes posts to disappear.
Hope this helps!
Joshua.
I’ve just realised that if you change it back to “Pending Review” again, the problem does not come back.
Oops. Spoke too soon. Yes it does.
Nice catch spotting this bug. In v0.7, we allow users to delete the “Pending Review” status. Unfortunately, if you use the “Submit for Review” button, it will still save the post with the “Pending Review” status. In core, this “Pending Review” status has the slug of “pending”, so you can regain access to the posts by recreating a “Pending” status.
I’ll think on what might be a better solution. I’m also happy to hear any ideas you guys have.
Thanks for the workaround guys, that’s worked perfectly! It’s not on a production site, but even if it was that would do the trick as long as it needs to.
I can think of two ways it could work:
- Have the slugs independent of the names of the statuses, just like the categories work. So if you set up a status and then change the name of it, the slug doesn’t change unless you manually change it. That way you could have the plugin recognise that “pending” is the default slug of “Pending Review”.
- Keep everything working how it is and just code in an exception for the pending slug. Part of me thinks that would be preferable, to keep the UI as simple as possible, but on the other hand, are there any other circumstances where something similar could crop up?
