Plugins Garbage Collector (Database Cleanup)


El plugin de limpieza de la base de datos explora la base de datos y muestra las tablas más allá del núcleo de la instalación de WordPress. Algunos plugins de WordPress crean y usan sus propias tablas de base de datos.
Esas tablas a menudo se dejan en tu base de datos después de desactivar y borrar el plugin.
Con la ayuda de este plugin, puedes comprobar tu base de datos y descubrir si está limpia o no.
También se podrían mostrar columnas adicionales añadidas a las tablas del núcleo de WordPress.
Para leer más acerca de «Plugins Garbage Collector», visita este enlace en

Documentación adicional

Puedes encontrar más información acerca de el plugin «Plugins Garbage Collector» en esta página

Estoy listo para responder a tus preguntas acerca de el uso de este plugin. Usa el foro ShinePHP en
o los comentarios de la página del plugin y el formulario de contacto del sitio para ello, por favor.


  • resultados de la acción de exploración de Plugins Garbage Collector screenshot-1.png.


Procedimiento de instalación:

  1. Desactivar el plugin si tienes instalada la versión anterior.
  2. Extrae el contenido del archivo «» al directorio «/wp-content/plugins/plugins-garbage-collector».
  3. Activar el plugin «Plugins Garbage Collector» a través del menú «Plugins» en el menú de administración de WordPress.
  4. Ves al menú del elemento «Herramientas»-«Plugins Garbage Collector» y explora tu base de datos de WordPress si tiene algunas tablas olvidadas de plugins antiguos.


Próximamente. Solo pregúntar. Buscaré por la respuesta.


28 de mayo de 2021
Thanks to this plugin, I was able to clean up my database from uninstalled plugins I no longer use. If a table is unknown, you can easily google search for it. In most cases, you will find your answer what it is and if it is safe to remove directly. Suggestion: Option to edit Unknown tables and assign them to current plugins in use would be a great addition
7 de mayo de 2021
Even though it said it wasn't compatible with my version of WP - it ran smoothly. My Database tables isn't that big, but I'm told that optimising it is the key to a smooth operation. Couldn't believe what was in it after running WP-Sweep, but it didn't clean out the orphaned tables. I have been trying, (unsuccessfully), to remove old BuddyPress and WP_Members table entries from my Database for some time. WP-Optimize killed off the Primary Tables themselves, but it then left these children behind. wp_bp_friends, wp_bp_groups, wp_bp_groups_groupmeta, wp_bp_groups_members, wp_signups, wp_uwp_social_profiles I can even see them in my MySQL table using Adminer, but I'm not brave enough to go about dropping stuff in it. Not not one plugin I tried thus far could delete the orphaned kids. This one did, bravo: 10 out of 10, well done indeed! - Worked like a charm. Donation sent over. BTW - Every operation carried out above, was only undertaken AFTER A BACKUP WAS MADE! On Your Head Be It If You Don't Also Practice Taking Up The Back Method Now And Again! Hope it helped ..
3 de marzo de 2021
My database is maintained regularly including going in and deleting things manually along with wp-options tables. Well I just ran this plugin and wow all the crap it found is awesome 👍♥♥♥
Leer todas las 79 reseñas

Colaboradores y desarrolladores

«Plugins Garbage Collector (Database Cleanup)» es un software de código abierto. Las siguientes personas han colaborado con este plugin.


«Plugins Garbage Collector (Database Cleanup)» ha sido traducido a 5 idiomas locales. Gracias a los traductores por sus contribuciones.

Traduce «Plugins Garbage Collector (Database Cleanup)» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

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.

Leer changelog.txt para la lista completa de los cambios.