Problem with scheduled post

Hi, Dallass.

Are you absolutely sure that the scheduled posts are posting on time, and simply not visible?

Or could it be possible that the scheduled posts are actually not posting at all until you interact with WordPress?

The reason I ask, is that the latter is a known issue. I’ve written an extensive blog post on the subject, but in a nutshell:

• wp-cron depends upon a request (any request) hitting the backend to wake it up.
• If your site is well-cached, there is no interaction with the WP backend, even when you have many visitors, and so wp-cron doesn’t run.
• When you check up on the post as admin, you hit the WP backend and cause wp-cron to start up, which in turn publishes the post.

Do you think this is what could be happening with your site? If so, you can fix it by using your system cron to wake up wp-cron every 10 minutes, every hour, or whatever schedule works for you.

There are detailed instructions in that blog post I mentioned.

If this isn’t the issue, please let us know!

Hi Lisa,

The post it is published but not visible on the website.

Just to be very clear: in the admin the post status it is changed from “Scheduled” to “Published” but the post it is not visible.

Before of LiteSpeed I was using WP Rocket and everything was OK.

Hmmm, ok. That is a different problem. Can you provide some additional details? Your site’s URL, and/or the environment report found under LiteSpeed Cache > Environment Report? It would be helpful to see your settings.

If you prefer not to share publicly, you may also email those details to [email protected]. Your choice ?? Thanks!

To find the Environment report I have followed the info presented here:
https://plugintests.com/results/litespeed-cache/1.2.2/screenshots/admin-6-litespeed-cache-environment-report.png

However, I do not have an Environment report.
Under LiteSpeed Chase i only have: Manage, Settings, Information, Image Optimization and Crawler.

I use LiteSpeed on a MultiSite, but the plugin it is not network active, but active under each site.

Hmmm. I have one last idea: Navigate to LiteSpeed Cache > Settings > Purge and take a look at Auto Purge Rules for Publish/Update and verify that there are check marks next to Front page and Home page and anything else you want to purge when a new post is published.

If those options are already checked, I’m afraid I don’t have any other suggestions. Would you please create a ticket (or send email to bug at litespeedtech.com) so that our support team can dig a little bit deeper into the issue?

Thanks!

The “Front Page” and “Homepage” are checked.
I dig up a bit before I posted here.

That’s good ??

It would definitely be a good idea to create a ticket, then. The support team can think of other areas to explore.

Hi Dallass,

Just a short question, is there any settings about cron in wp-config.php?
run command like cat wp-config.php | grep -i CRON

Best,
Eric

Where should I run this ? Via ssh ?

Hi Dallass,

Yes, but you need to know where your WordPress installed. Run the command in the WordPress folder.

I just tried Scheduled Post, cache purge normally with LSCache 1.6.2.1 + WP 4.8.3.

Best,
Eric

Hi, Dallass

Are you still having a problem with your scheduled posts, or can we close this thread?

The problem was not solved.

• This reply was modified 7 years, 4 months ago by dallass.

Hi Dallass,

So have you checked wp-config.php yet? What is the result?

Best,
Eric

I am not very good with shell commands. I use CPanel to manage my VPS.

But, I run the command you gave me cat wp-config.php | grep -i CRON.
Nothing happens. What should I expect as result ?

• This reply was modified 7 years, 4 months ago by dallass.

Hi, dallass.

To clarify what Eric wants you to try:

First, you should see if you are in the right directory. Do you see wp-config.php when you list the files? (ls command).

If so, and the grep above gave you no results, then you don’t have cron disabled in your wp-config.php. This is what you want – for wp-cron to be enabled.

If you are not in your WP root directory, then you’ll need to find out where that is for your installation, and run the grep command again.

Like I said before, though, troubleshooting this would be much easier if you create a ticket (or send email to [email protected]). There’s a limit to what we can accomplish in this forum ??