Jeff Rose

This is affecting me in the same situation. It’s a compatibility issue with PHP 7.

• This reply was modified 7 years, 11 months ago by Jeff Rose.

It seems this issue is still not addressed, is there any chance of getting this? The workaround seems to not work 100%.

Right now, I’m creating a “simple” product that’s a duplicate of the main variation and applying the coming soon option to it. I’ll switch them when the actual product is available.

Thanks for the fix dries863.

Thanks Lucian. Not sure why I didn’t get notification of your comments. I’ll re-enable the plugin and see how it goes.

Thank you for looking into it.

When you say “tries to work”, can you be more clear? The plugin uses basic WordPress functions to set times of draft posts, which should continue to work unless Core makes major changes.

With more details, I can test this better.

I’m seeing similar behavior. The first post to Facebook (auto) is giving a 404 message, but if I publish again, it’s fine.

I get around this by first publishing the post without the Facebook option checked, and then update with the Facebook option checked.

But yes – Scheduling does not seem to work properly.

Hi Vrabecccc:

There are no limits built into Drafts Scheduler. It will schedule every draft you have. Now, 10K is a lot.

You’re likely running into server limitations, although 200 is low. I can schedule more than that on my local machine, which is way less powerful than a server should be.

The latest version (I assume you’re running) had an update to make it more efficient. Make sure you’re running the latest.

The schedule you choose won’t matter, since the processing is about the same for them. It just starts looping through the posts and assigning date/time to each.

Who is your website host?

Hi Zoltar:

1 – Random is random. If there were a “good interval”, it wouldn’t be random.

2 – Currently no. The plugin doesn’t know day from night. If you schedule 5 posts for a calendar day, they get scheduled during that 24 hour period based on the interval.

Remember too that even if people aren’t actively reading at night, they will be able to discover the content when they return, and Google will be able to index it in the meantime.

In either case, after the schedule is set, you can tweak it by editing the posts that don’t occur when you like them. The plugin was designed as a quick way to schedule a ton of posts, mainly from drip feeds, RSS and other bulk content creation.

With a small number of posts, it might be easier to handle them manually.

Posts are published by the WordPress Cron event if they are scheduled – that checks to see if it is needed on every page load.

If you don’t have traffic, then wp-cron doesn’t run.

If you’re not getting enough traffic, you can use a monitoring tool like Pingdom or something to ping your blog. This generates a page hit and will run the cron when needed.

Thanks for the feedback and suggestion.

I’ll update the plugin shortly with this.

Hi Andrikos, not sure if Paolo is replying the forum or not, but those are “warnings” of some less than perfect practice, but doesn’t cause the site to crash. Your site is running with WP_DEBUG on, which isn’t normal for a production site. These errors wouldn’t be seen.

Hi Stiofan, be sure to test a FRESH install. I can guarantee you’ll see a bunch of messages.

Yes, this is covered in the FAQs. It was added a couple of versions ago.

Sorry, that’s not currently a feature, and with some of the settings, it wouldn’t be possible.

Hi Alex:

This is a 3 year old issue that was resolved – as noted. Have you verified your server time is correct?