Database cleanup: transients and revisions — follow-up

wp-cron only fires on page views, so low-traffic sites should switch to system cron.

The block editor is fine now, but I still install Classic Editor on client sites.

Child themes are still the correct way to override a theme you do not control.

My rule of thumb: if a plugin has not been updated in a year, it is a liability.

Would love to hear how you all handle this.

I cap client sites at 15 plugins, anything above that needs justification.

Nice thread, following for the replies.

I cap client sites at 15 plugins, anything above that needs justification.

Transient cleanup shaved 200MB off one of my databases.

I cap client sites at 15 plugins, anything above that needs justification.

Managed hosting saves me enough time to be worth the markup.

I disagree slightly, but I can see where you are coming from.

System cron fixed my missed scheduled posts too.

Managed hosting saves me enough time to be worth the markup.

Good point, I had not thought of it that way.

Could not agree more.

Headless WP is fun but a lot of moving parts for a blog.

Headless WP is fun but a lot of moving parts for a blog.

I cap client sites at 15 plugins, anything above that needs justification.

System cron fixed my missed scheduled posts too.

I disagree slightly, but I can see where you are coming from.

Nice thread, following for the replies.

Headless WP is fun but a lot of moving parts for a blog.

Headless WP is fun but a lot of moving parts for a blog.

Managed hosting saves me enough time to be worth the markup.

Good point, I had not thought of it that way.