{"id":310977,"date":"2026-06-11T15:59:49","date_gmt":"2026-06-11T15:59:49","guid":{"rendered":"https:\/\/it.wordpress.org\/plugins\/codingbunny-database-cleaner\/"},"modified":"2026-09-20T07:43:12","modified_gmt":"2026-09-20T07:43:12","slug":"codingbunny-database-cleaner","status":"publish","type":"plugin","link":"https:\/\/zh-sg.wordpress.org\/plugins\/codingbunny-database-cleaner\/","author":23187711,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.4.7","stable_tag":"1.4.7","tested":"7.1.1","requires":"6.2","requires_php":"8.2","requires_plugins":null,"header_name":"CodingBunny Database Cleaner","header_author":"CodingBunny","header_description":"User-friendly tool to inspect, clean and optimize your WordPress database.","assets_banners_color":"ebdfd0","last_updated":"2026-09-20 07:43:12","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"https:\/\/coding-bunny.com","rating":5,"author_block_rating":0,"active_installs":200,"downloads":3531,"num_ratings":2,"support_threads":3,"support_threads_resolved":2,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.1.1":{"tag":"1.1.1","author":"codingbunny","date":"2026-06-11 15:59:18","revision":3569112},"1.2.0":{"tag":"1.2.0","author":"codingbunny","date":"2026-06-18 07:11:07","revision":3576705},"1.2.1":{"tag":"1.2.1","author":"codingbunny","date":"2026-06-28 21:58:59","revision":3589281},"1.2.2":{"tag":"1.2.2","author":"codingbunny","date":"2026-07-04 10:05:26","revision":3595865},"1.2.3":{"tag":"1.2.3","author":"codingbunny","date":"2026-07-06 16:27:25","revision":3598091},"1.2.4":{"tag":"1.2.4","author":"codingbunny","date":"2026-07-17 09:01:10","revision":3611218},"1.3.0":{"tag":"1.3.0","author":"codingbunny","date":"2026-07-20 07:51:42","revision":3614355},"1.3.1":{"tag":"1.3.1","author":"codingbunny","date":"2026-07-21 15:18:59","revision":3617365},"1.4.0":{"tag":"1.4.0","author":"codingbunny","date":"2026-07-27 07:02:31","revision":3624069},"1.4.1":{"tag":"1.4.1","author":"codingbunny","date":"2026-07-29 06:31:02","revision":3626742},"1.4.2":{"tag":"1.4.2","author":"codingbunny","date":"2026-08-19 07:41:15","revision":3654074},"1.4.3":{"tag":"1.4.3","author":"codingbunny","date":"2026-08-26 15:23:17","revision":3667364},"1.4.4":{"tag":"1.4.4","author":"codingbunny","date":"2026-08-31 07:02:21","revision":3673519},"1.4.5":{"tag":"1.4.5","author":"codingbunny","date":"2026-09-02 08:11:10","revision":3677443},"1.4.6":{"tag":"1.4.6","author":"codingbunny","date":"2026-09-12 14:11:51","revision":3692748},"1.4.7":{"tag":"1.4.7","author":"codingbunny","date":"2026-09-20 07:43:12","revision":3703974}},"upgrade_notice":{"1.6.0":"<p>Large update: every module was rewritten for speed and reliability on big databases and multisite networks. The extended code search in the Prefix Scanner is now off until you enable it. Back up your database before cleaning, as always.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":2},"assets_icons":{"icon-256x256.png":{"filename":"icon-256x256.png","revision":3569117,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3569117,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3569117,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.1.1","1.2.0","1.2.1","1.2.2","1.2.3","1.2.4","1.3.0","1.3.1","1.4.0","1.4.1","1.4.2","1.4.3","1.4.4","1.4.5","1.4.6","1.4.7"],"block_files":[],"assets_screenshots":{"screenshot-1.jpg":{"filename":"screenshot-1.jpg","revision":3569112,"resolution":"1","location":"assets","locale":"","width":1200,"height":712},"screenshot-2.jpg":{"filename":"screenshot-2.jpg","revision":3569112,"resolution":"2","location":"assets","locale":"","width":1200,"height":705},"screenshot-3.jpg":{"filename":"screenshot-3.jpg","revision":3617365,"resolution":"3","location":"assets","locale":"","width":1200,"height":699}},"screenshots":[]},"plugin_section":[],"plugin_tags":[4657,153,1452,247,4062],"plugin_category":[52,54,59],"plugin_contributors":[237669],"plugin_business_model":[],"class_list":["post-310977","plugin","type-plugin","status-publish","hentry","plugin_tags-clean","plugin_tags-database","plugin_tags-optimize","plugin_tags-performance","plugin_tags-schedule","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_category-utilities-and-tools","plugin_contributors-codingbunny","plugin_committers-codingbunny"],"banners":{"banner":"https:\/\/ps.w.org\/codingbunny-database-cleaner\/assets\/banner-772x250.png?rev=3569117","banner_2x":"https:\/\/ps.w.org\/codingbunny-database-cleaner\/assets\/banner-1544x500.png?rev=3569117","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/codingbunny-database-cleaner\/assets\/icon-256x256.png?rev=3569117","icon_2x":"https:\/\/ps.w.org\/codingbunny-database-cleaner\/assets\/icon-256x256.png?rev=3569117","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/codingbunny-database-cleaner\/assets\/screenshot-1.jpg?rev=3569112","caption":""},{"src":"https:\/\/ps.w.org\/codingbunny-database-cleaner\/assets\/screenshot-2.jpg?rev=3569112","caption":""},{"src":"https:\/\/ps.w.org\/codingbunny-database-cleaner\/assets\/screenshot-3.jpg?rev=3617365","caption":""}],"raw_content":"<!--section=description-->\n<p>CodingBunny Database Cleaner is a WordPress plugin that helps you analyze, filter, and safely remove unnecessary data from your database. It can identify orphaned options, leftover post meta, unused comments, transients, and other types of residual data, giving you a clear overview of what is stored in your database and allowing you to clean it when needed.<\/p>\n\n<p>The plugin attempts to detect the likely origin of database entries \u2014 such as plugin, theme, or WordPress core \u2014 so you can review data with additional context before performing any deletion.<\/p>\n\n<h3>Why use CodingBunny Database Cleaner?<\/h3>\n\n<ul>\n<li>View database contents with detected origin information<\/li>\n<li>Remove unnecessary data with safety checks in place<\/li>\n<li>Improve database performance and reduce overhead<\/li>\n<li>Schedule automated cleanup tasks<\/li>\n<li>Contribute corrections when origin detection is inaccurate<\/li>\n<\/ul>\n\n<h4>Features<\/h4>\n\n<p><strong>Tables<\/strong>\n* Optimize, repair, and convert tables to InnoDB\n* Delete unused tables\n* Detect table sources\n* Inspect the contents of any table in a paginated viewer<\/p>\n\n<p><strong>Options<\/strong>\n* Delete unused options\n* Manage and optimize autoloaded options<\/p>\n\n<p><strong>Posts<\/strong>\n* Delete posts, revisions, auto drafts, and trashed posts\n* Scheduled cleanup support<\/p>\n\n<p><strong>Post Meta<\/strong>\n* Remove orphaned and unused post meta\n* Scheduled cleanup support<\/p>\n\n<p><strong>Comments<\/strong>\n* Delete spam, trashed, orphaned comments, pingbacks, and trackbacks\n* Scheduled cleanup support<\/p>\n\n<p><strong>Comment Meta<\/strong>\n* Remove orphaned and unused comment meta\n* Scheduled cleanup support<\/p>\n\n<p><strong>User Meta<\/strong>\n* Remove orphaned and unused user meta\n* Scheduled cleanup support<\/p>\n\n<p><strong>Term Meta<\/strong>\n* Remove orphaned and unused term meta\n* Scheduled cleanup support<\/p>\n\n<p><strong>Term Relationships<\/strong>\n* Remove unused term relationships\n* Scheduled cleanup support<\/p>\n\n<p><strong>Post Types<\/strong>\n* Remove unused post types<\/p>\n\n<p><strong>Transients<\/strong>\n* Delete expired and unused transients\n* Scheduled cleanup support<\/p>\n\n<p><strong>Cron Jobs<\/strong>\n* Remove unused scheduled cron jobs\n* Scheduled cleanup support<\/p>\n\n<p><strong>Action Scheduler<\/strong>\n* Delete completed, failed, and canceled actions\n* Clean up Action Scheduler logs\n* Scheduled cleanup support<\/p>\n\n<p><strong>oEmbed Cache<\/strong>\n* Remove oEmbed caches (all or expired only)\n* Scheduled cleanup support<\/p>\n\n<p><strong>Full Database Cleanup<\/strong>\n* Run a complete database cleanup in a single operation\n* Works within a time budget, so it can be run again to continue on very large databases<\/p>\n\n<p><strong>Prefix Scanner<\/strong>\n* Identify which plugin or theme an unknown database prefix belongs to\n* Local pattern and source code scan, with an optional lookup on the WordPress.org directory<\/p>\n\n<p><strong>General Tools<\/strong>\n* Multisite support (per-site or network-wide cleanup)\n* Filtering, searching, and sorting across all modules\n* Paginated results for large datasets\n* Preview the stored value of options, meta keys, transients, and scheduled actions before deleting them\n* Safety confirmations and nonce protection for all actions\n* Option to contribute detection corrections<\/p>\n\n<h3>Learn More<\/h3>\n\n<p>For additional information about WordPress database optimization and maintenance practices, you can refer to the following resource:<\/p>\n\n<p><a href=\"https:\/\/supporthost.com\/it\/ottimizzare-database-wordpress\/\">supporthost.com<\/a><\/p>\n\n<h3>Video Guide<\/h3>\n\n<p>A video overview of WordPress database cleanup and optimization techniques is available here:<\/p>\n\n<p>[youtube https:\/\/www.youtube.com\/watch?v=ZX-eS5Glchs]<\/p>\n\n<h3>External services<\/h3>\n\n<p>This plugin can connect to two external services. Both are used only inside the\n<strong>Prefix Scanner<\/strong> tool (DB Cleaner \u2192 Report Match), never during normal database cleaning,\nand never on the front end of your site.<\/p>\n\n<h4>1. WordPress.org Plugin and Theme Directory API<\/h4>\n\n<p>What it is used for: when you run a prefix scan, the plugin queries the official WordPress.org\ndirectory to find out which published plugin or theme a database prefix belongs to.<\/p>\n\n<p>What is sent: the prefix you typed into the Prefix Scanner field, and nothing else. No site URL,\nno user data, no database content.<\/p>\n\n<p>When it is sent: only when you click \"Start scan\" in the Prefix Scanner, and only after the\nlocal scans have failed to produce an exact match.<\/p>\n\n<p>Service provider: WordPress.org, run by the WordPress Foundation.\nTerms of service: https:\/\/wordpress.org\/about\/privacy\/\nPrivacy policy: https:\/\/wordpress.org\/about\/privacy\/<\/p>\n\n<h4>2. Veloria code search<\/h4>\n\n<p>What it is used for: an optional extended search that looks for the prefix inside the published\nsource code of plugins and themes that are not installed on your site \u2014 the case the local scan\ncannot cover.<\/p>\n\n<p>What is sent: the prefix you typed into the Prefix Scanner field, and nothing else. No site URL,\nno user data, no database content.<\/p>\n\n<p>When it is sent: only when you click \"Start scan\" in the Prefix Scanner, <strong>and only if you have\nexplicitly enabled this option<\/strong>. The option is disabled by default. You can turn it on or off at\nany time from the checkbox in the Prefix Scanner panel; while it is off, no request is made and\nno data leaves your site.<\/p>\n\n<p>What the service does with it: Veloria stores the search query and its results so that they can\nbe revisited, and keeps temporary server logs that include the IP address the request came from.\nVeloria states that it does not sell, share or transfer data to third parties.<\/p>\n\n<p>Service provider: Veloria (https:\/\/veloria.dev)\nTerms of service: https:\/\/veloria.dev\/terms\nPrivacy policy: https:\/\/veloria.dev\/privacy<\/p>\n\n<h4>Reporting an unknown match<\/h4>\n\n<p>The separate \"Report Match\" form sends an email to the plugin author with only the fields you\nfill in yourself: the item type, the item name, the plugin or theme you associate it with, and\nyour notes, plus the plugin, WordPress and PHP version numbers. It is sent through your own\nsite's mail system, it carries no site URL and no user data, and nothing is sent unless you\npress the button.<\/p>\n\n<h4>Controlling this from code<\/h4>\n\n<p>Site owners and hosts can control both services with filters:<\/p>\n\n<pre><code>\/\/ Hide the extended code search entirely: the option disappears from the UI.\nadd_filter( 'cbdc_pf_remote_search_available', '__return_false' );\n\n\/\/ Disable the WordPress.org lookup.\nadd_filter( 'cbdc_pf_wporg_search_enabled', '__return_false' );\n<\/code><\/pre>\n\n<p>The consent for the extended code search is stored in the site option\n    cbdc_pf_remote_consent (<code>0<\/code> = off, which is the default).<\/p>\n\n<!--section=installation-->\n<h4>1. Via WordPress dashboard<\/h4>\n\n<ul>\n<li>Go to Plugins \u2192 Add New<\/li>\n<li>Search for \"CodingBunny Database Cleaner\"<\/li>\n<li>Click Install Now and then Activate<\/li>\n<\/ul>\n\n<h4>2. Via upload<\/h4>\n\n<ul>\n<li>Download the plugin ZIP file<\/li>\n<li>Go to Plugins \u2192 Add New \u2192 Upload Plugin<\/li>\n<li>Select the ZIP file and install it<\/li>\n<li>Activate the plugin<\/li>\n<\/ul>\n\n<h4>3. Via FTP<\/h4>\n\n<ul>\n<li>Extract the plugin archive<\/li>\n<li>Upload the folder to \/wp-content\/plugins\/<\/li>\n<li>Activate it from the Plugins menu<\/li>\n<\/ul>\n\n<h4>After activation<\/h4>\n\n<p>Open the DB Cleaner menu in your WordPress dashboard sidebar.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"is%20this%20plugin%20safe%3F\"><h3>Is this plugin safe?<\/h3><\/dt>\n<dd><p>All cleanup actions require administrator permissions and are protected by nonces and confirmation prompts. Before deleting anything, the plugin checks again that each row is still eligible for removal. It is still recommended to back up your database before performing any cleanup.<\/p><\/dd>\n<dt id=\"can%20deleted%20data%20be%20recovered%3F\"><h3>Can deleted data be recovered?<\/h3><\/dt>\n<dd><p>No. Deleted data cannot be automatically restored. Always create a backup before cleanup operations.<\/p><\/dd>\n<dt id=\"does%20it%20support%20multisite%3F\"><h3>Does it support Multisite?<\/h3><\/dt>\n<dd><p>Yes. You can clean individual subsites or the entire network. Network-wide operations require network administrator permissions.<\/p><\/dd>\n<dt id=\"how%20does%20detection%20work%3F\"><h3>How does detection work?<\/h3><\/dt>\n<dd><p>The plugin matches database entries against known patterns to identify their likely origin (plugin, theme, or core). Users can submit corrections to improve accuracy.<\/p><\/dd>\n<dt id=\"is%20it%20suitable%20for%20large%20databases%3F\"><h3>Is it suitable for large databases?<\/h3><\/dt>\n<dd><p>Yes. Counting, filtering, and sorting are performed by the database itself rather than in PHP, results are paginated, and deletions run in batches within a time budget. For very large databases, running the full cleanup more than once is normal: each run continues where the previous one stopped.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20send%20any%20data%20anywhere%3F\"><h3>Does the plugin send any data anywhere?<\/h3><\/dt>\n<dd><p>Only inside the Prefix Scanner, and only when you start a scan. The scanner can query the WordPress.org directory, and it can optionally use an external code search service that is disabled until you enable it yourself. In both cases the only thing sent is the prefix you typed. See the \"External services\" section below for the full details.<\/p><\/dd>\n<dt id=\"what%20are%20the%20system%20requirements%3F\"><h3>What are the system requirements?<\/h3><\/dt>\n<dd><p>PHP 8.2 or later and WordPress 6.2 or later. If your server does not meet these requirements the plugin will not load and will tell you why, leaving the rest of your site untouched.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.4.7 \u2013 09\/17\/2026<\/h4>\n\n<ul>\n<li>Improved: added recognition for additional plugins<\/li>\n<li>Improved: rewrote every module for large databases \u2014 counting, filtering, sorting, and pagination are now handled by the database instead of loading whole tables into PHP<\/li>\n<li>Improved: greatly reduced memory usage and the number of queries needed to display each screen<\/li>\n<li>Improved: the cleanup totals in the sidebar are now cached and refreshed automatically when the data changes<\/li>\n<li>Improved: rewrote multisite handling across all modules, including network-wide pagination and cleanup<\/li>\n<li>Improved: the full database cleanup now runs within a time budget and can be repeated to continue, instead of timing out on large databases<\/li>\n<li>Improved: the full database cleanup now deletes posts and comments through the WordPress API, so related data and caches stay consistent<\/li>\n<li>Improved: deletions are checked once more before they run, and protected WordPress core entries are never removed<\/li>\n<li>Improved: scheduled cleanups are more reliable and no longer leave stale data in the interface<\/li>\n<li>Improved: reworked the admin interface \u2014 clearer bulk selections, accessible confirmations, keyboard support in the value preview windows<\/li>\n<li>Improved: the plugin is now fully translatable, including the interface texts and the summary messages<\/li>\n<li>Improved: the Prefix Scanner is faster, caches its results, and can be cancelled while running<\/li>\n<li>Improved: the extended code search in the Prefix Scanner is now disabled until you explicitly enable it, and clearly states what is sent and to whom<\/li>\n<li>Improved: added a requirements check that prevents the plugin from loading on unsupported PHP or WordPress versions<\/li>\n<li>Fixed: corrected the item counts shown in the sidebar and in the individual tabs, which could differ from each other<\/li>\n<li>Fixed: expired transients and oEmbed caches are now detected and counted correctly<\/li>\n<li>Fixed: deleting orphaned or unused meta no longer leaves related records behind<\/li>\n<li>Fixed: sorting and pagination settings no longer interfere between tabs<\/li>\n<li>Fixed: several actions could fail silently or report the wrong result message<\/li>\n<li>Fixed: scheduled cleanup events are now removed when the plugin is deactivated<\/li>\n<\/ul>\n\n<h4>1.4.6 \u2013 09\/12\/2026<\/h4>\n\n<ul>\n<li>Improved: added recognition for additional plugins<\/li>\n<\/ul>\n\n<h4>1.4.5 \u2013 09\/02\/2026<\/h4>\n\n<ul>\n<li>Improved: added recognition for additional plugins<\/li>\n<\/ul>\n\n<h4>1.4.4 \u2013 08\/31\/2026<\/h4>\n\n<ul>\n<li>Improved: added recognition for additional plugins<\/li>\n<\/ul>\n\n<h4>1.4.3 \u2013 08\/26\/2026<\/h4>\n\n<ul>\n<li>Fix: Corrected the recognition of Crocoblock plugins<\/li>\n<\/ul>\n\n<h4>1.4.2 \u2013 08\/19\/2026<\/h4>\n\n<ul>\n<li>Improved: added recognition for additional plugins<\/li>\n<li>Improved: compatibility with WordPress 7.1<\/li>\n<\/ul>\n\n<h4>1.4.1 \u2013 07\/29\/2026<\/h4>\n\n<ul>\n<li>Improved: added recognition for additional plugins<\/li>\n<\/ul>\n\n<h4>1.4.0 \u2013 07\/27\/2026<\/h4>\n\n<ul>\n<li>Improved: added recognition for additional plugins<\/li>\n<li>Improved: improved Prefix Scanner<\/li>\n<\/ul>\n\n<h4>1.3.1 \u2013 07\/21\/2026<\/h4>\n\n<ul>\n<li>Improvement: The Prefix Finder recognition system has been redesigned and renamed Prefix Scanner. Thanks to a direct connection to the WordPress repository APIs, it is no longer necessary to use artificial intelligence to identify database elements.<\/li>\n<li>Improvement: Added recognition for additional plugins<\/li>\n<li>Fix: Corrected the recognition of certain plugins<\/li>\n<\/ul>\n\n<h4>1.3.0 \u2013 07\/20\/2026<\/h4>\n\n<ul>\n<li>New: added Prefix Finder for local or AI-based recognition of database elements<\/li>\n<li>Improved: added recognition for additional plugins<\/li>\n<\/ul>\n\n<h4>1.2.4 \u2013 07\/17\/2026<\/h4>\n\n<ul>\n<li>Improved: added recognition for additional plugins<\/li>\n<\/ul>\n\n<h4>1.2.3 \u2013 07\/07\/2026<\/h4>\n\n<ul>\n<li>Improved: added recognition for additional plugins<\/li>\n<\/ul>\n\n<h4>1.2.2 \u2013 07\/04\/2026<\/h4>\n\n<ul>\n<li>Improved: expanded plugin recognition database<\/li>\n<\/ul>\n\n<h4>1.2.1 \u2013 06\/28\/2026<\/h4>\n\n<ul>\n<li>Improved: updated plugin detection rules<\/li>\n<li>Fixed: corrected WP Accessibility \/ WP Armour option mapping<\/li>\n<li>Fixed: corrected Bricks prefix associations<\/li>\n<\/ul>\n\n<h4>1.2.0 \u2013 06\/18\/2026<\/h4>\n\n<ul>\n<li>New: added summary messages for improved UX<\/li>\n<\/ul>\n\n<h4>1.1.2 \u2013 06\/14\/2026<\/h4>\n\n<ul>\n<li>Improved: expanded plugin recognition patterns<\/li>\n<li>Improved: improved builder pattern detection<\/li>\n<\/ul>\n\n<h4>1.1.1 \u2013 06\/11\/2026<\/h4>\n\n<ul>\n<li>Improved: added UI indicators for clickable elements<\/li>\n<li>Improved: improved color contrast for readability<\/li>\n<li>Improved: enhanced plugin recognition system<\/li>\n<li>Fixed: corrected Wordfence to 301 Redirects table association<\/li>\n<\/ul>\n\n<h4>1.1.0 \u2013 06\/10\/2026<\/h4>\n\n<ul>\n<li>New: added Unknown Match form<\/li>\n<\/ul>\n\n<h4>1.0.1 \u2013 06\/09\/2026<\/h4>\n\n<ul>\n<li>Improved: expanded plugin detection dataset<\/li>\n<li>Improved: moved WooCommerce-dependent patterns to separate file<\/li>\n<\/ul>\n\n<h4>1.0.0 \u2013 06\/07\/2026<\/h4>\n\n<ul>\n<li>Initial release<\/li>\n<\/ul>","raw_excerpt":"Keep your WordPress database fast and clean by removing orphaned data left behind by plugins, themes, and WordPress core.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/zh-sg.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/310977","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zh-sg.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/zh-sg.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/zh-sg.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=310977"}],"author":[{"embeddable":true,"href":"https:\/\/zh-sg.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/codingbunny"}],"wp:attachment":[{"href":"https:\/\/zh-sg.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=310977"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/zh-sg.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=310977"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/zh-sg.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=310977"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/zh-sg.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=310977"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/zh-sg.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=310977"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/zh-sg.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=310977"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}