[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fUhfpm1Jx4dTwQlyTsSQikc733oMO57l0wVbqBnbqkVM":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"ealab","https:\u002F\u002Fprofiles.wordpress.org\u002Fkrealab\u002F",2,10,93,30,89,"2026-08-26T23:50:46.732Z",[13,37],{"slug":14,"name":15,"version":16,"author":17,"author_profile":5,"description":18,"short_description":19,"active_installs":7,"downloaded":20,"rating":21,"num_ratings":22,"last_updated":23,"tested_up_to":24,"requires_at_least":25,"requires_php":26,"tags":27,"homepage":31,"download_link":32,"security_score":33,"vuln_count":34,"unpatched_count":34,"last_vuln_date":35,"fetched_at":36},"kl-debug","KL Debug","1.0.5","Kiwik","\u003Cp>Add a Debug Bar to your WordPress website to debug and develop your themes, plugins, etc…\u003C\u002Fp>\n\u003Cp>With the plugin you can find every variables you want to debug in the same place and use debug functions to display them.\u003C\u002Fp>\n\u003Ch4>Prerequisites\u003C\u002Fh4>\n\u003Cp>To fully help you to debug your website you need to add some code to your \u003Ccode>wp-config.php\u003C\u002Fcode> file.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WP_DEBUG', true ); \u002F\u002F PHP errors, notices and warnings will be displayed\ndefine( 'SAVEQUERIES', true ); \u002F\u002F Display queries in current page\ndefine( 'WP_DISABLE_FATAL_ERROR_HANDLER', true ); \u002F\u002F Disable WP Fatal error handler\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Usage of the debug functions\u003C\u002Fh4>\n\u003Cp>To debug a simple variable you can use:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php dump( $var ); \u002F\u002F Dump the variable(s) ?>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>To debug a variable and stop the process after you can use:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php dd( $var ); \u002F\u002F This will die after dumping the variable(s) ?>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Debug a variable in the debug bar\u003C\u002Fh4>\n\u003Cp>This is one of the main aspect of the plugin, to debug variables in a separate place.\u003C\u002Fp>\n\u003Cp>The most difficult task when you debug a variable is to deal with container width, with the plugin you have a debug bar where you can add the variables of the current page.\u003C\u002Fp>\n\u003Cp>To add a variable to the debug bar you can use the function bellow:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php kl_debug_add_var( $var ); ?>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can add custom tabs in the debug bar to filter you variables:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php\nkl_debug_add_var(\n    $var, \u002F\u002F The variable you want to debug\n    'Your variable title', \u002F\u002F If you want to name the variable\n    'The section title', \u002F\u002F The tab title\n    'the-section-slug' \u002F\u002F The tab slug\n);\n?>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>What’s Whoops in the setting panel?\u003C\u002Fh4>\n\u003Cp>Whoops is the framework that we use to display error handling. (cf. Pretty error handler with stack frames)\u003C\u002Fp>\n","Friendly debug bar for developer, debug variables helpers and pretty error handler interface(powered by Whoops).",1712,100,1,"2022-06-24T07:18:00.000Z","6.0.12","5.2","7.2",[28,29,30],"debug","developer","toolbar","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fkl-debug.1.0.5.zip",85,0,null,"2026-07-22T17:31:50.256Z",{"slug":38,"name":39,"version":40,"author":4,"author_profile":41,"description":42,"short_description":43,"active_installs":34,"downloaded":44,"rating":21,"num_ratings":22,"last_updated":45,"tested_up_to":46,"requires_at_least":47,"requires_php":48,"tags":49,"homepage":55,"download_link":56,"security_score":21,"vuln_count":34,"unpatched_count":34,"last_vuln_date":35,"fetched_at":57},"deploy-sync-content","Deploy & Sync Content","2.2.0","https:\u002F\u002Fprofiles.wordpress.org\u002Fealab\u002F","\u003Cp>\u003Cstrong>⚠️ Warning: Experimental plugin. Please make a full backup before use and test thoroughly.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>About\u003C\u002Fh4>\n\u003Cp>The \u003Cem>WordPress\u003C\u002Fem> ecosystem has never offered a simple solution for managing content between environments. Since its inception, one problem persists: granular deployment of content and configurations.\u003C\u002Fp>\n\u003Cp>You develop on a test site and want to send only certain content to your production site. With existing tools, two scenarios often occur: creating duplicates… or having to overwrite the entire database. The constraints imposed by the diversity of plugin ecosystem operations have already caused several attempts to fail.\u003C\u002Fp>\n\u003Cp>We are convinced that a solution is possible.\u003C\u002Fp>\n\u003Cp>That’s why we designed \u003Cem>Deploy & Sync Content\u003C\u002Fem>: a new approach, designed to finally offer selective synchronization between your environments.\u003C\u002Fp>\n\u003Ch4>Main Features\u003C\u002Fh4>\n\u003Cp>The free version offers unidirectional synchronization (Production \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Staging\u002FLocal), ideal for simply transferring your content and media between your sites.\u003C\u002Fp>\n\u003Cp>For bidirectional synchronization and advanced features, check out the Pro version(https:\u002F\u002Fwp-deployer.io\u002Fen\u002Ffeatures).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Intelligent database merging\u003C\u002Fstrong>: The plugin detects existing content to update or create it as needed. You thus maintain the consistency of your environments and avoid any loss of information.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Unidirectional synchronization (free version)\u003C\u002Fstrong>: Production \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Staging\u002FLocal: quickly transfer your content and media between your sites.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Data conflict management\u003C\u002Fstrong>: The tool identifies and allows you to resolve differences before import, ensuring updates without loss.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Automatic ID mapping\u003C\u002Fstrong>: Avoid duplicates and inconsistencies related to page builders and ID references.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Preservation of content relationships\u003C\u002Fstrong>: Posts, taxonomies, media and metadata remain correctly linked after each synchronization.\u003C\u002Fp>\n\u003Ch3>Terms of use and External Services\u003C\u002Fh3>\n\u003Cp>\u003Cem>Deploy & Sync Content\u003C\u002Fem> is free to use and relies on the following services:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>\u003Cstrong>Online Configuration Service\u003C\u002Fstrong> (wp-deployer.io)\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Purpose\u003C\u002Fstrong>: Configures and updates the export\u002Fimport system. This service is optional, but recommended until alternatives are provided by the community.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Data Collection\u003C\u002Fstrong>:\n\u003Cul>\n\u003Cli>IP address of your WordPress instance\u003C\u002Fli>\n\u003Cli>Production URL (from plugin settings)\u003C\u002Fli>\n\u003Cli>Site URL\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>When Used\u003C\u002Fstrong>:\n\u003Cul>\n\u003Cli>During plugin activation\u003C\u002Fli>\n\u003Cli>For configuration updates\u003C\u002Fli>\n\u003Cli>For license verification (Pro version)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Security\u003C\u002Fstrong>: This data is used to protect our systems from spam and malicious use\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Privacy\u003C\u002Fstrong>: Data is not shared with any business partners\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Terms & Privacy\u003C\u002Fstrong>: \u003Ca href=\"https:\u002F\u002Fwp-deployer.io\u002Fen\u002Fgeneral-terms-and-conditions-use-gtcu\" rel=\"nofollow ugc\">https:\u002F\u002Fwp-deployer.io\u002Fen\u002Fgeneral-terms-and-conditions-use-gtcu\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Local Data Storage\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Purpose\u003C\u002Fstrong>: Temporary storage for content synchronization\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Location\u003C\u002Fstrong>: in the \u003Ccode>uploads\u003C\u002Fcode> directory of your WordPress installations\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Security\u003C\u002Fstrong>: Data is stored on your servers and is not transmitted to any external services\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cp>\u003Cem>Deploy & Sync Content\u003C\u002Fem> is developed by \u003Cem>EA Lab\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>\u003Cem>Deploy & Sync Content\u003C\u002Fem> includes the \u003Cem>plugin.json\u003C\u002Fem> file from the \u003Cem>WP Optimize\u003C\u002Fem> plugin\u003Cbr \u002F>\n(GPLv2+ licensed).\u003C\u002Fp>\n\u003Cp>\u003Cem>Deploy & Sync Content\u003C\u002Fem> includes various software dependencies taken from the packagist\u003Cbr \u002F>\nrepository, listed in \u003Cstrong>vendor\u003C\u002Fstrong> and \u003Cstrong>vendor-prefixed\u003C\u002Fstrong> directories. Most\u003Cbr \u002F>\nof them are unaltered in functionality. The only patched library is\u003Cbr \u002F>\n    jfcherng\u002Fphp-diff, which has been patched for translation and customized\u003Cbr \u002F>\nrendering.\u003C\u002Fp>\n","Move your content easily from your production instance to your development instance.",725,"2025-11-20T15:04:00.000Z","6.8.5","6.0","7.4",[50,51,52,53,54],"deploy","download","sync","transfer","upload","https:\u002F\u002Fwp-deployer.io\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdeploy-sync-content.2.2.0.zip","2026-04-16T10:56:18.058Z"]