johnh10

From your log it looks like it is working. Perhaps you could elaborate just a smidge? Maybe post the rest of the log?

I don’t see a debug log so I’m unable to guess. Works fine here.

You could try WP Auto Poster.

Hmm the log looks correct. APS is querying WordPress for 1 random draft post. How many drafts do you have?

If WordPress is not returning a random post, likely another plugin (such as WPML) is hooking in and changing the query parameters. You can try this code snippet to suppress any filters during the APS query:

add_filter( 'aps_eligible_query', 'change_aps_eligible_query' );

function change_aps_eligible_query( $args ) {
  $args['suppress_filters'] = true;
  return $args;
}

Sorry, but yes cron can be a bit confusing. Even though the event is scheduled for a certain time, APS won’t be triggered by cron until cron checks for events on or after the scheduled time. In WordPress, this generally happens on the page load after the scheduled time has passed, however long that takes. If you need absolute timing, you can drop WordPress cron for a proper server cron job (use a Google search). Those will always trigger at the frequency you configure (such as check cron every minute).

>The above settings are still like they were. An idea whats wrong?

Nothing is wrong. Cron triggered APS and APS saw it wasn’t Tuesday between 0000 and 0100 and so did nothing, as you wanted.

>But it seems that APS is only do this, when I am logged in to the WordPress backend…

APS is only called via a cron event. By default, WordPress only checks for cron events during page loads. If someone doesn’t load a page until after the APS event time, then that is when cron will trigger APS to check your rules. If you’re the only one loading pages, then it would appear as you’ve stated.

I cannot tell from just what you provided.

But if there are no eligible posts found and recycle mode is on, APS will recycle the oldest content as new.

You got it. ??

No, but if this is the issue, then turning off object caching would solve it.

Hello,

I see APS publishes a post at 02:43:14 and correctly sets the next cron event for the next day. However, your cron triggers APS again shortly thereafter at 02:43:30 instead.

I’ve only see this when a caching plugin, like W3 or LiteSpeed, caches the object table, including the cron events, so scheduled events get messed up. That’s the only thing I can think of.

k

When you change the APS schedule time, APS still has to trigger to read the new value. After the next trigger it will set the following one for 480 seconds later.

You can try setting this up with APS.

If you want to randomly publish 3 posts randomly throughout the day, I would recommend something like:

Auto Post Schedule: 4-8 hours

Eligible Post Statuses: pending

Number of Posts: 1

Max Posts per day: 3

This tells cron to activate APS every 4 to 8 hours, query 1 pending post and publish it, with a max of 3 posts published each day. Hope that helps.

No, that limits checks to those hours on those days.

I’m not aware of any randomization of schedules feature. What is that?

Hello, I think I’ve found the issue. Please try updating to v1.83