Plugins Garbage Collector WordPress plugin

Plugins Garbage Collector

Plugins Garbage Collector

Plugins Garbage Collector

Plugins Garbage Collector

This plugin scans your WordPress database and shows the tables which not belong to the core WordPress installation.
Some WordPress plugins create and use its own database tables. Those tables (small and large) are left in your database after plugin deactivation and deletion often. If your blog is more than 1 day old you have some plugins garbage in your WordPress database probably. With the help of this plugin you can check your database and discover if it is clean or not. Plugin shows not WordPress tables list with quant of its records, size they occupy in Kb. Plugin name and plugin state are shown too if those data are available.
Changes made to the core WordPress database tables (columns added) could be discovered too.

The latest version: 0.12. Click the Download button below if you wish to try it.
Quant of downloads: 244930
download
Attention! Starting from version 0.9.2 plugin works with WordPress 3.0 and higher only. For earlier WordPress versions use plugin version 0.9.1 from here.

Quick Links

FAQ

Look at “Plugins Garbage Collector” plugin in action screenshot:

Plugins Garbage Collector in action
  • Red color rows with high probability show old deleted plugins forgotten tables, so-called plugins garbage, which can be deleted from your WordPress database with the help of Delete Tables button or some of your favorite database tools, e.g. phpMyAdmin.
  • Blue color rows show tables which belong to deactivated plugins. Those tables are probably candidates for deletion after you decide to delete theirs parent plugins.
  • Green color rows show tables which belong to active plugins. Those tables are now in use. You do not need to touch them.

How Plugins Garbage Collector works? It selects all table names from your WordPress database, excludes core WordPress installation tables, then scans your plugins directory .php files text for table names and shows you the result as written above.

Delete Tables button appears if you have red color rows in the scan results table only. You need to turn on checkbox near the table name if you decided to drop it before click the Delete Tables button.
Attention! Delete table operation can not be rolled back. Please double think what are you doing before use Delete Tables button.
Plugins Garbage Collector is the decision support tool only and its conclusion about table usage can be wrong in some (I hope rare) cases. For example, if plugin developer uses some sophisticated scheme to assign names for his tables, not puts simple text into source code e.g. ‘my_plugin_table_name’, but calculates it with some algorithm e.g. ‘my’.’_’.’plugin’.’_’.’table’, etc… Final decision is for you – blog owner.

It is highly recommended to make database backup before apply any actions to your WordPress database.

Do you have a suggestion what useful feature we can add to this plugin? Please, left your comments.

Translations

Dear plugin User,
if you wish to help me with this plugin translation I very appreciate it. Please contact me via Contact form and I will answer you by email. Do not forget include your site link in order I can show it with greetings for the translation help at shinephp.com, plugin settings page and in this readme.txt file. If you have better translation for some phrases send it to me. You are welcome!

Special Thanks to

  • alx359 – for contribution to the source code which fixed AJAX empty response for WordPress multi-site with subdomains and other stuff.

You are welcome! Help me in the bug hunting, share with me new ideas about plugin further development, contribute to the source code and link to your site will appear here.


ChangeLog

0.12 [16.08.2020]

  • Update: Server side “Fatal error: Maximum execution time of NN seconds exceeded” should not take place now. PGC scans plugins with large quantity of files by splitting job to smaller parts per 500 files.
  • Update: “foreign key constraint fails” error should not prevent database table deletion. PGC temporally switches off “foreign keys constraints checking”.
  • Fix: Known database tables with DB prefix ‘wp_’ inside name (like wp_pro_quiz_question from LearnDash LMS) were not recognized. Code had used str_replace( $db_prefix, ”, $table_name ) to exclude DB prefix from the table name and broke the name itself.

0.11.1 [23.06.2020]

  • Fix: Checkbox to mark table for deletion was not shown, if table belongs to the known, but unused (uninstalled) plugin.
  • Fix: Plugin state translation is made now exactly before output, to use its value in the code logic safely.

0.11. [19.06.2020]

  • New: “Tools->Plugins Garbage Collector” menu item was renamed to “Tools->Database Cleanup”
  • New: Multisite support was added. It’s safe to use PGC at the single sites of the WordPress multisite network.
  • New: PGC uses the list of known database tables and list of plugins which do not create own database tables.
    This reduces files scanning time as plugins known for PGC are not scanned for database tables usage. PGC checks these lists updates once a day. There is an intent to extend/update known plugins list on the regular base.
  • New: It’s possible to hide (temporally exclude from the listing) any found database table. Earlier this feature was available only for the tables belong to the active plugins. You can use this feature to hide the tables which are known for you, but are not recognized by PGC. Thanks for reporting such cases.
  • Update: Call to deprecated function mysql_get_server_info() was excluded.
  • Update: PGC shows database tables in the original format, without converting them all to lowercase letters.
  • Fix: Last item in the installed plugins list ( item C in the list (A, B, C) ) was never scanned for database tables. Db tables created by such plugin were always shown as belong to unknown plugin.

Read changelog.txt for the full list of changes.

FAQ

Coming soon. Just ask it. I will search the answer.

download

I am ready to answer on your questions about this plugin usage and help with possible problems. Use Plugins Garbage Collector plugin forum or this page comments and site contact form for that please.

Thanks,
Vladimir, ShinePHP.com.

Tags: ,