[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fQz9qPa9uF1OmRBkdrav9wa-t-j4MYGWTWbLqzU9wZNw":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":39,"analysis":134,"fingerprints":311},"sf-adminbar-tools","Admin Bar Tools","4.0","Grégory Viguier","https:\u002F\u002Fprofiles.wordpress.org\u002Fgreglone\u002F","\u003Cp>The plugin adds a new tab in your admin bar with simple but useful indications and tools.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Displays the number of queries in your page and the amount of time to generate the page.\u003C\u002Fli>\n\u003Cli>Displays the php memory usage and php memory limits (constants \u003Ccode>WP_MEMORY_LIMIT\u003C\u002Fcode> and \u003Ccode>WP_MAX_MEMORY_LIMIT\u003C\u002Fcode>).\u003C\u002Fli>\n\u003Cli>displays the php version and WP version.\u003C\u002Fli>\n\u003Cli>Displays \u003Ccode>WP_DEBUG\u003C\u002Fcode>, \u003Ccode>SCRIPT_DEBUG\u003C\u002Fcode>, \u003Ccode>WP_DEBUG_LOG\u003C\u002Fcode>, \u003Ccode>WP_DEBUG_DISPLAY\u003C\u002Fcode>, and error reporting values.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>In your site front-end:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Lists the template and all template parts used in the current page (template parts added with \u003Ccode>get_template_part()\u003C\u002Fcode>). Compatible with WooCommerce’s templates.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$wp_query\u003C\u002Fcode>: this will open a lightbox displaying the content of \u003Ccode>$wp_query\u003C\u002Fcode>. Click the lightbox title to reload the value, click outside the lightbox to close it.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>In your site administration:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Admin hooks: lists some oftenly used hooks (like \u003Ccode>admin_init\u003C\u002Fcode>). The indicator to the right of the line tells you how many times the hook has been triggered by a callback. A “P” means the hook has a parameter: hover it for more details. Click a hook (on its text) to auto-select its code, for example: click \u003Cem>admin_init\u003C\u002Fem> to select \u003Ccode>add_action( 'admin_init', '' );\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$current_screen\u003C\u002Fcode>: displays the value of 4 properties of this object: \u003Ccode>id\u003C\u002Fcode>, \u003Ccode>base\u003C\u002Fcode>, \u003Ccode>parent_base\u003C\u002Fcode>, \u003Ccode>parent_file\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$...now\u003C\u002Fcode>: displays the value of the well-known variables \u003Ccode>$pagenow\u003C\u002Fcode>, \u003Ccode>$typenow\u003C\u002Fcode>, and \u003Ccode>$taxnow\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>On a user profile page, \u003Ccode>$userdata\u003C\u002Fcode>: : this will open a lightbox displaying the user’s data.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>You can decide who’s gonna use this plugin (go to your profile page for all the settings). This way, the plugin’s items won’t show up to other users (your client for example).\u003Cbr \u002F>\nAlso, a new menu item \u003Ccode>Code Tester\u003C\u002Fcode> will appear. There you are able to do some tests with your code.\u003C\u002Fp>\n","Adds some small development tools to the admin bar.",400,15121,96,8,"2021-01-18T16:09:00.000Z","5.6.0","4.7","5.6",[20,21,22,23,24],"debug","development","query","testing","tests","https:\u002F\u002Fwww.screenfeed.fr\u002Fsf-abt\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsf-adminbar-tools.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":33,"display_name":7,"profile_url":8,"plugin_count":34,"total_installs":35,"avg_security_score":27,"avg_patch_time_days":36,"trust_score":37,"computed_at":38},"greglone",5,7410,30,84,"2026-04-03T21:28:59.142Z",[40,62,80,97,116],{"slug":41,"name":42,"version":43,"author":44,"author_profile":45,"description":46,"short_description":47,"active_installs":48,"downloaded":49,"rating":50,"num_ratings":51,"last_updated":52,"tested_up_to":53,"requires_at_least":54,"requires_php":55,"tags":56,"homepage":59,"download_link":60,"security_score":61,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"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",[20,57,21,58,41],"debug-bar","performance","https:\u002F\u002Fquerymonitor.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquery-monitor.3.20.2.zip",100,{"slug":63,"name":64,"version":65,"author":66,"author_profile":67,"description":68,"short_description":69,"active_installs":61,"downloaded":70,"rating":61,"num_ratings":34,"last_updated":71,"tested_up_to":72,"requires_at_least":73,"requires_php":55,"tags":74,"homepage":78,"download_link":79,"security_score":61,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"debugpress","DebugPress: Debugger in Popup","4.1","Milan Petrovic","https:\u002F\u002Fprofiles.wordpress.org\u002Fgdragon\u002F","\u003Cp>DebugPress is an easy-to-use plugin implementing popup for debugging and profiling currently loaded WordPress powered website page with support for intercepting AJAX requests. The main debugger window is displayed as a popup, activated through the button with the Bug integrated into WordPress Toolbar, or floating on the page.\u003C\u002Fp>\n\u003Cp>The plugin currently has a total of 22 tabs in the popup debugger window, showing all kinds of information relevant to the current page, WordPress setup, background AJAX calls, and much more.\u003C\u002Fp>\n\u003Cp>The plugin doesn’t modify or replace any WordPress files or functions.\u003C\u002Fp>\n\u003Ch4>Home and GitHub\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Learn more about the plugin: \u003Ca href=\"https:\u002F\u002Fwww.dev4press.com\u002Fplugins\u002Fdebugpress\u002F\" rel=\"nofollow ugc\">DebugPress Website\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Contribute to plugin development: \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdev4press\u002Fdebugpress\" rel=\"nofollow ugc\">DebugPress on GitHub\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Quick Overview Video\u003C\u002Fh4>\n\u003Cp>\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002F-eFnBRLhy-s?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\u003C\u002Fp>\n\u003Ch4>Pretty Print for objects\u003C\u002Fh4>\n\u003Cp>To display the content of objects or arrays, plugin has pretty print functionality through use of simpler PrettyPrint library, or more robust third-party library Kint. You can choose one or the other from the plugin Settings, Advanced tab.\u003C\u002Fp>\n\u003Ch4>Debugger Panels\u003C\u002Fh4>\n\u003Cp>Currently, the plugin has the following panels:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Basic\u003C\u002Fli>\n\u003Cli>Request (optional)\u003C\u002Fli>\n\u003Cli>Query (for frontend only)\u003C\u002Fli>\n\u003Cli>Content (optional)\u003C\u002Fli>\n\u003Cli>Roles (optional)\u003C\u002Fli>\n\u003Cli>Constants (optional)\u003C\u002Fli>\n\u003Cli>Hooks (optional)\u003C\u002Fli>\n\u003Cli>PHP (optional)\u003C\u002Fli>\n\u003Cli>Server (optional)\u003C\u002Fli>\n\u003Cli>Enqueue (optional)\u003C\u002Fli>\n\u003Cli>SQL Queries (if SQL queries logging is enabled)\u003C\u002Fli>\n\u003Cli>User (optional, if user is logged in only)\u003C\u002Fli>\n\u003Cli>HTTP (optional, if HTTP API calls are captured)\u003C\u002Fli>\n\u003Cli>bbPress (optional, on bbPress forum pages only)\u003C\u002Fli>\n\u003Cli>Plugins (optional, if plugins store data)\u003C\u002Fli>\n\u003Cli>Errors (for all captured PHP errors)\u003C\u002Fli>\n\u003Cli>Doing It Wrong (for captured WordPress Doing It Wrong warnings)\u003C\u002Fli>\n\u003Cli>Deprecated (for captured PHP deprecated warnings)\u003C\u002Fli>\n\u003Cli>AJAX (for captured AJAX calls while page is active)\u003C\u002Fli>\n\u003Cli>Store (for any user stored objects during the page loading)\u003C\u002Fli>\n\u003Cli>Tools (internal and external tools links)\u003C\u002Fli>\n\u003Cli>Debug Log (load content on demand from WordPress ‘debug.log’)\u003C\u002Fli>\n\u003Cli>Layout (control the size, position and activation of the popup)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>SQL Queries\u003C\u002Fh4>\n\u003Cp>This panel lists all the queries WordPress has run. It allows you to order the queries by execution order or length of execution, and all queries can be filtered by the query type, database table it targets or the WordPress function that called it. Every query displays the execution time, order, caller functions stack and fully formatted SQL query that is easy to read. For some Dev4Press created plugins (and that list will grow), DebugPress can detect the source of the query and allow you to filter by the plugin calling the query.\u003C\u002Fp>\n\u003Ch4>PHP and WordPress Errors\u003C\u002Fh4>\n\u003Cp>Plugin has 3 panels dedicated to showing PHP and WordPress errors and warnings. The Plugin captures this information during the page load, and it shows full debug trace as returned by the PHP debug tracing function.\u003C\u002Fp>\n\u003Ch4>AJAX\u003C\u002Fh4>\n\u003Cp>The plugin tracks every AJAX call coming through WordPress \u003Ccode>admin-ajax.php\u003C\u002Fcode> handler, and with every response, it returns HTTP headers with AJAX request basic execution information. Right now, plugin is not returning a list of logged errors or SQL queries, because both can produce huge output that goes over the HTTP header limits. Plan is to introduce these in the future plugin versions.\u003C\u002Fp>\n\u003Ch4>Info Panels\u003C\u002Fh4>\n\u003Cp>In the administration Tools menu, plugin adds DebugPress Info page showing several panels\u003C\u002Fp>\n\u003Cul>\n\u003Cli>PHP Info: full formatted results from \u003Ccode>phpinfo()\u003C\u002Fcode> function\u003C\u002Fli>\n\u003Cli>OPCache Info: full settings and statistics for the OPCache PHP extension\u003C\u002Fli>\n\u003Cli>MySQL Variables: full MySQL settings retrieved from the database\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Plugin Settings\u003C\u002Fh4>\n\u003Cp>The plugin has various options controlling the plugin activation, button integration position, user roles that can see the debugger window, options to attempt overriding WordPress debug flags and options controlling the visibility of optional debugger panels.\u003C\u002Fp>\n\u003Ch4>Log into Database\u003C\u002Fh4>\n\u003Cp>Debugger popup is visible for the request running in the browser. But there are many requests that are happening in the background (AJAX calls, REST API calls…), and for them, you can’t see errors, call information and other stuff in the debugger. Because of that, DebugPress supports logging of various events into database with the use of ‘coreActivity’ plugin, and it is highly recommended to install and use coreActivity.\u003C\u002Fp>\n\u003Cp>Log various debug events into a database with the free plugin: \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcoreactivity\u002F\" rel=\"ugc\">coreActivity Plugin\u003C\u002Fa>, supporting over 120 events and 10 popular WordPress plugins. DebugPress related events will be logged and available for later analysis, and this includes errors, AJAX calls, and HTTP API calls.\u003C\u002Fp>\n\u003Ch4>Documentation and Support\u003C\u002Fh4>\n\u003Cp>To get help with the plugin, you can use WordPress.org support forums, or you can use Dev4Press.com support forums.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Plugin Documentation: \u003Ca href=\"https:\u002F\u002Fwww.dev4press.com\u002Fkb\u002Fproduct\u002Fdebugpress\u002F\" rel=\"nofollow ugc\">DebugPress Website\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Support Forum: \u003Ca href=\"https:\u002F\u002Fsupport.dev4press.com\u002Fforums\u002Fforum\u002Fplugins-free\u002Fdebugpress\u002F\" rel=\"nofollow ugc\">Dev4Press Support\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Easy-to-use plugin for debugging and profiling website loading, SQL queries analysis, help with development, bug fixing, all in configurable popup.",14884,"2025-09-29T18:36:00.000Z","6.8.5","5.5",[75,76,77,21,41],"ajax-monitor","debugging","dev4press","https:\u002F\u002Fwww.dev4press.com\u002Fplugins\u002Fdebugpress\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebugpress.4.1.zip",{"slug":81,"name":82,"version":83,"author":84,"author_profile":85,"description":86,"short_description":87,"active_installs":88,"downloaded":89,"rating":28,"num_ratings":28,"last_updated":90,"tested_up_to":91,"requires_at_least":92,"requires_php":16,"tags":93,"homepage":95,"download_link":96,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"back-to-the-theme","Back To The Theme","1.2.0","Mikael Korpela","https:\u002F\u002Fprofiles.wordpress.org\u002Fsimison\u002F","\u003Cp>A tool to observe how a page loads in different themes simultaneously.\u003Cbr \u002F>\nUseful for debugging plugins or Gutenberg blocks.\u003C\u002Fp>\n\u003Cp>How to Use:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Install several themes you’d like to check out.\u003C\u002Fli>\n\u003Cli>Create a new page.\u003C\u002Fli>\n\u003Cli>Navigate to \u003Cem>Tools\u003C\u002Fem> \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> \u003Cem>Back To The Theme\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>Choose if you want to demo editor- or view side.\u003C\u002Fli>\n\u003Cli>Select the themes you’d like to check out.\u003C\u002Fli>\n\u003Cli>Choose the page you just created. This page will be previewed with all the themes you’ve selected.\u003C\u002Fli>\n\u003Cli>Click \u003Cem>Do it!\u003C\u002Fem>.\u003C\u002Fli>\n\u003Cli>Scroll to see the page rendered with all the themes you selected.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>You’ll see your page load with different themes in a bunch of iframes for handy preview and debugging.\u003C\u002Fp>\n\u003Cp>A nice list of popular themes to test:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>wp theme install \\\u003Cbr \u002F>\n  astra \\\u003Cbr \u002F>\n  colormag \\\u003Cbr \u002F>\n  customizr \\\u003Cbr \u002F>\n  generatepress \\\u003Cbr \u002F>\n  hestia \\\u003Cbr \u002F>\n  hueman \\\u003Cbr \u002F>\n  oceanwp \\\u003Cbr \u002F>\n  shapely \\\u003Cbr \u002F>\n  storefront \\\u003Cbr \u002F>\n  sydney \\\u003Cbr \u002F>\n  twentyeleven \\\u003Cbr \u002F>\n  twentyfifteen \\\u003Cbr \u002F>\n  twentyfourteen \\\u003Cbr \u002F>\n  twentynineteen \\\u003Cbr \u002F>\n  twentyseventeen \\\u003Cbr \u002F>\n  twentysixteen \\\u003Cbr \u002F>\n  twentyten \\\u003Cbr \u002F>\n  twentythirteen \\\u003Cbr \u002F>\n  twentytwelve \\\u003Cbr \u002F>\n  vantage\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>See docs for \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Fcli\u002Fcommands\u002Ftheme\u002Finstall\u002F\" rel=\"nofollow ugc\">wp theme install\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsimison\u002Fback-to-the-theme\" rel=\"nofollow ugc\">Plugin’s source code on GitHub\u003C\u002Fa>.\u003C\u002Fp>\n","See a page with different themes all at once, just like that!",10,1687,"2019-03-01T22:26:00.000Z","5.1.22","4.6",[20,21,23,94],"themes","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fback-to-the-theme.zip",{"slug":98,"name":99,"version":100,"author":101,"author_profile":102,"description":103,"short_description":104,"active_installs":88,"downloaded":105,"rating":106,"num_ratings":107,"last_updated":108,"tested_up_to":72,"requires_at_least":109,"requires_php":110,"tags":111,"homepage":114,"download_link":115,"security_score":61,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"development-assistant","Development Assistant","1.2.10","OMG!PRESS","https:\u002F\u002Fprofiles.wordpress.org\u002Fomgpress\u002F","\u003Cp>Development Assistant is a comprehensive toolkit designed to streamline the development process and enhance support capabilities within WordPress. Whether you’re a seasoned developer or a novice WordPress user, this plugin provides essential functionalities to manage debugging, diagnose issues, and facilitate smoother development workflows.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Debugging Made Easy:\u003C\u002Fstrong> Enable WP_DEBUG, WP_DEBUG_LOG, and WP_DEBUG_DISPLAY modes directly from the WordPress admin panel without the need to manually edit the wp-config.php file. Effortlessly toggle these settings to facilitate efficient debugging and error tracking.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Create Support User in One Click:\u003C\u002Fstrong> Create a support user with a single click to provide temporary access to your WordPress environment. This feature simplifies the process of sharing debugging information with developers or support teams, enabling them to diagnose and resolve issues more effectively. You can control after how many days the user will be auto-deleted. After creating a user, you can quickly copy the credentials to the clipboard, or share them via email (optionally adding a message).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Plugin Conflict Resolution:\u003C\u002Fstrong> Simplify the process of identifying and resolving plugin conflicts. Quickly compare the performance of active and inactive plugins, and temporarily disable or enable plugins to isolate issues without disrupting your entire plugin ecosystem.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SMTP Testing with MailHog:\u003C\u002Fstrong> Seamlessly integrate MailHog for SMTP testing purposes. Verify the functionality of email delivery within your WordPress environment, ensuring reliable communication with users and clients.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Download Plugins:\u003C\u002Fstrong> Download plugins directly from the WordPress admin panel’s plugin view. Streamline your workflow by easily obtaining plugin files for offline storage, manual installation, or testing in other environments and sandboxes. This feature facilitates seamless testing of plugins in various environments, allowing for thorough evaluation and development iterations.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Reset:\u003C\u002Fstrong> Effortlessly undo any changes made by the plugin to restore your WordPress environment to its original state. This feature deletes all plugin settings and data from the database, resets debug constants to their pre-activation states, deletes the debug.log file (if it didn’t exist before activation), and activates any temporarily deactivated plugins.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Who Can Benefit\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Power Developers:\u003C\u002Fstrong> Streamline your development workflow with a comprehensive toolkit tailored for debugging and issue resolution. Enhance productivity and efficiency while tackling complex WordPress projects.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Novice Users:\u003C\u002Fstrong> Empower yourself to diagnose and troubleshoot WordPress issues with ease. Quickly share debugging information with developers or support teams to expedite issue resolution and enhance your WordPress experience.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Development Assistant is your go-to solution for simplifying WordPress development tasks and enhancing support capabilities. Whether you’re troubleshooting intricate issues or optimizing your development workflow, this plugin equips you with the tools you need for success.\u003C\u002Fp>\n","Toolkit for debugging and customer support.",2056,60,2,"2025-10-08T01:06:00.000Z","5.0.0","7.4.0",[20,21,112,113,23],"manager","support","https:\u002F\u002Fomgpress.com\u002Fdevelopment-assistant","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdevelopment-assistant.1.2.10.zip",{"slug":117,"name":118,"version":119,"author":120,"author_profile":121,"description":122,"short_description":123,"active_installs":124,"downloaded":125,"rating":13,"num_ratings":126,"last_updated":127,"tested_up_to":72,"requires_at_least":128,"requires_php":18,"tags":129,"homepage":95,"download_link":133,"security_score":61,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"debug-this","Debug This","0.6.7","Razvan Aldea","https:\u002F\u002Fprofiles.wordpress.org\u002Fraldea89\u002F","\u003Cp>For admins, developers, and support staff, \u003Cstrong>Debug This\u003C\u002Fstrong> provides a ton of information about your WordPress installation, all from the front-end admin bar.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>The current WP_Query object\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>Blog info and options\u003C\u002Fli>\n\u003Cli>Embed providers\u003C\u002Fli>\n\u003Cli>Files in rendered HTML (CSS, images, JavaScript)\u003C\u002Fli>\n\u003Cli>Filters and actions\u003C\u002Fli>\n\u003Cli>Images sizes\u003C\u002Fli>\n\u003Cli>Globals and constants\u003C\u002Fli>\n\u003Cli>Menus\u003C\u002Fli>\n\u003Cli>Object cache stats\u003C\u002Fli>\n\u003Cli>Plugins, must-use plugins, and dropins\u003C\u002Fli>\n\u003Cli>Rewrite rules\u003C\u002Fli>\n\u003Cli>Queries\u003C\u002Fli>\n\u003Cli>PHP and server information\u003C\u002Fli>\n\u003Cli>Post attachments\u003C\u002Fli>\n\u003Cli>Post types\u003C\u002Fli>\n\u003Cli>Scripts and styles enqueued\u003C\u002Fli>\n\u003Cli>Shortcodes\u003C\u002Fli>\n\u003Cli>Sidebars and widgets\u003C\u002Fli>\n\u003Cli>Taxonomies and terms\u003C\u002Fli>\n\u003Cli>Themes\u003C\u002Fli>\n\u003Cli>Users\u003C\u002Fli>\n\u003Cli>WP cron schedules and jobs\u003C\u002Fli>\n\u003Cli>WP debug log\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Debug This\u003C\u002Fstrong> helps you save time and effort when trying to figure out what’s going on. Instead of hardcoding debug snippets or writing complex unit\u003Cbr \u002F>\ntests for small functionality, you can simply bring to the surface what you need right from the admin bar.\u003C\u002Fp>\n\u003Cp>For example, when viewing a single post, you can see:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>a list of post attachments,\u003C\u002Fli>\n\u003Cli>which menus and sidebars are being displayed,\u003C\u002Fli>\n\u003Cli>the post type, post fields, and meta data,\u003C\u002Fli>\n\u003Cli>the current query variables and query string,\u003C\u002Fli>\n\u003Cli>the rewrite rules applied,\u003C\u002Fli>\n\u003Cli>the author,\u003C\u002Fli>\n\u003Cli>the terms,\u003C\u002Fli>\n\u003Cli>and much more.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Extend\u003C\u002Fh3>\n\u003Ch4>Debug This Functions\u003C\u002Fh4>\n\u003Cp>New debug modes can be created easily:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_debug_extension(\n    $mode,\n    $menu_label,\n    $description,\n    $callback,\n    $group = 'General'\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Example\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_debug_extension(\n    'actions',\n    __('Actions', 'debug-this'),\n    __('$wp_actions contains all active registered actions', 'debug-this'),\n    'foo_callback',\n    'Filters And Actions'\n);\nfunction foo_callback($buffer, $template){\n    global $wp_actions;\n    $debug = print_r($wp_actions, true);\n    return $debug;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can add links to the header of a debug mode page. Place this code within your debug callback function.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_debug_header_link('http:\u002F\u002Furltolink', 'Link Label');\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Extensions can be removed as well using \u003Ccode>remove_debug_extension($mode);\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>No PRE Tags\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If you don’t want your debug output to be enclosed in PRE tags, simply set the following in your extension:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Debug_This::$no_pre = true;\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Saved Queries and Execution Time\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Retrieve saved queries and execution time by using the following static properties:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>Debug_This::$execution_time\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>Debug_This::$queries\u003C\u002Fcode> – SAVEQUERIES must defined as true\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>URL Helpers\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>Debug_This::get_current_debug_url()\u003C\u002Fcode> – current URL with the debug query\u003C\u002Fli>\n\u003Cli>\u003Ccode>Debug_This::get_escape_url()\u003C\u002Fcode> – used for the debug escape link that links to original page URL\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>WP Actions\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ccode>debug_this\u003C\u002Fcode> – receives the $mode arg – outputs the debug code sent from the extension modes. The default action is set to priority 5. This allows you to prepend or append any output without conflict using less or greater priorities.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>WP Filters\u003C\u002Fh4>\n\u003Cp>There are a few filters you can use to customize Debug This to your needs:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>debug_this_template\u003C\u002Fcode> – receives $template arg – Use your own template\u003C\u002Fli>\n\u003Cli>\u003Ccode>debug_this_default_mode\u003C\u002Fcode>  – receives $mode arg – Alters the mode for the parent DT admin bar button link.\u003C\u002Fli>\n\u003Cli>\u003Ccode>debug_this_output\u003C\u002Fcode> – receives $output, $mode args – Filter debug content before it’s rendered\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>JavaScript\u003C\u002Fh4>\n\u003Cp>To access the built-in Debug This JS functionality, enqueue your custom script with the dependency set to \u003Ccode>debug-this\u003C\u002Fcode>. Your script will inherit a jQuery dependency.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Object: debugThis\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>debugThis.mode\u003C\u002Fcode> – current mode\u003C\u002Fli>\n\u003Cli>\u003Ccode>debugThis.defaultMode\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>debugThis.template\u003C\u002Fcode> – current included template\u003C\u002Fli>\n\u003Cli>\u003Ccode>debugThis.queryVar\u003C\u002Fcode> – the defined query string variable\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Functions:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>isDebug()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>getDebugMode()\u003C\u002Fcode> – uses \u003Ccode>isDebug()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Events:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>A jQuery \u003Ccode>debug-this\u003C\u002Fcode> event is fired from the footer. You can hook into this event with the following;\u003C\u002Fp>\n\u003Cpre>\u003Ccode>jQuery(document).bind('debug-this', function(event, debugThis){\n    console.log(debugThis);\n});\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Helper Functions\u003C\u002Fh4>\n\u003Cp>There are three included functions to help you work with files.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>debug_this_get_file_ownership($file)\u003C\u002Fcode> – returns \u003Ccode>array('name' => $name, 'group' => $group)\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>debug_this_get_file_perms($file)\u003C\u002Fcode> – returns string – Example: 0775\u003C\u002Fli>\n\u003Cli>\u003Ccode>debug_this_convert_perms_to_rwx($perms)\u003C\u002Fcode> – returns string – converts permission number to RWX format – Example: 0755 folder becomes drwxr-xr-x\u003C\u002Fli>\n\u003C\u002Ful>\n","Peek under the hood with sixty debugging reports just one click away.",2000,158436,17,"2025-06-04T08:56:00.000Z","5.2",[20,130,131,132,22],"debugger","developer","hooks","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-this.0.6.7.zip",{"attackSurface":135,"codeSignals":278,"taintFlows":304,"riskAssessment":305,"analyzedAt":310},{"hooks":136,"ajaxHandlers":274,"restRoutes":275,"shortcodes":276,"cronEvents":277,"entryPointCount":28,"unprotectedCount":28},[137,143,148,153,156,162,165,170,173,178,182,185,190,194,196,199,201,203,208,210,213,217,221,224,226,230,234,237,242,246,249,252,256,260,265,270],{"type":138,"name":139,"callback":140,"file":141,"line":142},"action","plugins_loaded","sfabt_plugin_init","sf-adminbar-tools.php",23,{"type":138,"name":144,"callback":145,"file":146,"line":147},"admin_notices","print_notice","src\\class-sfabt-requirements-check.php",142,{"type":138,"name":149,"callback":150,"file":151,"line":152},"admin_menu","add_tests_menu_item","src\\classes\\AdminUI.php",76,{"type":138,"name":149,"callback":154,"file":151,"line":155},"add_all_settings_menu_item",77,{"type":138,"name":157,"callback":158,"priority":159,"file":160,"line":161},"admin_enqueue_scripts","enqueue_assets",999,"src\\classes\\Assets.php",50,{"type":138,"name":163,"callback":158,"priority":159,"file":160,"line":164},"wp_print_styles",51,{"type":138,"name":166,"callback":167,"file":168,"line":169},"load-post.php","maybe_disable_autosave","src\\classes\\DisableWPFeatures.php",45,{"type":138,"name":171,"callback":167,"file":168,"line":172},"load-post-new.php",46,{"type":174,"name":175,"callback":176,"priority":88,"file":168,"line":177},"filter","update_post_metadata","dont_set_post_lock",48,{"type":174,"name":179,"callback":180,"file":168,"line":181},"show_post_locked_dialog","__return_false",49,{"type":138,"name":144,"callback":183,"file":168,"line":184},"disable_autosave_notice",94,{"type":138,"name":186,"callback":187,"priority":34,"file":188,"line":189},"sfabt_add_nodes_inside","add_nodes","src\\classes\\DisplayData\\AdminHooks\\NodesUI.php",41,{"type":138,"name":191,"callback":187,"priority":28,"file":192,"line":193},"admin_bar_menu","src\\classes\\DisplayData\\BaseItems\\NodesUI.php",32,{"type":138,"name":186,"callback":187,"priority":34,"file":195,"line":193},"src\\classes\\DisplayData\\CurrentScreen\\NodesUI.php",{"type":138,"name":186,"callback":187,"priority":34,"file":197,"line":198},"src\\classes\\DisplayData\\Debug\\NodesUI.php",34,{"type":138,"name":186,"callback":187,"priority":34,"file":200,"line":193},"src\\classes\\DisplayData\\Pagenow\\NodesUI.php",{"type":138,"name":186,"callback":187,"priority":34,"file":202,"line":193},"src\\classes\\DisplayData\\PhpMemory\\NodesUI.php",{"type":174,"name":204,"callback":205,"priority":34,"file":206,"line":207},"sfabt_displayable_vars","add_wp_query","src\\classes\\DisplayData\\SomeVar\\Data.php",33,{"type":174,"name":204,"callback":209,"priority":34,"file":206,"line":198},"add_profile_data",{"type":174,"name":204,"callback":211,"priority":34,"file":206,"line":212},"add_user_data",35,{"type":174,"name":214,"callback":215,"priority":34,"file":216,"line":161},"sfabt_localize_script","localize_script","src\\classes\\DisplayData\\SomeVar\\NodesUI.php",{"type":138,"name":218,"callback":219,"file":216,"line":220},"admin_print_footer_scripts","print_lightbox_template",53,{"type":138,"name":222,"callback":219,"file":216,"line":223},"wp_print_footer_scripts",55,{"type":138,"name":186,"callback":187,"file":216,"line":225},58,{"type":138,"name":227,"callback":228,"file":216,"line":229},"init","dispatch_guide",59,{"type":138,"name":231,"callback":232,"priority":28,"file":216,"line":233},"admin_init","maybe_print_value",148,{"type":138,"name":235,"callback":232,"priority":28,"file":216,"line":236},"wp",150,{"type":138,"name":238,"callback":239,"priority":88,"file":240,"line":241},"all","store_template_parts","src\\classes\\DisplayData\\Templates\\Data.php",70,{"type":174,"name":243,"callback":244,"file":240,"line":245},"comments_template","store_comments_template",71,{"type":138,"name":186,"callback":187,"priority":247,"file":248,"line":223},1,"src\\classes\\DisplayData\\Templates\\NodesUI.php",{"type":138,"name":186,"callback":250,"priority":247,"file":248,"line":251},"add_template_part_nodes",56,{"type":138,"name":227,"callback":253,"priority":247,"file":254,"line":255},"init_context","src\\classes\\Plugin.php",109,{"type":174,"name":257,"callback":258,"file":254,"line":259},"sfabt_container","closure",203,{"type":138,"name":261,"callback":262,"file":263,"line":264},"load-profile.php","add_settings_fields","src\\classes\\ProfileUI.php",66,{"type":138,"name":266,"callback":267,"priority":268,"file":263,"line":269},"show_user_profile","show_user_fields",11,67,{"type":138,"name":271,"callback":272,"file":263,"line":273},"personal_options_update","update_user_options",68,[],[],[],[],{"dangerousFunctions":279,"sqlUsage":287,"outputEscaping":290,"fileOperations":301,"externalRequests":28,"nonceChecks":107,"capabilityChecks":302,"bundledLibraries":303},[280,285],{"fn":281,"file":282,"line":283,"context":284},"preg_replace(\u002Fe)","src\\classes\\Dependencies\\Composer\\Installers\\MicroweberInstaller.php",113,"preg_replace('\u002Fe",{"fn":281,"file":282,"line":286,"context":284},115,{"prepared":288,"raw":28,"locations":289},15,[],{"escaped":142,"rawEcho":291,"locations":292},3,[293,297,300],{"file":294,"line":295,"context":296},"src\\classes\\Traits\\TemplateEngineTrait.php",122,"raw output",{"file":298,"line":299,"context":296},"src\\functions\\debug.php",37,{"file":298,"line":269,"context":296},9,4,[],[],{"summary":306,"deductions":307},"The sf-adminbar-tools v4.0 plugin exhibits a generally strong security posture based on the provided static analysis and vulnerability history. The absence of any known CVEs, coupled with a clean vulnerability history, is a significant positive indicator.  The code heavily relies on prepared statements for SQL queries and demonstrates a high percentage of properly escaped output, which are crucial best practices for preventing common web vulnerabilities.\n\nHowever, there are a few areas that warrant attention. The presence of two 'dangerous functions' (preg_replace(\u002Fe)) indicates a potential for remote code execution if these functions are used with user-supplied input that is not properly sanitized. While the taint analysis shows no flows with unsanitized paths, the potential for misuse of these functions remains a concern. The limited attack surface and the presence of nonce and capability checks on the few entry points are good, but the absence of any taint analysis data (0 flows analyzed) means we cannot definitively rule out subtle issues that might not be flagged by static checks alone.\n\nOverall, sf-adminbar-tools v4.0 appears to be a well-maintained plugin with a strong foundation in secure coding practices. The lack of past vulnerabilities is a testament to this. The primary area for improvement lies in carefully reviewing the implementation of the `preg_replace(\u002Fe)` functions to ensure robust sanitization of any input processed by them. Until this is confirmed, a minor level of caution is advised.",[308],{"reason":309,"points":88},"Dangerous function detected (preg_replace(\u002Fe))","2026-03-16T19:49:19.716Z",{"wat":312,"direct":327},{"assetPaths":313,"generatorPatterns":318,"scriptPaths":319,"versionParams":324},[314,315,316,317],"\u002Fwp-content\u002Fplugins\u002Fsf-adminbar-tools\u002Fassets\u002Fcss\u002Fsfabt.css","\u002Fwp-content\u002Fplugins\u002Fsf-adminbar-tools\u002Fassets\u002Fcss\u002Fsfabt.min.css","\u002Fwp-content\u002Fplugins\u002Fsf-adminbar-tools\u002Fassets\u002Fjs\u002Fsfabt.js","\u002Fwp-content\u002Fplugins\u002Fsf-adminbar-tools\u002Fassets\u002Fjs\u002Fsfabt.min.js",[],[320,321,322,323],"assets\u002Fcss\u002Fsfabt.css","assets\u002Fcss\u002Fsfabt.min.css","assets\u002Fjs\u002Fsfabt.js","assets\u002Fjs\u002Fsfabt.min.js",[325,326],"sf-adminbar-tools\u002Fassets\u002Fcss\u002Fsfabt.css?ver=","sf-adminbar-tools\u002Fassets\u002Fjs\u002Fsfabt.js?ver=",{"cssClasses":328,"htmlComments":329,"htmlAttributes":330,"restEndpoints":331,"jsGlobals":332,"shortcodeOutput":334},[],[],[],[],[333],"sfabtContext",[]]