You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inside the Site Health rapport, there are two things that SO should integrate with as a proper setup of a WordPress site on Servebolt now triggers two items. One critical, one recommended improvement.
Background updates are not working as expected.
This is triggered because the cron is moved to server. Easy thing to catch and because it's labeled as critical, this is what actually generates unnecessary support requests from clients.
You should use a persistent object cache
Since this is not available at all on Bolts, this should be further explained in Servebolt context.
The text was updated successfully, but these errors were encountered:
Thanks for the pointers Remkus. I will get the next sprint that I can.
Incidentally we've implemented 'Canny' https://roadmap.servebolt.com/ to give customers, and internals at servebolt the chance to place their throughts for improvements to get voted on and prioritized.
Inside the Site Health rapport, there are two things that SO should integrate with as a proper setup of a WordPress site on Servebolt now triggers two items. One critical, one recommended improvement.
This is triggered because the cron is moved to server. Easy thing to catch and because it's labeled as critical, this is what actually generates unnecessary support requests from clients.
Since this is not available at all on Bolts, this should be further explained in Servebolt context.
The text was updated successfully, but these errors were encountered: