My WP Customize Admin/Frontend vs Query Monitor

My WP Customize is customize for WordPress. Simply and easy-to-use the customize for Admin and Frontend. A lot of custom filters and actions, and included the developer tools. There are lots of custom actions and filters. You will speed up to your site creation. Debug on current post, Debug on current using theme, Debug on server info, …etc more helpful info. The demo site is here: https://playground.wordpress.net/?plugin=my-wp&url=/wp-admin/admin.php?page=mywp Customize the admin Admin General(hide update notifications, hide screen options, custom footer text). Admin Dashboard(hide meta boxes, change meta box title, restrict meta box order). Admin Sidebar(hide menus, order menus, change icon and title, add custom link menu). Admin Toolbar(hide menus, order menus, change icon and title, add custom link menu). Admin Post list(hide columns, order columns, change title). Admin Post edit(support block editor and classic editor, hide meta boxes, change title placeholder, restrict order meta box). Admin Terms(hide columns, order columns, change title). Admin Media uploads(hide columns, order columns, change title). Admin Comments(hide columns, order columns, change title). Admin Users(hide columns, order columns, change title). Admin User edit(hide Visual Editor checkbox, hide Syntax Highlighting checkbox, hide Admin Color Scheme). Admin Site editor(Change top left button). Admin Nav menus(hide meta boxes, hide Link target, hide Title Attribute, hide CSS classes). Customize the frontend Frontend General(show and hide toolbar, hide Rest link, hide Shortlink, set X-Frame-Options, add custom header meta). Frontend Author archive(hide archive page, add Disallow to robots.txt). Frontend Date archive(hide archive page). Frontend Taxonomy archive(hide archive page). Frontend Toolbar(hide menus, order menus, change icon and title, add custom link menu). Customize the login Login General(Change logo link and image, hide select language, add custom footer text). Login User(redirect after login and logout). Customize the website Site General(Disable file edit, hide PHP X-Mailer version). Site Post type(Change create_posts capability). Site Sitemap(hide core sitemap.xml). For Debug Debug General(Display a debug screen that is useful for development). Debug Blogs(Show all blogs on network/multisite). Debug Crons(Show all crons). Debug Date time(Show all date and time values). Debug Defines(Show all defines). Debug Post statuses(Show all post statuses). Debug Post structure(Show a post structure). Debug Post types(Show all post types). Debug Rest API(Show all rest api). Debug Site options(Show all site options on network/multisite). Debug Taxonomies(Show all taxonomies). Debug Terms(Show all terms). Debug transients(Show all transients). Debug translations(Show all translations). Debug Capabilities(Show all user roles capabilities).

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. 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. 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. Query Monitor supports versions of WordPress up to three years old, and PHP version 7.4 or higher. For complete information, please see the Query Monitor website. Here’s an overview of what’s shown for each page load: Database queries, including notifications for slow, duplicate, or erroneous queries. Allows filtering by query type (SELECT, UPDATE, DELETE, etc), responsible component (plugin, theme, WordPress core), and calling function, and provides separate aggregate views for each. 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). PHP errors presented nicely along with their responsible component and call stack, and a visible warning in the admin toolbar. Usage of “Doing it Wrong” or “Deprecated” functionality in the code on your site. Blocks and associated properties within post content and within full site editing (FSE). Matched rewrite rules, associated query strings, and query vars. Enqueued scripts and stylesheets, along with their dependencies, dependents, and alerts for broken dependencies. Language settings and loaded translation files (MO files and JSON files) for each text domain. HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests. User capability checks, along with the result and any parameters passed to the capability check. Environment information, including detailed information about PHP, the database, WordPress, and the web server. The values of all WordPress conditional functions such as is_single(), is_home(), etc. Transients that were updated. Usage of switch_to_blog() and restore_current_blog() on Multisite installations. In addition: 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. 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. 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 an enveloped REST API request will include even more debugging information in the qm property of the response. By default, Query Monitor’s output is only shown to Administrators on single-site installations, and Super Admins on Multisite installations. 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. Browser extension Query Monitor is also available as an optional browser dev tools extension. This is an alternative to using the in-page panel that gets output into the admin toolbar. Using the browser extension has some advantages over the in-page panel: The Query Monitor panel doesn’t take up space within the page you are inspecting The panel can be resized, undocked, and moved around like any other developer tools panel Information about the Query Monitor browser extension can be found here. Other Plugins I maintain several other plugins for developers. Check them out: User Switching provides instant switching between user accounts in WordPress. WP Crontrol lets you view and control what’s happening in the WP-Cron system Thanks The time that I spend maintaining this plugin and others is in part sponsored by: Automattic ServMask WP Staging All my kind sponsors on GitHub Privacy Statement 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. Query Monitor’s full privacy statement can be found here. Accessibility Statement Query Monitor aims to be fully accessible to all of its users. Query Monitor’s full accessibility statement can be found here.