Plugins Garbage Collector (Database Cleanup)

설명

Database Cleanup plugin scans the database and shows the tables beyond of core WordPress installation. Some WordPress plugins create and use its own database tables.
Those tables are left in your database after plugin deactivation and deletion often.
With the help of this plugin you can check your database and discover if it is clean or not.
Extra columns added to the core WordPress tables could be shown also.
To read more about ‘Plugins Garbage Collector’ visit this link at shinephp.com

Additional Documentation

You can find more information about “Plugins Garbage Collector” plugin at this page
http://www.shinephp.com/plugins-garbage-collector-wordpress-plugin/

I am ready to answer on your questions about this plugin usage. Use ShinePHP forum at
http://shinephp.com/community/forum/plugins-garbage-collector/
or plugin page comments and site contact form for it please.

스크린샷

  • screenshot-1.png Plugins Garbage Collector scan action results.

설치

Installation procedure:

  1. Deactivate plugin if you have the previous version installed.
  2. Extract “plugins-garbage-collector.x.x.x.zip” archive content to the “/wp-content/plugins/plugins-garbage-collector” directory.
  3. Activate “Plugins Garbage Collector” plugin via ‘Plugins’ menu in WordPress admin menu.
  4. Go to the “Tools”-“Plugins Garbage Collector” menu item and scan your WordPress database if it has some forgotten tables from old plugins.

FAQ

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

후기

2020년 September 26일
TYVM for making this. I have wanted something like this forever. No more manual deleting junk using phpmyadmin. Simple, eloquent, and highly useful plugin that will help you identify junk and leftover tables in your database. It should be part of the core. I also use this author's "User Role Editor" (pro version) for years. Outstanding support any time time I needed his help. I highly recommend him and his plugins.
2020년 August 4일
I found database table entries from plugins I removed years ago! I forgot I even installed them to begin with. Cleaned up a lot of junk. Just what I needed.
2020년 July 27일
First I duplicated a website, then I installed plugins, then uninstalled them again etc. This to see why and which extra tables were added to the WordPress database. After that I uninstalled several plugins and finally tested this plugin. And indeed, this plugin found the remaining tables that I no longer need. That works perfectly for me! That is an indispensable plugin to keep WordPress in perfect condition! 🙂 I couldn't find a better one. 😉
2020년 July 6일
Hi Love this plugin but foreign-key constraints errors reduce its effectiveness for completing the whole job. If your prepared do the actual deletions yourself in phpMyAdmin (or similar) then this is a superb way of finding and highlighting the unwanted 'garbage tables' slowing down your installation. Please see my suggestion in this plugins forum: here. I, and i believe, many other who've encountered this would give this worthy plugin 5 big fat, in-your-face stars if all deletions on large DBs'/MultiSites were possible without hitch. Please take this as constructive, honest appraisal - nice work
모든 65 평가 읽기

기여자 & 개발자

“Plugins Garbage Collector (Database Cleanup)”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에 기여하였습니다.

기여자

“Plugins Garbage Collector (Database Cleanup)”(이)가 3(으)로 번역되었습니다. 기여해 주셔서 번역자님께 감사드립니다.

자국어로 “Plugins Garbage Collector (Database Cleanup)”(을)를 번역하십시오.

개발에 관심이 있으십니까?

코드 탐색하기는, SVN 저장소를 확인하시거나, 개발 기록RSS로 구독하십시오.

변경이력

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.