[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fHXJ4P8XnUiGPLWIvt0I9q5dGgDWjhsWMHyRYZEUz0Fo":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":35,"analysis":132,"fingerprints":180},"echo-out-viewer","Echo Out Viewer","4.0.1","aminul Islam","https:\u002F\u002Fprofiles.wordpress.org\u002Faminul147471\u002F","\u003Cp>Echo Out Viewer lets you easily display and inspect PHP variable output directly in the browser, using a console-like interface. Helpful for debugging and development.\u003C\u002Fp>\n","Short Description: A simple tool to output and inspect PHP variables directly in your browser for debugging purposes.",0,444,"2025-07-21T03:10:00.000Z","6.8.5","5.0","7.0",[18,19,20,21,22],"debug","development","logging","output","php","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fecho-out-viewer.zip",100,null,"2026-03-15T15:16:48.613Z",[],{"slug":30,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":25,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},"aminul147471",1,30,94,"2026-04-04T15:11:00.791Z",[36,56,75,91,109],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":25,"num_ratings":31,"last_updated":46,"tested_up_to":47,"requires_at_least":48,"requires_php":49,"tags":50,"homepage":53,"download_link":54,"security_score":55,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"php-console-log","PHP Console Log","1.0.1","Marcus Viar","https:\u002F\u002Fprofiles.wordpress.org\u002Fmarcusviar\u002F","\u003Ch4>Examples\u003C\u002Fh4>\n\u003Cp>Place the \u003Cstrong>do_action( ‘php_console_log’, ‘My String or Array’ );\u003C\u002Fstrong> function anywhere in your WordPress plugin PHP code. The value(s) you pass into \u003Cstrong>do_action( ‘php_console_log’, ‘My String or Array’ );\u003C\u002Fstrong> will be logged to the web console in your browser.\u003C\u002Fp>\n\u003Ch4>Pass in a string\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>$my_string = 'My String';\ndo_action( 'php_console_log', $my_string );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Pass in an array\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>$my_array = array(\n    'elm 1'\n    'elm 2',\n);\ndo_action( 'php_console_log', $my_array );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Pass in an associative array\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>$my_array = array(\n    'key 1'=>'elm 1',\n    'key 2'=>'elm 2',\n);\ndo_action( 'php_console_log', $my_array);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Pass in an unlimited number of arguments nested to an unlimited depth (multi-dimensional array)\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>$my_array = array(\n    'My String 1',\n    'My String 2',\n    array(\n        'elm 1',\n        'elm 2',\n    ),\n    'My String 3',\n    array(\n        'key 1'=>'elm 1',\n        'key 2'=>'elm 2',\n        'key 3' => array(\n            'key 3a' => 'elm 3a',\n            'key 3b' => 'elm 3b',\n        ),\n    ),\n    'My String 4'\n);\ndo_action( 'php_console_log', $my_array);\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Log PHP variables and arrays to the web console in your browser via JavaScript's console.log(). No browser extensions required.",20,2536,"2020-02-07T08:58:00.000Z","5.3.21","4.4","5.6.20",[51,52,18,19,22],"browser","console-log","https:\u002F\u002Fmarcusviar.com\u002Fphp-console-log","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fphp-console-log.1.0.1.zip",85,{"slug":57,"name":58,"version":59,"author":60,"author_profile":61,"description":62,"short_description":63,"active_installs":64,"downloaded":65,"rating":11,"num_ratings":11,"last_updated":66,"tested_up_to":67,"requires_at_least":68,"requires_php":23,"tags":69,"homepage":73,"download_link":74,"security_score":55,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"mail-debug","Mail Debug","1.4","Ben","https:\u002F\u002Fprofiles.wordpress.org\u002Fbforchhammer\u002F","\u003Cp>This plugin when activated automatically redirects all email sent through wp_mail\u002Fphpmailer to the user currently logged in or the site administrator.\u003C\u002Fp>\n\u003Cp>The redirected email contains information about where the original email would have been sent to.\u003C\u002Fp>\n\u003Cp>Use this plugin if you want to test email-sending features without actually sending emails our to anyone but yourself. I wrote this plugin to ease debugging with subscribe2.\u003C\u002Fp>\n\u003Cp>Since Version 1.2 you can choose whether to redirect all email to the currently logged in user (default), the site administrator (only wpmu) or the blog administrator.\u003C\u002Fp>\n","Redirects all email sent through wordpress to the user currently logged in or the site administrator.",10,4253,"2010-07-20T15:01:00.000Z","2.7.1","2.7",[18,19,70,71,72],"email","phpmailer","wp_mail","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fmail-debug\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmail-debug.1.4.zip",{"slug":76,"name":77,"version":78,"author":79,"author_profile":80,"description":81,"short_description":82,"active_installs":64,"downloaded":83,"rating":11,"num_ratings":11,"last_updated":23,"tested_up_to":84,"requires_at_least":85,"requires_php":23,"tags":86,"homepage":88,"download_link":89,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":90},"wp-debug-logger","WP Debug Logger","0.1","Donncha O Caoimh (a11n)","https:\u002F\u002Fprofiles.wordpress.org\u002Fdonncha\u002F","\u003Cp>This plugin logs the activity of supported plugins to a file, making it easier to figure out why there’s a problem.\u003C\u002Fp>\n\u003Cp>If you have been asked to install this plugin because of a support issue then installing this plugin is just like installing any other plugin. Once installed, go to Settings->WP Logger and enable logging. If you have a number of supported plugins enable the one you are interested in.\u003C\u002Fp>\n\u003Cp>Developers who want to use this plugin to add logging to their own plugin should see the Developers section of this documentation.\u003C\u002Fp>\n\u003Cp>Mark Jaquith’s \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fmonitor-pages\u002F\" rel=\"ugc\">Monitor Pages\u003C\u002Fa> plugin was used as a template for this plugin. Thanks Mark!\u003C\u002Fp>\n\u003Ch4>Developers\u003C\u002Fh4>\n\u003Cp>Other plugins can use this plugin to record important events which are then dumped to a log file. Plugins must add the event to a global array in the following way:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$GLOBALS[ 'wp_log' ][ 'name_of_plugin' ][] = 'Some important event';\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Plugins must also add themselves to a list of enabled plugins. This will make it easier for blog owners to filter out which plugin they want to debug on the settings page. Add and edit the following code so it is executed when the plugin is loaded.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$GLOBALS[ 'wp_log_plugins' ][] = 'name_of_plugin';\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>A hypothetical example might be a plugin (let’s call it “Big A”) that uses the output buffer to change the letter “a” to “A”. The events recorded by this might include the following:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$GLOBALS[ 'wp_log' ][ 'big_a' ][] = 'Created output buffer';\n$GLOBALS[ 'wp_log' ][ 'big_a' ][] = 'Output buffer callback';\n$GLOBALS[ 'wp_log' ][ 'big_a' ][] = 'Replaced a with A in page';\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This plugin takes the “wp_log” array and dumps it to a file in the upload directory of the blog it’s activated on. The file is linked from the plugin settings page and can be deleted on that page too. The file is a simple text file and is not protected in any way so be careful if auth cookies are logged by a plugin.\u003C\u002Fp>\n\u003Cp>A “log” function isn’t included but if you want to add one to your plugin check the constant WP_DEBUG_LOG is defined before adding to the log array. If your plugin doesn’t use a class make sure that you call the log function a unique name so it doesn’t conflict with other plugins.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>function log( $message ) {\n    if ( defined( 'WP_DEBUG_LOG' ) )\n        $GLOBALS[ 'wp_log' ][ 'name_of_plugin' ][] = $message;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n","A plugin that makes it easy to log code activity to a file.",4742,"4.7.32","2.9.2",[18,19,87,22],"log","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fwp-debug-logger\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-debug-logger.zip","2026-03-15T10:48:56.248Z",{"slug":92,"name":93,"version":94,"author":95,"author_profile":96,"description":97,"short_description":98,"active_installs":11,"downloaded":99,"rating":11,"num_ratings":11,"last_updated":100,"tested_up_to":101,"requires_at_least":102,"requires_php":103,"tags":104,"homepage":107,"download_link":108,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"debug-toggle","Debug Toggle","1.7.8","webjive","https:\u002F\u002Fprofiles.wordpress.org\u002Fwebjive\u002F","\u003Cp>\u003Cstrong>Debug Toggle\u003C\u002Fstrong> is a WordPress plugin that allows administrators to easily manage WordPress debug settings directly from the dashboard. It provides the ability to enable or disable individual debug constants, such as \u003Ccode>WP_DEBUG\u003C\u002Fcode>, \u003Ccode>WP_DEBUG_LOG\u003C\u002Fcode>, \u003Ccode>WP_DEBUG_DISPLAY\u003C\u002Fcode>, \u003Ccode>SCRIPT_DEBUG\u003C\u002Fcode>, and \u003Ccode>SAVEQUERIES\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Toggle Debug Settings Individually:\u003C\u002Fstrong> Enable or disable each debug setting according to your needs.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debug Monitoring:\u003C\u002Fstrong> Prevent other plugins or themes from changing your debug settings by periodically enforcing your configurations.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Admin Bar Integration:\u003C\u002Fstrong> Quickly toggle all debug modes directly from the admin bar menu.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Uninstall Options:\u003C\u002Fstrong> Choose to remove all plugin data upon uninstalling the plugin, including removing debug constants from \u003Ccode>wp-config.php\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Automatic Cleanup on Reinstall:\u003C\u002Fstrong> Removes duplicate debug constants from \u003Ccode>wp-config.php\u003C\u002Fcode> on activation to ensure clean configuration.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Why Use Debug Toggle?\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Managing debug settings can be cumbersome, especially when you need to edit the \u003Ccode>wp-config.php\u003C\u002Fcode> file manually. Debug Toggle simplifies this process by providing an intuitive interface within the WordPress admin area, making it easier for developers and site administrators to control debugging options without directly editing core files.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This plugin is licensed under the GPLv2 or later.\u003C\u002Fp>\n\u003Ch3>Additional Info\u003C\u002Fh3>\n\u003Cp>For support and more information, please visit \u003Ca href=\"https:\u002F\u002Fwww.web-jive.com\" rel=\"nofollow ugc\">https:\u002F\u002Fwww.web-jive.com\u003C\u002Fa>.\u003C\u002Fp>\n","Manage WordPress debug settings from your dashboard. Toggle debug modes and prevent unauthorized changes.",172,"2025-12-01T20:34:00.000Z","6.6.5","5.2","5.6",[18,19,105,106],"troubleshooting","wp-config-php","https:\u002F\u002Fwww.web-jive.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-toggle.1.7.8.zip",{"slug":110,"name":111,"version":112,"author":113,"author_profile":114,"description":115,"short_description":116,"active_installs":117,"downloaded":118,"rating":119,"num_ratings":120,"last_updated":121,"tested_up_to":122,"requires_at_least":123,"requires_php":124,"tags":125,"homepage":128,"download_link":129,"security_score":130,"vuln_count":31,"unpatched_count":11,"last_vuln_date":131,"fetched_at":27},"query-monitor","Query Monitor – The developer tools panel for WordPress","3.20.2","John Blackbourn","https:\u002F\u002Fprofiles.wordpress.org\u002Fjohnbillion\u002F","\u003Cp>Query Monitor is the developer tools panel for WordPress and WooCommerce. It enables debugging of database queries, PHP errors, hooks and actions, block editor blocks, enqueued scripts and stylesheets, HTTP API calls, and more.\u003C\u002Fp>\n\u003Cp>It includes some advanced features such as debugging of Ajax calls, REST API calls, user capability checks, and full support for block themes and full site editing. It includes the ability to narrow down much of its output by plugin or theme, allowing you to quickly determine poorly performing plugins, themes, or functions.\u003C\u002Fp>\n\u003Cp>Query Monitor focuses heavily on presenting its information in a useful manner, for example by showing aggregate database queries grouped by the plugins, themes, or functions that are responsible for them. It adds an admin toolbar menu showing an overview of the current page, with complete debugging information shown in panels once you select a menu item.\u003C\u002Fp>\n\u003Cp>Query Monitor supports versions of WordPress up to three years old, and PHP version 7.4 or higher.\u003C\u002Fp>\n\u003Cp>For complete information, please see \u003Ca href=\"https:\u002F\u002Fquerymonitor.com\u002F\" rel=\"nofollow ugc\">the Query Monitor website\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Here’s an overview of what’s shown for each page load:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Database queries, including notifications for slow, duplicate, or erroneous queries. Allows filtering by query type (\u003Ccode>SELECT\u003C\u002Fcode>, \u003Ccode>UPDATE\u003C\u002Fcode>, \u003Ccode>DELETE\u003C\u002Fcode>, etc), responsible component (plugin, theme, WordPress core), and calling function, and provides separate aggregate views for each.\u003C\u002Fli>\n\u003Cli>The template filename, the complete template hierarchy, and names of all template parts that were loaded or not loaded (for block themes and classic themes).\u003C\u002Fli>\n\u003Cli>PHP errors presented nicely along with their responsible component and call stack, and a visible warning in the admin toolbar.\u003C\u002Fli>\n\u003Cli>Usage of “Doing it Wrong” or “Deprecated” functionality in the code on your site.\u003C\u002Fli>\n\u003Cli>Blocks and associated properties within post content and within full site editing (FSE).\u003C\u002Fli>\n\u003Cli>Matched rewrite rules, associated query strings, and query vars.\u003C\u002Fli>\n\u003Cli>Enqueued scripts and stylesheets, along with their dependencies, dependents, and alerts for broken dependencies.\u003C\u002Fli>\n\u003Cli>Language settings and loaded translation files (MO files and JSON files) for each text domain.\u003C\u002Fli>\n\u003Cli>HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.\u003C\u002Fli>\n\u003Cli>User capability checks, along with the result and any parameters passed to the capability check.\u003C\u002Fli>\n\u003Cli>Environment information, including detailed information about PHP, the database, WordPress, and the web server.\u003C\u002Fli>\n\u003Cli>The values of all WordPress conditional functions such as \u003Ccode>is_single()\u003C\u002Fcode>, \u003Ccode>is_home()\u003C\u002Fcode>, etc.\u003C\u002Fli>\n\u003Cli>Transients that were updated.\u003C\u002Fli>\n\u003Cli>Usage of \u003Ccode>switch_to_blog()\u003C\u002Fcode> and \u003Ccode>restore_current_blog()\u003C\u002Fcode> on Multisite installations.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>In addition:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Whenever a redirect occurs, Query Monitor adds an HTTP header containing the call stack, so you can use your favourite HTTP inspector or browser developer tools to trace what triggered the redirect.\u003C\u002Fli>\n\u003Cli>The response from any jQuery-initiated Ajax request on the page will contain various debugging information in its headers. PHP errors also get output to the browser’s developer console.\u003C\u002Fli>\n\u003Cli>The response from an authenticated WordPress REST API request will contain an overview of performance information and PHP errors in its headers, as long as the authenticated user has permission to view Query Monitor’s output. An \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Frest-api\u002Fusing-the-rest-api\u002Fglobal-parameters\u002F#_envelope\" rel=\"nofollow ugc\">an enveloped REST API request\u003C\u002Fa> will include even more debugging information in the \u003Ccode>qm\u003C\u002Fcode> property of the response.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>By default, Query Monitor’s output is only shown to Administrators on single-site installations, and Super Admins on Multisite installations.\u003C\u002Fp>\n\u003Cp>In addition to this, you can set an authentication cookie which allows you to view Query Monitor output when you’re not logged in (or if you’re logged in as a non-Administrator). See the Settings panel for details.\u003C\u002Fp>\n\u003Ch3>Other Plugins\u003C\u002Fh3>\n\u003Cp>I maintain several other plugins for developers. Check them out:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fuser-switching\u002F\" rel=\"ugc\">User Switching\u003C\u002Fa> provides instant switching between user accounts in WordPress.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-crontrol\u002F\" rel=\"ugc\">WP Crontrol\u003C\u002Fa> lets you view and control what’s happening in the WP-Cron system\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy Statement\u003C\u002Fh3>\n\u003Cp>Query Monitor is private by default and always will be. It does not persistently store any of the data that it collects. It does not send data to any third party, nor does it include any third party resources. \u003Ca href=\"https:\u002F\u002Fquerymonitor.com\u002Fprivacy\u002F\" rel=\"nofollow ugc\">Query Monitor’s full privacy statement can be found here\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Accessibility Statement\u003C\u002Fh3>\n\u003Cp>Query Monitor aims to be fully accessible to all of its users. \u003Ca href=\"https:\u002F\u002Fquerymonitor.com\u002Faccessibility\u002F\" rel=\"nofollow ugc\">Query Monitor’s full accessibility statement can be found here\u003C\u002Fa>.\u003C\u002Fp>\n","Query Monitor is the developer tools panel for WordPress and WooCommerce.",200000,19156533,98,463,"2025-12-11T22:16:00.000Z","6.9.4","6.1","7.4",[18,126,19,127,110],"debug-bar","performance","https:\u002F\u002Fquerymonitor.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquery-monitor.3.20.2.zip",97,"2026-03-30 23:21:22",{"attackSurface":133,"codeSignals":157,"taintFlows":169,"riskAssessment":170,"analyzedAt":179},{"hooks":134,"ajaxHandlers":153,"restRoutes":154,"shortcodes":155,"cronEvents":156,"entryPointCount":11,"unprotectedCount":11},[135,140,144,149],{"type":136,"name":137,"callback":138,"file":139,"line":32},"action","init","echooutviewer_maybe_log_output","echo-out-viewer.php",{"type":136,"name":141,"callback":142,"file":139,"line":143},"admin_menu","echooutviewer_add_admin_menu",78,{"type":136,"name":145,"callback":146,"file":147,"line":148},"admin_enqueue_scripts","echooutviewer_enqueue_admin_assets","includes\\enqueue.php",24,{"type":136,"name":150,"callback":151,"file":147,"line":152},"wp_enqueue_scripts","echooutviewer_enqueue_frontend_assets",43,[],[],[],[],{"dangerousFunctions":158,"sqlUsage":159,"outputEscaping":161,"fileOperations":11,"externalRequests":11,"nonceChecks":11,"capabilityChecks":167,"bundledLibraries":168},[],{"prepared":11,"raw":11,"locations":160},[],{"escaped":162,"rawEcho":31,"locations":163},17,[164],{"file":139,"line":165,"context":166},96,"raw output",2,[],[],{"summary":171,"deductions":172},"The \"echo-out-viewer\" plugin v4.0.1 demonstrates a generally strong security posture based on the static analysis.  It boasts a zero attack surface for direct entry points like AJAX handlers, REST API routes, and shortcodes, and importantly, none of these are unprotected. The plugin also avoids dangerous functions, file operations, and external HTTP requests, all of which are positive signs for security.  Furthermore, the code's adherence to prepared statements for SQL queries and the high percentage of properly escaped output are commendable practices that significantly reduce the risk of common vulnerabilities like SQL injection and cross-site scripting.",[173,176],{"reason":174,"points":175},"No Nonce Checks detected",5,{"reason":177,"points":178},"Limited Capability Checks",3,"2026-03-17T07:00:07.068Z",{"wat":181,"direct":194},{"assetPaths":182,"generatorPatterns":187,"scriptPaths":188,"versionParams":189},[183,184,185,186],"\u002Fwp-content\u002Fplugins\u002Fecho-out-viewer\u002Fassets\u002Fadmin\u002Fcss\u002Fadmin-style.css","\u002Fwp-content\u002Fplugins\u002Fecho-out-viewer\u002Fassets\u002Fadmin\u002Fjs\u002Fadmin-script.js","\u002Fwp-content\u002Fplugins\u002Fecho-out-viewer\u002Fassets\u002Ffrontend\u002Fcss\u002Ffrontend-style.css","\u002Fwp-content\u002Fplugins\u002Fecho-out-viewer\u002Fassets\u002Ffrontend\u002Fjs\u002Ffrontend-script.js",[],[184,186],[190,191,192,193],"echo-out-viewer\u002Fassets\u002Fadmin\u002Fcss\u002Fadmin-style.css?ver=","echo-out-viewer\u002Fassets\u002Fadmin\u002Fjs\u002Fadmin-script.js?ver=","echo-out-viewer\u002Fassets\u002Ffrontend\u002Fcss\u002Ffrontend-style.css?ver=","echo-out-viewer\u002Fassets\u002Ffrontend\u002Fjs\u002Ffrontend-script.js?ver=",{"cssClasses":195,"htmlComments":196,"htmlAttributes":197,"restEndpoints":198,"jsGlobals":199,"shortcodeOutput":200},[],[],[],[],[],[]]