WordPress loads every option marked as \"autoloaded\" into memory on every single page request. Over the years, plugins leave large or forgotten options behind, and every page gets a little slower and uses more memory. Database Cleaner makes this visible and lets you do something about it, without guessing.<\/p>\n\n
WordPress core options can never be changed. Transients are cleaned up, not switched.<\/p>\n\n
The free version fully covers the autoload analysis, changing single options with undo, and the clean-up of transients and revisions.<\/p>\n\n
Database Cleaner Pro<\/strong> adds:<\/p>\n\n Options are small settings stored in the database. Those marked as autoloaded are read on every single page request, whether the page needs them or not. A few hundred kilobytes is normal; several megabytes slow every page down and use memory on every request.<\/p><\/dd>\n Nothing is removed without showing you first what would be removed. WordPress core options cannot be changed, and every change to an option can be undone. One thing to know: if you stop an option from loading automatically that a plugin reads on every page, WordPress then fetches it with an extra database query each time. That is why the plugin only does it when you click, with a confirmation, and why you can undo it at any time. Take a backup before cleaning up a live site if you are unsure.<\/p><\/dd>\n WordPress core options, transients and the plugin's own settings are locked. Transients are handled under Clean up<\/em>, not here.<\/p><\/dd>\n The plugin guesses which plugin an option belongs to from the beginning of its name. It is a guess, not a certainty, and nothing is done automatically based on it.<\/p><\/dd>\n If a persistent object cache is active, WordPress keeps transients in that cache and not in the database, so there is nothing to remove from the database.<\/p><\/dd>\n Revisions older than the number of days you set under Settings<\/em>, except the newest ones of every post. By default it removes revisions older than 30 days and always keeps the newest 5 of every post.<\/p><\/dd>\n No. The free version makes no requests to external services and sets no cookies. It does not create its own database tables either.<\/p><\/dd>\n Deactivating keeps your settings and history. Deleting the plugin removes them. Changes you made to options and entries you removed stay as they are.<\/p><\/dd>\n The plugin works per site. Open it in the dashboard of each site you want to analyze or clean up.<\/p><\/dd>\n This plugin is provided without any warranty (\"as is\"). The developer assumes no liability for data loss or damage arising from its use. Taking a full backup before use is strongly recommended.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
\n
\n
What is autoload, and why does it matter?<\/h3><\/dt>\n
Can this break my site?<\/h3><\/dt>\n
Why can I not change some options?<\/h3><\/dt>\n
What does \"Probably from\" mean?<\/h3><\/dt>\n
Why does the transients clean-up say there is nothing to remove?<\/h3><\/dt>\n
What exactly does the revisions clean-up remove?<\/h3><\/dt>\n
Does the plugin send data to other servers?<\/h3><\/dt>\n
What happens when I deactivate or delete the plugin?<\/h3><\/dt>\n
Does it work on multisite?<\/h3><\/dt>\n
Liability?<\/h3><\/dt>\n
1.0.2<\/h4>\n\n
\n