The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,878 other followers

Do I really need to write a WordPress API wrapper to check the status of “missed schedule” posts?

Posted by jpluimers on 2020/01/29

After years with “missed schedule” posts on (paid!) wordpress.com based sites, WordPress has documented that the scheduler officially does not support more than 100 posts:

[WayBackWarning: Please do not schedule more than 100 posts. Any posts scheduled beyond that amount will not be published.

In practice this is not fully true, so lets explain that a little.

Background

Imagine the list of scheduled posts as a list of posts to be posted anywhere from the near future (lets call that tail) until far in the future (for now head).

As long as you schedule posts in head to tail order, then there is no problem. You can schedule 100s of posts (usually I’ve between 700 and 1200 posts scheduled that way).

The problems appear when:

  • the list is long (in my experience: much larger than 100 posts, closer to 600-800, but that might depend on your blog)
  • you schedule *new* posts towards the tail(i.e. near future)

These new posts then will be marked “missed schedule” shortly after their scheduled time like for instance in Source: In case you are still curious on “It’s a German thing, you wouldn’t understand. ‘Dinner for one’ on New Year’s eve.”.

Despite taking discussions on this out of the public, not much changes: [WayBack] The “Missed Schedule” is back on WordPress.com. Now please go fix it for good. « WordPress.com Forums

Plugin-solutions

Pay more, become more dependent on stuff that will be retired some say.

Pay more, become more dependent on stuff that will be retired some say.

When you run your own site, or you pay WordPress.com much more and you dare to install plugins (which might be retired just[WayBack] like themes within a few years), that solve problems WordPress introduced in the first place, then you have a few choices

If I read the core PHP source code of them, I’m not really impressed by the large amount of code for a problem that seems so simple: scheduling posts.

If you still want to try plugins, then read these links:

Other solutions

Some posts indicate this might have to do with the WP-CRON job not running often enough or not at all. It looks like these URLs are related to it:

The plan for them was this:

Put one-minuted uptimerobot monitors on them, to see if they have any effect.

If these do not consistently work, I need to write my own API wrapper that posts ones marked missed-schedule.

They sort of worked:

  • scheduled posts were indeed posted after being on the “Missed Schedule” list for some time
  • the actual time of posting (which usually is NOT the “scheduled time”, or the “pubData” in the RSS on https://wiert.me/feed/) is when a non-“Missed Schedule” post is being posted

Next step I need to research is if there is a way to use the API to force posting.

Some notes on writing an API

For my link archive:

Note that this fails: https://wiert.me/wp-json/wp/v2/posts/ so I need to really dig into this more deeply on how to get started.

–jeroen

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

 
%d bloggers like this: