[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f5bJLbhYC4cP0nm0fDrve2LPjgqMsuNNASuJ6yPD9GYs":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":32,"crawl_stats":29,"alternatives":38,"analysis":119,"fingerprints":210},"check-conflicts","Check Conflicts","1.1.6","ioannup","https:\u002F\u002Fprofiles.wordpress.org\u002Fioannup\u002F","\u003Cp>The plugin allows you to disable\u002Fenable plugins and\u002For activate a default theme for checking conflict between them \u003Cstrong>only for your IP\u003C\u002Fstrong>; other users won’t see any changes during the tests.\u003C\u002Fp>\n\u003Cp>It is made for developers, techical support engineers, as well as for regular WordPress users. Sometimes, usually after updating your plugins, themes or WordPress installation, strange issues may appear and mess the things up. This plugin provides a really neat way to check the problem.\u003C\u002Fp>\n\u003Ch3>Plugin Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Change active plugins only for your IP\u003C\u002Fli>\n\u003Cli>Change active theme only for your IP\u003C\u002Fli>\n\u003Cli>Add additional IPs to apply these settings\u003C\u002Fli>\n\u003Cli>Reset settings\u003C\u002Fli>\n\u003Cli>Support Multisites\u003C\u002Fli>\n\u003C\u002Ful>\n","The plugin allows you to disable\u002Fenable plugins and\u002For activate a default theme for checking conflict between them only for your IP; other users won&# &hellip;",1000,21152,94,18,"2023-11-07T16:20:00.000Z","6.4.8","5.0","5.6",[20,21,22,23,24],"check-plugin-conflicts","conflicts","debug","health-check","plugin-conflicts","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcheck-conflicts\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcheck-conflicts.1.1.6.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":34,"avg_security_score":27,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},3,1020,30,84,"2026-04-04T00:36:26.100Z",[39,62,82,94,106],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":49,"num_ratings":50,"last_updated":51,"tested_up_to":52,"requires_at_least":53,"requires_php":54,"tags":55,"homepage":59,"download_link":60,"security_score":61,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"plugin-detective","Plugin Detective – Troubleshooting Conflicts","1.2.29","NSquared","https:\u002F\u002Fprofiles.wordpress.org\u002Fcroixhaug\u002F","\u003Cp>\u003Cstrong>Plugin Detective helps you troubleshoot issues on your site quickly and easily to find the cause of a problem.\u003C\u002Fstrong> Once the culprit is found, the problem plugin can be quickly deactivated. You can even fix your site when it has the white screen of death (fatal error). You’ll want to have Plugin Detective installed, so if your site crashes from a conflict or bad plugin update, you can get it back up and running quickly!\u003C\u002Fp>\n\u003Cp>Plugin Detective is your best friend when you need to:\u003Cbr \u002F>\n– Troubleshoot WordPress plugin conflicts\u003Cbr \u002F>\n– Remove stuck .maintenance files\u003Cbr \u002F>\n– Recover your site from fatal errors caused by plugins\u003C\u002Fp>\n\u003Cp>We’ve all been there–something’s broken on your site. You’ve looked around the web for advice about what to do and have stumbled across the typical wisdom: deactivate all your plugins and then reactivate them one by one, checking your site for the problem after each reactivation.\u003C\u002Fp>\n\u003Cp>Ugh.\u003C\u002Fp>\n\u003Cp>Sure, it works. But who has \u003Cem>time\u003C\u002Fem> for that?\u003C\u002Fp>\n\u003Cdiv class=\"embed-vimeo\" style=\"text-align: center;\">\u003Ciframe loading=\"lazy\" src=\"https:\u002F\u002Fplayer.vimeo.com\u002Fvideo\u002F270010645\" width=\"750\" height=\"422\" frameborder=\"0\" webkitallowfullscreen mozallowfullscreen allowfullscreen>\u003C\u002Fiframe>\u003C\u002Fdiv>\n\u003Ch4>Find Plugin Conflicts with Detective Otto Bot\u003C\u002Fh4>\n\u003Cp>Detective Otto Bot walks you through solving your case one step at a time, all from one single screen.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Open a case and tell Detective Otto where you’re seeing the problem. If your site requires any plugins to run correctly, tell Otto about those, too.\u003C\u002Fli>\n\u003Cli>Then, Otto will interrogate the suspects and track clues, checking in with you from time to time.\u003C\u002Fli>\n\u003Cli>All you need to do is answer “Yes, it’s fixed” or “No, it’s still broken” each time. Otto will do the rest and find the culprit in minutes.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Best of all – Plugin Detective can work even if you’re seeing the White Screen of Death on your site or if all you can see are PHP errors. Please have a look at the FAQ’s for how to access Plugin Detective and log into WordPress even if you can’t get to your login screen.\u003C\u002Fp>\n\u003Cp>Once Otto has identified the culprit, you can quickly deactivate the troublesome plugin and go about your day.\u003C\u002Fp>\n\u003Ch4>Remove Stuck .Maintenance File or Scheduled Maintenance\u003C\u002Fh4>\n\u003Cp>Have you gotten stuck in maintenance mode on WordPress? The dreaded “Briefly unavailable for scheduled maintenance. Check back in a minute” message haunts you; the minute never ends!\u003C\u002Fp>\n\u003Cp>With Plugin Detective installed you can quickly get out of these situations without the hassle of deleting files via your host or FTP. Just tack on this slug to the end of your website URL:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002Fwp-content\u002Fplugins\u002Fplugin-detective\u002Ftroubleshoot\u002F?restore=1\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>So that your URL looks like this:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>https:\u002F\u002Fyoursite.com\u002Fwp-content\u002Fplugins\u002Fplugin-detective\u002Ftroubleshoot\u002F?restore=1\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This will prompt you to log in and automatically remove that stuck maintenance file for you.\u003C\u002Fp>\n\u003Ch4>Who Can Use This Troubleshooting Tool?\u003C\u002Fh4>\n\u003Cp>Plugin Detective is a tool that requires no coding experience or technical knowledge to use. For that reason, Plugin Detective is the ideal troubleshooting and conflict-checking tool for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Any WordPress website owner\u003C\u002Fli>\n\u003Cli>Developers and technical support engineers\u003C\u002Fli>\n\u003Cli>Plugin and theme owners and their support teams\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Debug Tool Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Strategically activate and deactivate plugins on your site to help you find the plugin causing trouble\u003C\u002Fli>\n\u003Cli>Open Plugin Detective for troubleshooting on any page on your site – both in the backend and the frontend!\u003C\u002Fli>\n\u003Cli>Choose any subset of your active plugins as the baseline for your testing  \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Loved by Plugin Support Teams\u003C\u002Fh4>\n\u003Cp>The \u003Ca href=\"https:\u002F\u002Fsimplyscheduleappointments.com\u002Fguides\u002Fplugin-detective-for-plugin-conflicts\u002F\" rel=\"nofollow ugc\">Simply Schedule Appointments\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwpdrawattention.com\u002Fguides\u002Fplugin-detective-for-finding-conflicts\u002F\" rel=\"nofollow ugc\">Draw Attention\u003C\u002Fa> support teams love to share this conflict-checking tool with their customers.\u003Cbr \u002F>\nPlugin Detective makes it easy for their clients to debug performance issues and figure out plugin conflicts in a jiffy!\u003C\u002Fp>\n\u003Ch3>1.2.14 – 2023-06-10\u003C\u002Fh3>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Fix PHP 8.2 compatibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.2.13 – 2023-05-25\u003C\u002Fh3>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Update required WP version to 6.1\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.2.12 – 2023-05-25\u003C\u002Fh3>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Update required WP version to 6.1\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.2.11 – 2023-04-27\u003C\u002Fh3>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Cp>PR:#25 – Compatibility with WordPress 6.2\u003C\u002Fp>\n\u003Ch3>1.2.10 – 2023-04-11\u003C\u002Fh3>\n\u003Ch4>Fixes\u003C\u002Fh4>\n\u003Cp>PR:#19 – Prevent fatal error on WP versions where WP_Textdomain_Registry doesn…\u003C\u002Fp>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Ch3>1.2.9 – 2023-03-28\u003C\u002Fh3>\n\u003Ch4>Fixes\u003C\u002Fh4>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Ch3>1.2.8 – 2023-03-28\u003C\u002Fh3>\n\u003Ch4>Fixes\u003C\u002Fh4>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Ch3>1.2.7 – 2023-03-28\u003C\u002Fh3>\n\u003Ch4>Fixes\u003C\u002Fh4>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Ch3>1.2.6 – 2023-02-24\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>no changes\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.2.3\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fixed for WP 6.1 compatibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.2.1\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fixed for WP 5.9 compatibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.1.8\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fixed for WP 5.8 compatibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.1.8\u003C\u002Fh3>\n\u003Cp>For older changelog entries, please see the \u003Ca href=\"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fplugin-detective\u002Ftrunk\u002FCHANGELOG.md\" rel=\"nofollow ugc\">additional changelog.txt file\u003C\u002Fa> delivered with the plugin.\u003C\u002Fp>\n","Plugin Detective helps you troubleshoot issues on your site quickly and easily to find the cause of a problem. Once the culprit is found, the problem  &hellip;",5000,211383,80,48,"2025-12-09T17:11:00.000Z","6.9.4","6.1","5.3",[56,21,22,57,58],"administration","support","troubleshoot","https:\u002F\u002Fnsquared.io","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fplugin-detective.1.2.29.zip",100,{"slug":63,"name":64,"version":65,"author":66,"author_profile":67,"description":68,"short_description":69,"active_installs":70,"downloaded":71,"rating":61,"num_ratings":72,"last_updated":73,"tested_up_to":52,"requires_at_least":74,"requires_php":18,"tags":75,"homepage":80,"download_link":81,"security_score":61,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"editor-cleanup-for-elementor","Editor Cleanup For Elementor: clean up and solve plugin conflicts with the Elementor editor","0.0.6","Jose Mortellaro","https:\u002F\u002Fprofiles.wordpress.org\u002Fgiuse\u002F","\u003Cp>Editor Cleanup For Elementor is an add-on of \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffreesoul-deactivate-plugins\u002F\" rel=\"ugc\">Freesoul Deactivate Plugins\u003C\u002Fa> to clean up the editor of \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Felementor\u002F\" rel=\"ugc\">Elementor\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>It will not only clean up the assets of other plugins, their PHP code will not run either.\u003C\u002Fp>\n\u003Cp>The Elementor editor will be faster and without conflicts with other plugins.\u003C\u002Fp>\n\u003Cp>Both Freesoul Deactivate Plugins and Elementor must be installed and active, in another case this plugin will not run.\u003C\u002Fp>\n\u003Ch3>How to clean up the Elementor editor\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Install and activate Freesoul Deactivate Plugins if not active yet\u003C\u002Fli>\n\u003Cli>Install and activate Elementor if not active yet\u003C\u002Fli>\n\u003Cli>Install and activate Editor Cleanup For Elementor\u003C\u002Fli>\n\u003Cli>Go to Elementor => Editor Cleanup\u003C\u002Fli>\n\u003Cli>Click on “Outer editor cleanup” to disable plugins that the outer editor does’t need (usually no plugin needed)\u003C\u002Fli>\n\u003Cli>Click on “Inner editor cleanup” to disable plugins that the inner editor does’t need (the inner editor is like the page on frontend, but loaded inside the Elementor editor)\u003C\u002Fli>\n\u003Cli>Click on “Editor loading cleanup” to disable the plugins that are called during the loading of the editor (usually no plugin needed, disabling plugins here can solve conflicts with other plugins)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Similar add-ons to clean up\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-oxygen\u002F\" rel=\"ugc\">Editor Cleanup For Oxygen\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-avada\u002F\" rel=\"ugc\">Editor Cleanup For Avada\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-wpbakery\u002F\" rel=\"ugc\">Editor Cleanup For WPBakery\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-divi-builder\u002F\" rel=\"ugc\">Editor Cleanup For Divi Builder\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-flatsome\u002F\" rel=\"ugc\">Editor Cleanup For Flatsome\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Backend Speed Optimization\u003C\u002Fh3>\n\u003Cp>Professional backend tuning for a smoother, faster WordPress admin.\u003Cbr \u002F>\nRead \u003Ca href=\"https:\u002F\u002Fjosemortellaro.com\u002Fbackend-speed-optimization\u002F\" rel=\"nofollow ugc\">Backend Speed Optimization\u003C\u002Fa> for more information.\u003C\u002Fp>\n\u003Ch3>Help\u003C\u002Fh3>\n\u003Cp>For any question or if something doesn’t work, don’t hesitate to open a thread on the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Feditor-cleanup-for-elementor\u002F\" rel=\"ugc\">support forum\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Please, before posting enable the debugging in wp-config.php. Need a step-by-step guide? Read \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Fhow-to-enable-debugging-in-wordpress-a-step-by-step-guide\u002F\" rel=\"nofollow ugc\">this detailed tutorial\u003C\u002Fa> on \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Fhow-to-enable-debugging-in-wordpress-a-step-by-step-guide\u002F\" rel=\"nofollow ugc\">how to enable debugging in WordPress\u003C\u002Fa> to learn more.\u003C\u002Fp>\n","FDP add-on to clean up the editor of Elementor. The Elementor editor will be faster and without conflicts with other plugins.",200,5473,2,"2025-12-10T09:01:00.000Z","4.6",[76,21,77,78,79],"cleanup","debugging","elementor","performance","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Feditor-cleanup-for-elementor.0.0.6.zip",{"slug":83,"name":84,"version":85,"author":66,"author_profile":67,"description":86,"short_description":87,"active_installs":61,"downloaded":88,"rating":61,"num_ratings":89,"last_updated":80,"tested_up_to":52,"requires_at_least":74,"requires_php":18,"tags":90,"homepage":80,"download_link":92,"security_score":61,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":93},"editor-cleanup-for-oxygen","Editor Cleanup For Oxygen: FDP add-on to cleanup the Oxygen editor","0.0.9","\u003Cp>Editor Cleanup For Oxygen is an add-on of \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffreesoul-deactivate-plugins\u002F\" rel=\"ugc\">Freesoul Deactivate Plugins\u003C\u002Fa> to \u003Cstrong>clean up the editor of \u003Ca href=\"https:\u002F\u002Foxygenbuilder.com\u002F\" rel=\"nofollow ugc\">Oxygen\u003C\u002Fa>\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>It will not only clean up the assets added by other plugins, their PHP code will not run either.\u003C\u002Fp>\n\u003Cp>The editor of Oxygen will load faster and without conflicts with other plugins.\u003C\u002Fp>\n\u003Cp>Both Freesoul Deactivate Plugins and Oxygen must be active, in another case this plugin will not run.\u003C\u002Fp>\n\u003Ch3>How to clean up the Oxygen editor\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Install and activate Freesoul Deactivate Plugins if not active yet\u003C\u002Fli>\n\u003Cli>Install and activate Oxygen if not active yet\u003C\u002Fli>\n\u003Cli>Install and activate Editor Cleanup For Oxygen\u003C\u002Fli>\n\u003Cli>Go to Oxygen => Editor CLeanup\u003C\u002Fli>\n\u003Cli>Click on “Outer editor cleanup” to disable plugins that the outer editor does’t need (usually no plugin needed)\u003C\u002Fli>\n\u003Cli>Click on “Inner editor cleanup” to disable plugins that the inner editor does’t need (the inner editor is like the page on frontend, but loaded inside the Oxygen editor)\u003C\u002Fli>\n\u003Cli>Click on “Editor loading cleanup” to disable the plugins that are called during the loading of the editor (usually no plugin needed, disabling plugins here can solve conflicts with other plugins)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Similar add-ons to clean up\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-elementor\u002F\" rel=\"ugc\">Editor Cleanup For Elementor\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-avada\u002F\" rel=\"ugc\">Editor Cleanup For Avada\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-wpbakery\u002F\" rel=\"ugc\">Editor Cleanup For WPBakery\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-divi-builder\u002F\" rel=\"ugc\">Editor Cleanup For Divi Builder\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-flatsome\u002F\" rel=\"ugc\">Editor Cleanup For Flatsome\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Backend Speed Optimization\u003C\u002Fh3>\n\u003Cp>Get a faster dashboard with deep plugin analysis and backend optimizations.\u003Cbr \u002F>\nRead \u003Ca href=\"https:\u002F\u002Fjosemortellaro.com\u002Fbackend-speed-optimization\u002F\" rel=\"nofollow ugc\">Backend Speed Optimization Service\u003C\u002Fa> for more information.\u003C\u002Fp>\n\u003Ch3>Help\u003C\u002Fh3>\n\u003Cp>For any question or if something doesn’t work, don’t hesitate to open a thread on the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Feditor-cleanup-for-oxygen\u002F\" rel=\"ugc\">support forum\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Read also \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Feditor-cleanup-for-oxygen\u002F\" rel=\"nofollow ugc\">How to clean up the Oxygen editor\u003C\u002Fa> for more details.\u003C\u002Fp>\n\u003Cp>Please, before posting enable the debugging in wp-config.php. Need a step-by-step guide? Read \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Fhow-to-enable-debugging-in-wordpress-a-step-by-step-guide\u002F\" rel=\"nofollow ugc\">this detailed tutorial\u003C\u002Fa> on \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Fhow-to-enable-debugging-in-wordpress-a-step-by-step-guide\u002F\" rel=\"nofollow ugc\">how to enable debugging in WordPress\u003C\u002Fa> to learn more.\u003C\u002Fp>\n","FDP add-on to cleanup Oxygen in the backend. Your Oxygen backend will be faster and without conflicts with other plugins.",3831,1,[76,21,77,91,79],"oxygen","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Feditor-cleanup-for-oxygen.0.0.9.zip","2026-03-15T10:48:56.248Z",{"slug":95,"name":96,"version":97,"author":66,"author_profile":67,"description":98,"short_description":99,"active_installs":100,"downloaded":101,"rating":61,"num_ratings":89,"last_updated":73,"tested_up_to":52,"requires_at_least":74,"requires_php":18,"tags":102,"homepage":80,"download_link":105,"security_score":61,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"editor-cleanup-for-flatsome","Editor Cleanup For Flatsome: FDP add-on to clean up the Flatsome UX Builder","0.0.5","\u003Cp>Editor Cleanup For Flatsome is an add-on of \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffreesoul-deactivate-plugins\u002F\" rel=\"ugc\">Freesoul Deactivate Plugins\u003C\u002Fa> to \u003Cstrong>clean up the editor of \u003Ca href=\"https:\u002F\u002Fflatsomebuilder.com\u002F\" rel=\"nofollow ugc\">Flatsome (UX Builder)\u003C\u002Fa>\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>It will not only clean up the assets added by other plugins, their PHP code will not run either.\u003C\u002Fp>\n\u003Cp>The editor of Flatsome will load faster and without conflicts with other plugins.\u003C\u002Fp>\n\u003Cp>Both Freesoul Deactivate Plugins and Flatsome must be installed and active, in another case this plugin will not run.\u003C\u002Fp>\n\u003Ch3>How to clean up the Flatsome editor\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Install and activate Freesoul Deactivate Plugins if not active yet\u003C\u002Fli>\n\u003Cli>Install and activate Flatsome if not active yet\u003C\u002Fli>\n\u003Cli>Install and activate Editor Cleanup For Flatsome\u003C\u002Fli>\n\u003Cli>Go to Flatsome => Editor CLeanup\u003C\u002Fli>\n\u003Cli>Click on “Outer editor cleanup” to disable plugins that the outer editor does’t need (usually no plugin needed)\u003C\u002Fli>\n\u003Cli>Click on “Inner editor cleanup” to disable plugins that the inner editor does’t need (the inner editor is like the page on frontend, but loaded inside UX Builder)\u003C\u002Fli>\n\u003Cli>Click on “Editor actions cleanup” to disable the plugins that are called during any action triggered by UX Builder (updating  an element, adding an element…) (usually no plugin needed, disabling plugins here can solve conflicts with other plugins)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Similar add-ons for cleanup\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-oxygen\u002F\" rel=\"ugc\">Editor Cleanup For Oxygen\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-elementor\u002F\" rel=\"ugc\">Editor Cleanup For Elementor\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-avada\u002F\" rel=\"ugc\">Editor Cleanup For Avada\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-wpbakery\u002F\" rel=\"ugc\">Editor Cleanup For WPBakery\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-divi-builder\u002F\" rel=\"ugc\">Editor Cleanup For Divi Builder\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Backend Speed Optimization\u003C\u002Fh3>\n\u003Cp>Improve your backend speed with targeted query and plugin-level optimization.\u003Cbr \u002F>\nRead \u003Ca href=\"https:\u002F\u002Fjosemortellaro.com\u002Fbackend-speed-optimization\u002F\" rel=\"nofollow ugc\">Backend Speed Optimization\u003C\u002Fa> for more information.\u003C\u002Fp>\n\u003Ch3>Help\u003C\u002Fh3>\n\u003Cp>For any question or if something doesn’t work, don’t hesitate to open a thread on the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Feditor-cleanup-for-flatsome\u002F\" rel=\"ugc\">support forum\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Read also \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Feditor-cleanup-for-flatsome\u002F\" rel=\"nofollow ugc\">How to clean up the Flatsome editor\u003C\u002Fa> for more details.\u003C\u002Fp>\n\u003Cp>Please, before posting enable the debugging in wp-config.php. Need a step-by-step guide? Read \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Fhow-to-enable-debugging-in-wordpress-a-step-by-step-guide\u002F\" rel=\"nofollow ugc\">this detailed tutorial\u003C\u002Fa> on \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Fhow-to-enable-debugging-in-wordpress-a-step-by-step-guide\u002F\" rel=\"nofollow ugc\">how to enable debugging in WordPress\u003C\u002Fa> to learn more.\u003C\u002Fp>\n","FDP add-on to clean up UX Builder, the editor of Flatsome. UX Builder will be faster and without conflicts with other plugins.",60,3455,[76,21,77,103,104],"flatsome","ux-builder","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Feditor-cleanup-for-flatsome.0.0.5.zip",{"slug":107,"name":108,"version":109,"author":66,"author_profile":67,"description":110,"short_description":111,"active_installs":112,"downloaded":113,"rating":61,"num_ratings":89,"last_updated":114,"tested_up_to":52,"requires_at_least":74,"requires_php":18,"tags":115,"homepage":80,"download_link":118,"security_score":61,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"editor-cleanup-for-divi-builder","Editor Cleanup For Divi Builder: FDP add-on to cleanup the Divi Builder frontend editor","0.0.4","\u003Cp>Editor Cleanup For Divi Builder is an add-on of \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffreesoul-deactivate-plugins\u002F\" rel=\"ugc\">Freesoul Deactivate Plugins\u003C\u002Fa> to cleanup \u003Ca href=\"https:\u002F\u002Fdivi-elegantthemes.com\u002Fpage-builder-plugin\u002F\" rel=\"nofollow ugc\">Divi Builder\u003C\u002Fa> frontend editor.\u003C\u002Fp>\n\u003Cp>It will not only clean up the assets of other plugins, but their PHP code will not run either.\u003C\u002Fp>\n\u003Cp>Your Divi Builder frontend editor will be faster and without conflicts with other plugins.\u003C\u002Fp>\n\u003Cp>Freesoul Deactivate Plugins and Divi Builder must be installed and active, in another case this plugin will not run.\u003C\u002Fp>\n\u003Cp>If you need to clean up the backend editor of Divi Builder, you need only Freesoul Deactivate Plugins. You can do the cleanup by going to Freesoul Deactivate Plugins => Backend Singles => Pages => Edit Single Page.\u003C\u002Fp>\n\u003Ch3>How to clean up the Divi Builder editor\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Install and activate Freesoul Deactivate Plugins if not active yet\u003C\u002Fli>\n\u003Cli>Install and activate Divi Builder if not active yet\u003C\u002Fli>\n\u003Cli>Install and activate Editor Cleanup For Divi Builder\u003C\u002Fli>\n\u003Cli>Go to Divi Builder => Frontend Editor Cleanup\u003C\u002Fli>\n\u003Cli>Click on “Frontend Editor Cleanup” to disable plugins that the frontend editor does’t need\u003C\u002Fli>\n\u003Cli>Click on “Editor Actions Cleanup” to disable the plugins that are called during the Ajax actions of the editor (usually no plugin needed, disabling plugins here can solve conflicts with other plugins)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Similar add-ons for cleanup\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-oxygen\u002F\" rel=\"ugc\">Editor Cleanup For Oxygen\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-elementor\u002F\" rel=\"ugc\">Editor Cleanup For Elementor\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-avada\u002F\" rel=\"ugc\">Editor Cleanup For Avada\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-wpbakery\u002F\" rel=\"ugc\">Editor Cleanup For WPBakery\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feditor-cleanup-for-flatsome\u002F\" rel=\"ugc\">Editor Cleanup For Flatsome\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Backend Speed Optimization\u003C\u002Fh3>\n\u003Cp>Slow admin area? I remove unnecessary queries and optimize backend processes.\u003Cbr \u002F>\nRead \u003Ca href=\"https:\u002F\u002Fjosemortellaro.com\u002Fbackend-speed-optimization\u002F\" rel=\"nofollow ugc\">Backend Speed Optimization\u003C\u002Fa> for more information.\u003C\u002Fp>\n\u003Ch3>Help\u003C\u002Fh3>\n\u003Cp>For any question or if something doesn’t work, don’t hesitate to open a thread on the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Feditor-cleanup-for-divi-builder\u002F\" rel=\"ugc\">support forum\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Please, before posting enable the debugging in wp-config.php. Need a step-by-step guide? Read \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Fhow-to-enable-debugging-in-wordpress-a-step-by-step-guide\u002F\" rel=\"nofollow ugc\">this detailed tutorial\u003C\u002Fa> on \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Fhow-to-enable-debugging-in-wordpress-a-step-by-step-guide\u002F\" rel=\"nofollow ugc\">how to enable debugging in WordPress\u003C\u002Fa> to learn more.\u003C\u002Fp>\n","FDP add-on to cleanup the frontend editor of Divi Builder. Your Divi Builder frontend editor will be faster and without conflicts with other plugins.",40,2468,"2025-12-10T09:00:00.000Z",[76,21,77,116,117],"divi","frontend-builder","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Feditor-cleanup-for-divi-builder.0.0.4.zip",{"attackSurface":120,"codeSignals":175,"taintFlows":195,"riskAssessment":196,"analyzedAt":209},{"hooks":121,"ajaxHandlers":171,"restRoutes":172,"shortcodes":173,"cronEvents":174,"entryPointCount":28,"unprotectedCount":28},[122,128,134,137,140,144,148,152,155,157,161,165,168],{"type":123,"name":124,"callback":125,"file":126,"line":127},"action","admin_menu","add_menu","check-conflicts.php",23,{"type":129,"name":130,"callback":131,"priority":132,"file":126,"line":133},"filter","plugin_action_links","add_plugin_action_links",10,24,{"type":129,"name":135,"callback":131,"priority":132,"file":126,"line":136},"network_admin_plugin_action_links",25,{"type":123,"name":124,"callback":125,"file":138,"line":139},"mu-plugins\\mu-check-conflicts.php",14,{"type":129,"name":141,"callback":142,"priority":28,"file":138,"line":143},"option_active_plugins","change_active_plugins",17,{"type":129,"name":145,"callback":146,"priority":28,"file":138,"line":147},"site_option_active_sitewide_plugins","change_sitewide_plugins",19,{"type":129,"name":149,"callback":150,"priority":28,"file":138,"line":151},"stylesheet","change_stylesheet",22,{"type":129,"name":153,"callback":154,"priority":28,"file":138,"line":127},"template","change_template",{"type":129,"name":130,"callback":156,"priority":28,"file":138,"line":136},"manage_plugins_action_links",{"type":129,"name":158,"callback":159,"file":138,"line":160},"bulk_actions-plugins","manage_plugins_bulk_actions",26,{"type":129,"name":162,"callback":163,"priority":132,"file":138,"line":164},"pre_update_option_active_plugins","closure",104,{"type":129,"name":166,"callback":163,"priority":132,"file":138,"line":167},"pre_update_site_option_active_sitewide_plugins",107,{"type":123,"name":169,"callback":169,"file":138,"line":170},"admin_notices",111,[],[],[],[],{"dangerousFunctions":176,"sqlUsage":177,"outputEscaping":182,"fileOperations":72,"externalRequests":28,"nonceChecks":183,"capabilityChecks":28,"bundledLibraries":194},[],{"prepared":72,"raw":89,"locations":178},[179],{"file":138,"line":180,"context":181},265,"$wpdb->get_var() with variable interpolation",{"escaped":132,"rawEcho":183,"locations":184},4,[185,188,190,192],{"file":138,"line":186,"context":187},203,"raw output",{"file":138,"line":189,"context":187},441,{"file":138,"line":191,"context":187},454,{"file":138,"line":193,"context":187},457,[],[],{"summary":197,"deductions":198},"The 'check-conflicts' plugin v1.1.6 presents a strong security posture with no identified vulnerabilities in its history and a generally good application of security practices in its code. The static analysis reveals a minimal attack surface with zero entry points, including no unprotected AJAX handlers or REST API routes. The code also demonstrates a good understanding of secure coding by using prepared statements for a majority of its SQL queries and properly escaping a significant portion of its output. The presence of nonce checks further enhances its security.\n\nHowever, there are a few areas that warrant attention. While the majority of SQL queries use prepared statements, the remaining portion does not, posing a potential risk if those queries are susceptible to SQL injection. Additionally, the plugin performs file operations, and without further context on these operations, it's difficult to definitively assess their security. The absence of capability checks on its entry points is a significant weakness; while there are currently no exposed entry points, if any were to be introduced in the future, they would lack proper authorization.\n\nGiven the plugin's clean vulnerability history and the positive aspects of its code analysis, the overall risk is currently low. The strengths lie in its minimal attack surface and the use of prepared statements and output escaping. The primary weaknesses stem from the small percentage of unescaped output, the file operations, and the lack of capability checks on any potential future entry points.",[199,202,204,207],{"reason":200,"points":201},"Some SQL queries do not use prepared statements",7,{"reason":203,"points":183},"Some output is not properly escaped",{"reason":205,"points":206},"File operations present potential risk",5,{"reason":208,"points":132},"No capability checks on entry points","2026-03-16T18:53:55.304Z",{"wat":211,"direct":220},{"assetPaths":212,"generatorPatterns":215,"scriptPaths":216,"versionParams":217},[213,214],"\u002Fwp-content\u002Fplugins\u002Fcheck-conflicts\u002Fcss\u002Fstyle.css","\u002Fwp-content\u002Fplugins\u002Fcheck-conflicts\u002Fjs\u002Fscript.js",[],[214],[218,219],"check-conflicts\u002Fstyle.css?ver=","check-conflicts\u002Fscript.js?ver=",{"cssClasses":221,"htmlComments":223,"htmlAttributes":225,"restEndpoints":227,"jsGlobals":228,"shortcodeOutput":230},[222],"check-conflicts-settings",[224],"\u003C!-- This is a Check Conflicts MU-plugin -->",[226],"data-check-conflicts-ip",[],[229],"window.checkConflictsIP",[]]