I’ve not seen any reports of this and would assume it’s not a bug in a recent WP release. Unfortunately, looking at the logs, etc, is exactly what I’d suggest you do. Otherwise, you can try the standard things – change theme, deactivate plugins and try it, re-install a clean copy of WP, etc.
@dartiss, thank you, I did just that and I have managed to resolve it (hopefully) but since it was happening and I did a lot of search for it, it did come up quite a bit that starting a few years back they did introduce issues that were patched but reappared and seems to have eventually resolved, that’s why I asked did it somehow creep back in. Wasn’t saying that was the case.
For the time being, my research, which I would have posted back but the forum here takes days to make the posts visible for some reason and you can’t edit after posting until such time, which is ridiculous for a support site, but oh well; I digress. I have already asked about it on the forum support itself but haven’t heard anything.
It seems that the update from iThemes security (which you can find the post in my history) that broke things and was later patched twice in a row to bring it back had more than just broken the site for me which I had already corrected manually and later patches didn’t cause more issues.
It seems that somehow they orphaned a bunch of those tedious and redundant and constantly running jobs on WP, which is fine, not saying anything bad about that, I like it, but none the less they were foobared by the update and they were apparently holding up things or better yet mucking things up with inconsistency. Somehow a few would get by but most of them were held up. So I just cleared the jobs queue, reset it back to normal and so far it has not missed in two days, so I will keep watching it.
I am going to mark it tentatively resolved, but if it should change, I will notify.
Ok, I have found out WHY its happening but not really “WHY” its happening or how its happening.
I have found if I schedule a post and make the unfortunate attempt of clicking on “Preview Post”, it will never publish and will miss its schedule.
However, any post that I DO NOT click to preview after scheduled, will go through just fine.
So my question here is, why? How is this previewing stalling the process? I will admit I am at a loss as to the cause here. Now that I know under what circumstances its happening, I would like to find out why and have it fixed.
Thoughts? WP developers?
Same issue here. All 4 of my scheduls were missed on a high profile site. They were reviewed as well. I have not tried without reviewing them, this is not possible in our org.
This is a serious issue for a lot of people.
For me its not an option to go without previewing also so I figured I share more experience since then (aka anecdotal evidence).
I have found this so far based on (38 scheduled posts – control group) and without previewing before, during or after the schedule, there were 3 schedules missed (7.9%). The mere fact that it still happens suggests something broader but just looking at numbers it seems its at least a great part of it.
With 25 posts and previewing before, during but NOT after scheduling, resulted in 11 schedules being missed (44%). As you can see previewing has greatly increased the occurrence of the misses.
Finally with 19 scheduled posts (yes smaller sample because that’s all I could fit over this period – remember I am splitting them up into 3 distinct groups but also trying to keep them together to make sure they are subject to as much similar conditions as possible) being previewed before schedule and AFTER scheduled, 18 were missed (94.7%) – that’s almost all of them.
Beyond knowing it happens, I have not been able to figure out exactly WHAT is causing all this, hell the preview might be a symptom, not a cause but right now that’s all I got.
Same issue here, clicking preview after scheduling results in a ‘missed’.
I wasn’t sure how to proceed with this so raised it with the support volunteers and admins on Slack.
Basically, it’s known that WordPress doesn’t handle these very well. It’s already on Trac and can be found here… https://core.trac.wordpress.org/ticket/17888#comment:4. However, it is closed so it may be worth re-opening and adding in your own thoughts on this to see if it can be looked at again.
Any updates here? I discovered the issue shortly after updating from 4.4.4 last week.
@dartiss, you are right, I saw the trac entry and a bunch of other ones that were closed but they all date back quite a while, from what I recall. So I assumed it was an issue that was eventually addressed.
But seeing it happen now with certain regularity and only since the last couple of updates, I felt that maybe somehow they introduced a regression without realizing it or something that was dormant because something else was compensating is now not working together?
I wish I could say I have stayed up to date with the WP source, but alas, I have not since the very first 4.x release so I can’t say with any certainty what’s going on, so hence educated guesses to see if someone more involved can figure it out.
Quite surprised that we have gotten absolutely no input from any developer on the WP project, seems odd they wouldn’t address this.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Quite surprised that we have gotten absolutely no input from any developer on the WP project, seems odd they wouldn’t address this.
The developers generally don’t visit the forums here. Everyone here is a volunteer, including the developers, and they generally spend their time developing.
If you want to reach the developers, then Trac is the way to do it. As the last comment at https://core.trac.wordpress.org/ticket/17888 says, “Feel free to reopen with more information if there’s still a problem.”
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
Hi @guardian74 I deleted your comment. The personal commentary was both condescending and insulting. That doesn’t go far in these forums.
I suggest you give the forum welcome a read.
https://codex.wordpress.org/Forum_Welcome
This part in particular.
https://codex.wordpress.org/Forum_Welcome#Being_.27Mod_Watched.27_or_Banned
As you’ve gotten to the disparaging point in this conversation I am now closing this topic.
