Settings

General

• Developer Accounts: Add user accounts that should see errors, receive fatal error notifications, and have access to special features.
• Developer Timezone: Changes the timezone on Debug Log viewer and other areas in the plugin. Default is what the site uses.
• Developer Time Format: Changes the time format on Debug Log viewer and other areas in the plugin. Default is F j, Y g:i a T.
• Open Nav Links in New Tab: When navigating to a different page in the plugin from the dropdown navigation at the top right of the page, enabling this opens the link in a new tab.

Logging Options

• Disable Error Counts: Disabling this will prevent repeated counting and improve page load time for developers (developers are the only ones that see the count). Keeping it enabled during initial development is very helpful, but after launch it might be worth turning off.
• Max Log Size (MB): Set the maximum size for log files. Default is 10 MB. When a log file exceeds this size, we will not attempt to load it. Set to 0 for unlimited size (not recommended).
• Log Backtrace for Deprecations: Log the stack trace for any deprecated function calls. This can add up quickly, so it's only recommended temporarily while you're debugging.
• Log Backtrace for Notices: Log the stack trace whenever a PHP notice occurs. This can add up quickly, so it's only recommended temporarily while you're debugging.
• Log Backtrace for Warnings: Log the stack trace whenever a PHP warning occurs. This can add up quickly, so it's only recommended temporarily while you're debugging.
• Log Backtrace for Errors: Log the stack trace whenever a PHP warning occurs. This can add up quickly, so it's only recommended temporarily while you're debugging.
• Log WP Mail Failures: Does what it says, but only when debugging is enabled.
• Enable Discord Webhook for Fatal Errors: If you want to receive notifications of fatal errors in Discord, enable this option.
• Discord Webhook for Fatal Errors: Send notifications to a Discord Webhook when a fatal error occurs. Webhook URL should look like this: https://discord.com/api/webhooks/xxx/xxx

Paths

• Debug Log Path: The path to the debug.log file. This is usually in the wp-content directory.
• Error Log Path: The path to the error.log file. This is usually in the root directory.
• Admin Error Log Path: The path to the admin error.log file. This is usually in the wp-admin directory.
• Log Files to Check: You can add additional .TXT files to the Logs tab.
• Additional Log Files: We automatically check your debug.log, error_log, and admin error_log. If you have additional local logs you would like to view on the Logs page, enter the root paths to the files here (not including the domain).

Activity Log

• Enable Activity Logs: Select the types of activity you want to log to the activity log. Log can be viewed on the Activity tab. Activities include: Users Logging In, Updating User Meta, Creating Accounts, Deleting Accounts, Updating User Roles, Creating Posts & Pages, Updating Posts & Pages, Deleting Posts & Pages, Changing Post Statuses, Visiting Posts & Pages, Bots Crawling Posts & Pages, Activating Plugins, Updating Plugins, Deactivating Plugins, Deleting Plugins, Switching Themes, Updating Themes, Updating Site Settings, Failed Login Attempts, and Resetting Passwords.
• Skip User Meta Keys: Enter user meta keys (comma-separated) to exclude from the activity log. Use asterisks (*) as wildcards for prefixes or suffixes. For example, "wp_*" excludes all keys starting with "wp_". Suggested: session_tokens, user_activation_key, wpfv_user_level, _transient_*, wp_persisted_preferences
• Skip Post Meta Keys: Enter post meta keys (comma-separated) to exclude from the activity log. Use asterisks (*) as wildcards for prefixes or suffixes. For example, "wp_*" excludes all keys starting with "wp_".
  Suggested: ID, post_modified, post_modified_gmt, filter, _edit_lock, _edit_last, _wp_desired_post_slug, _encloseme, _wp_trash*, _transient_*, _yoast*, wp_page_template
• Skip Setting/Option Keys: Enter options (comma-separated) to exclude from the activity log. Use asterisks (*) as wildcards for prefixes or suffixes. For example, "wp_*" excludes all options starting with "wp_".
  Suggested: cron, rewrite_rules, recently_edited, _site_transient_*, _transient_*

Config Files

The WP-Config Cleaner and HTACCESS Cleaner tools are located in the Raw Editors of each file, and let you tidy up the code with a single click. The options below control what gets cleaned. After running the cleaner, you can cancel editing if needed, so test freely and turn off any options you don’t want.

WP-Config Cleaner

• Update DDT Section: For users upgrading from a version prior to 3.0, this option will relocate the old snippet section into its new standard position above "That's all, stop editing!", remove the legacy wrapper comments, and unify the comment format. After the initial cleanup, you can disable this option if desired, though leaving it on will not cause issues.
• Simplify Database Settings: Removes unnecessary MySQL configuration comments and formatting for a cleaner wp-config.php layout, while keeping the functional settings intact.
• Minimize Auth Key Comments: Condenses the default comment blocks that surround the authentication keys and salts section.
• Improve ABSPATH Definition: Reformats the ABSPATH setting at the end of wp-config.php for clarity and consistency, ensuring the conditional check is optimized by always using braces.
• Remove Double Blank Lines: Collapses any unnecessary double line breaks in wp-config.php so that spacing remains compact but still readable.
• Format Parentheses and Brackets: Adjusts the formatting of wp-config.php to add consistent spacing inside parentheses and brackets for better readability.
• Convert Multi-line Comments: Changes any multi-line style comments into a standardized /** ... */ single-line format to unify the code style throughout wp-config.php.

HTACCESS Cleaner

• Update DDT Section: For users upgrading from a version prior to 3.0, this option will remove the legacy wrapper comments. After the initial cleanup, you can disable this option if desired, though leaving it on will not cause issues.
• Move All Code from Top: Relocates all code blocks at the top of the .htaccess file down below the # BEGIN WordPress - END WordPress section.
• Minimize Begin End Comments: Removes the unnecessary comments explaining that the lines between "BEGIN WordPress" and "END WordPress" are for the WordPress core and should not be modified. Also removes any spaces between the anchors comments.
• Remove Double Comment Hashes: Collapses any unnecessary double hash marks (##) to a single hash mark (#) for cleaner comments.
• Remove Double Blank Lines: Collapses any unnecessary double line breaks so that spacing remains compact but still readable.
• Remove Spaces at Top and Bottom: Removes any extra spaces at the beginning and end of the file for a cleaner look.
• Add Line Breaks Between Blocks: Adds a single line break between code blocks for improved readability.

Metadata

• Protected Meta Keys: Enter meta keys (comma-separated) to protect from being deleted. Use asterisks (*) as wildcards for prefixes or suffixes. For example, "wp_*" protects all keys starting with "wp_".
• Add or Override an Object: Use this form to import a single object using a JSON file. You can download an object from the relative object managers to get a sense of what the structure should look like.

Hearbeat

• Enable Heartbeat Monitoring: Monitor the WordPress Heartbeat API activity and performance in your console across all pages.
• Disable Heartbeat Everywhere: Completely disable the WordPress Heartbeat API on both frontend and admin. Useful if you suspect Heartbeat is causing server load or 503 errors.
• Disable Heartbeat in Admin: Stop Heartbeat API requests in the WordPress admin area only. Auto-saves and post lock features will not work.
• Disable Heartbeat on Frontend: Stop Heartbeat API requests on the frontend for logged-in users.

Online Users

These settings control the Online Users feature, which adds an indicator to the admin bar and a column to the users admin list showing who is currently online. The admin bar indicator is only shown to administrators and only checks for users when you load the page. It also caches the results for 60 seconds to improve performance, so a new online user may not show online immediately. If you are seeing a lag from high traffic, try increasing the time frame, minimizing the roles tracked, disabling heartbeat if enabled, or disabling the feature entirely.

• Show Online Users: Adds an indicator to the admin bar that lists all currently online (logged-in) users. This does not show logged-out users. It also adds an admin list column to your Users list table that shows if the user is currently online or the last time they were.
• Last Seen Window (Minutes): Consider users "online" if they’ve been active within this time window.
• Enable Heartbeat: Keep track of the online users that match the "Roles to Monitor via Heartbeat" in real-time. Not advisable if you are tracking a lot of users at the same time. We use it only to track administrators and important roles that only have a handful of people.
• Heartbeat Interval (Minutes): Frequency for AJAX heartbeats to confirm users are still online. Default is 1.
• User Link URL: Link online users in the admin bar. Merge tags are available to use in the URL: {user_id}, {user_email}ie. https://yourdomain.com/wp-admin/user-edit.php?user_id={user_id}. Defaults to user profile edit page.
• Roles to Track on Page Load: Select the roles you want to track on page load.
• Roles to Monitor via Heartbeat: Logs these roles still on a page via AJAX every X minutes (defined above). Recommended for admins only or low-traffic sites.
• Roles to Prioritize on Top: This will move users with these roles to the top of the list so you can keep an eye on them rather than looking through the alphabetical list.
• Enable Discord Webhook for Logins: If you want to receive notifications of logins in Discord, enable this option.
• Discord Webhook for Logins: Send notifications to a Discord Webhook when users log in. Webhook URL should look like this: https://discord.com/api/webhooks/xxx/xxx...

Admin Bar

• Remove WordPress Logo: Removes the WordPress logo on the top left of the admin bar. Who needs that, really?
• Add Log Error Count: Add the total number of errors in your logs to the admin bar.
• Add Resources Menu: Add a Resources menu to the admin bar with links to useful resources.
• Remove Gravity Form Finder (if Gravity Forms is installed): The plugin adds a form finder that displays links to forms on the pages on the front-end. Helpful to jump to the form if there are issues. Some websites have reported this as not working as expected.
• Add My User ID: Display your User ID in the admin bar instead of "Howdy," for quick reference.
• Add Page Loaded Time: Display the time it took to load the current page as well as loaded date and time in the admin bar.
• Condense Admin Bar Items: This removes the words from core and commonly used admin bar menu items to help condense it down when you have a lot of things on there.
• Add Links to Admin Bar: Adds admin menu links to the admin bar under the dashboard icon. The links are automatically detected when enabled on the next page load. Links are added and removed automatically when plugins are activated/deactivated. Clicking the "Refresh Links" button will restart the detection process and start fresh, which is really only useful if you're having problems with the list showing up properly. If there are broken links, you can use the ddtt_​admin_​menu_​special_​urls hook to modify them. Additional links can also be added via the ddtt_​admin_​bar_​dropdown_​links hook.
• Add Post ID, Post Type, and Post Status: Display the Post ID, Post Type, and Post Status in the admin bar for quick reference.
• Add Shortcodes Finder: Add a Shortcodes finder to the admin bar for quick reference to shortcodes used on the page.
• Gravity Forms Finder: Add a Gravity Forms finder to the admin bar for quick access to forms.
• Add Centering Tool: Add a centering tool to the admin bar for easier alignment of elements on the page. By default, a centering tool has been added to the admin bar on the front end of your site to assist you with lining up content on the page. When you click on the ✛ Offlink, it will add a grid to the top of the page underneath the admin bar. If you click this grid, it will expand down the page. Click it again to retract it. You can change the grid in the admin bar settings when you hover the centering tool link.

Admin Area

• User ID Quick Links: Adds a User ID column to the Users admin list page with quick debug links for developers to debug user meta in the Metadata tool section.
• Post ID Quick Links: Adds a Post ID column to the Posts and Pages admin list page with quick debug links for developers to debug post meta in the Metadata tool section.
• Comment ID Quick Links: Adds columns for Comment ID, Comment Type and Karma to the Comments admin list page with quick debug links for developers to debug comment meta in the Metadata tool section.
• Include IDs in Admin List Table Searches: Allows searching by ID in the admin list tables.
• Include Post/Page Slugs in Admin List Tables: Displays the post/page slugs in the admin list tables.
• Plugins Page Enhancements: Adds the additional tools set below to your Plugins Page.

Plugins Page

• Size Column: Show the total folder size of each plugin.
• Path Column: Show the main plugin file path (e.g. dev-debug-tools/dev-debug-tools.php).
• Last Updated Column & Warning: Show the last modified date and time of the plugin files.
• Installed By Column: Show and edit who installed the plugin.
• Plugin Notes: Add an “Edit Notes” action link to include custom notes for each plugin.

Security

• Developer Access Only: Restrict access to the plugin for developers only.
• Hide Plugin: Hides the plugin from the left admin menu entirely and disguises it on the plugins page with the alias you set below. Requires you to access plugin area directly. We recommend bookmarking the dashboard first.
• Plugin Alias (when Hide Plugin is enabled): Set an alias for the plugin to disguise it on the plugins page. Defaults to "Developer Notifications" if not set.
• Plugin Description (when Hide Plugin is enabled): Set a description for the plugin to disguise it on the plugins page. Defaults to "Provides developer-focused system notifications." if not set.
• Plugin Author (when Hide Plugin is enabled): Set an author for the plugin to disguise it on the plugins page. Defaults to "WordPress Core Team" if not set.
• View Sensitive Information: Displays redacted database login info, authentication keys and salts, IP addresses, etc. It is recommended to keep this disabled when sharing your screen with anyone, including support.
• Enable Password Protection: Enable password protection for the Developer Debug Tools area and other specified admin pages set below.
• Password (when enabled): Set your password here.
• Keep Logged In For X Minutes: Enter the number of minutes until you have to re-enter your password.
• Attempts: Enter the number of attempts allowed before the user is locked out.
• Lockout Duration (Minutes): Enter the number of minutes the user will be locked out after exceeding the maximum attempts.
• Admin Pages to Secure with Password: All DDT pages are added to the list automatically. If you have additional admin pages you would like users to require a password for, such as the Users page, enter the URL paths here.

Plugin Data

• Export All Plugin Data: This action will download the current plugin settings as a JSON file to keep as a backup or use on a different site. This does not include the online user roles as roles are often different on each site.
• Import Plugin Data: Use this form to import plugin settings using a JSON file. Use the JSON schema provided in the download above. You may modify the JSON file to only import specific settings. Note that existing settings will be overwritten.
• Remove All Plugin Data on Uninstall: When you uninstall the plugin, all settings and data will be permanently deleted. This action cannot be undone.
• Reset All Plugin Data Now: This action will clear all plugin data for the current site to start fresh with default settings. This action cannot be undone.

Dashboard

The dashboard is new as of version 3.0, and includes data that was once in the header on every page, along with a plethora of additional data and tools to your avail.

• Navigation: At the top-right of the header there is a drop-down with the navigation links to all pages and tools in the plugin.
• ABSPATH: Displays the absolute path of the WordPress installation. This is redacted unless "View Sensitive Information" is enabled in the security settings. It is recommended to keep it redacted, and simply highlight the black area to reveal the path behind it.
• Download Important Files: This button downloads a zip file that contains your wp-config.php, .htaccess, and functions.php files. This is recommended before taking on a project that involves editing any of those files.
• Versions: Displays versions for the plugin, WordPress, PHP, MySQL, jQuery, cURL, and GD Library.
• Server Metrics: Displays the server's IP address, software type, CPU load, memory usage, and server uptime.
• Environment: Displays if Multisite is enabled, the active theme, number of active and inactive plugins, timezone, and if OPcache is enabled.
• Check for Site Issues: This section is a simple tool to check the site for issues that should be resolved before the site goes live. More issues are slated to be added in the future, but developers can also add additional checks using the ddtt_issues hook. Current checks include "Admin Email Domain Mismatch," "Site URL and Home URL Mismatch," "Plain Permalink Structure," and "Not Using Child Theme."

Tools

The Tools page was introduced in version 3.0 to centralize tool management and provide a single location where each tool is explained. Beyond serving as a navigation hub, this page also allows the following actions:

• Enabling/Disabling Tools: You can easily disable any tools that you don't use. This prevents the loading of unnecessary classes and scripts, and removes the tools from the navigation menu.
• Favoriting Tools: If you have tools that you use more than others, you might want to favorite them. To do so, just click the little heart icon on the top right of the tool container. This will add them to the admin menu in the left sidebar so they are easier to get to.
• Sorting Tools: You can also sort the tools simply by dragging and dropping them where you want on the page. Put your most used ones on top, or keep them alphabetical.

Auto Drafts (Tool)

Auto-drafts are temporary posts generated automatically when a new post is started but not yet saved. They preserve unsaved work but remain in the database if the editor is closed before saving.

This tool provides a central interface for reviewing and removing these entries. It supports bulk deletion of all auto-drafts, removal of only those older than one week, and individual cleanup. It also displays the creator, creation time, post type, and a link to inspect the associated post metadata.

Cookies (Tool)

Cookies are small text values stored in the browser to retain information about a visitor’s session and activity. They support features such as remembering preferences, maintaining sessions, and improving overall usability. They can be viewed in the browser’s developer tools under Application → Storage → Cookies → your site’s URL.

This tool allows full removal of all cookies or selective deletion of individual entries. It also provides options to set a test cookie and to automatically detect newly created cookies.

Cron Jobs (Tool)

Cron jobs are scheduled tasks that WordPress runs at specific intervals to handle automated actions such as publishing scheduled posts, running maintenance routines, processing queued tasks, or performing plugin-initiated operations. WordPress uses a simulated cron system that triggers these tasks during site activity rather than relying on a server-level scheduler.

This tool presents a structured view of all currently registered cron events, including the associated hook, any stored arguments, the recurrence pattern, the next scheduled execution time, and the action that will occur when the task runs.

For sites that need more direct control over scheduled tasks, using a dedicated tool such as the WP Crontrol plugin is advisable. It allows you to create, edit, run, and delete cron events, inspect callback functions, and diagnose issues with tasks that are not executing as expected. This level of management provides finer control than simply viewing the schedule and is useful for troubleshooting or adjusting cron behavior during development and maintenance.

Database Tables (Tool)

This tool provides a read-only view of your database tables, allowing you to inspect records without the risk of modifying or deleting data as you might in tools like phpMyAdmin. You can select any table to display its contents in an HTML table, search within the results, and quickly reference the current database name, version, and table prefix.

Defined Constants (Tool)

This tool displays all constants currently defined in your WordPress environment. Constants are fixed values set by WordPress, plugins, themes, or your configuration files, and they control behaviors ranging from debugging to file paths to performance settings. They cannot be changed at runtime, making them reliable reference points for understanding how the site is configured.

The interface allows you to search or select a constant to view its category and value, giving you a clear snapshot of what is active and how various parts of the system are set up.

Discord Messenger (Tool)

Discord is an online communication platform where you can create a free account and set up “servers,” which function as private or shared spaces containing text and voice channels. Servers can be used by a team, a community, or just a single user who wants a secure, personal area for notifications.

Using Discord as a notification channel is an effective alternative to email, especially for critical events like fatal errors. Email delivery can fail due to hosting limits, spam filtering, or mail configuration issues, while Discord webhooks provide a more direct and reliable way to receive alerts in real time. You can create a server that only you have access to or set up a private channel inside an existing server. In the Developer Debug Tools’ logging settings, you can enable Discord error notifications and enter a webhook URL.

To create a webhook in Discord, open your server settings, navigate to the Integrations section, select Webhooks, create a new webhook, choose the channel where alerts should appear, and copy the generated URL. This URL can then be added to the plugin settings.

This tool lets you send a test message to ensure your webhook is set up correctly without needing to trigger an actual fatal error. It provides fields for the webhook URL along with all message details, allowing you to verify that the connection is working as expected. Or you can just use it for fun to send a message as a "Bot."

Global Variables (Tool)

Global variables are variables defined in the global scope of WordPress or PHP that can be accessed from any part of the application when explicitly referenced with the global keyword. They store shared data that multiple functions or components may need to read or modify. An example is global $menu, which contains the structure of the WordPress admin menu and can be used when determining available pages, adjusting menu items, or inspecting how plugins register their entries.

This tool provides a selectable list of available global variables and displays the contents of the chosen variable in a structured table.

HTACCESS (Tool)

The .htaccess file is an Apache configuration file used to control directory-level behavior on your server. It governs URL rewriting, redirects, caching rules, access control, and many other server directives that influence how WordPress and your hosting environment operate. Because this file is executed by the web server, even a small mistake can produce errors across your entire site.

This tool lets you view and edit the .htaccess file directly within the page. You can adjust syntax highlighting colors, download the current file for backup, switch to a raw editing view, or use the snippets interface.

• The Raw Editor contains an HTACCESS Cleaner that reformats and normalizes the file using utilities configured in the Config Files settings. When enabled, these tools simplify and tidy the structure of the file for easier reading. Edits made in the Raw Editor are lint-checked before saving; if any syntax error is detected, the save is blocked.

• The Snippets section identifies recognizable code blocks in your existing file and lets you add or remove them without manually remembering their syntax. You choose the actions you want, and the tool rewrites the file accordingly.

• Every time the file is saved, a timestamped backup is stored in the same directory as the .htaccess file. The tool provides access to these backups so you can review, restore, or delete them as needed.

⚠ WARNING! Editing your .htaccess file can break your site if you make incorrect changes or introduce syntax errors. Every site is different, so not all snippets will work for everyone. Always create a backup before making any changes. This tool checks for syntax errors and requirements before saving, but you should still review your edits carefully. If you don’t know what you’re doing here, it’s best to seek assistance or avoid modifying it.

Logs (Tool)

This tool provides a centralized interface to view, download, and clear a variety of logs, including the WordPress debug log, error_log, /wp-admin/error_log, the plugin’s own activity log, and any custom logs you have configured in the logging settings. Log file paths can be defined in the logging settings.

The log viewer offers extensive customization options:

• Easy Reader / Raw Editor: The Raw Editor displays the log as plain text without formatting. The Easy Reader parses the log into a table for easier reading, with columns for line number, date/time (using the developer’s timezone and preferred format), error type, and the error message. For the debug log, a “Help me with this error” button appears for recognized errors, providing explanations and guidance based on the help map.
• Most Recent on Bottom / Top: Sort entries in ascending or descending order by date.
• Combine Log Entries / Do Not Combine: When combined, identical errors are displayed once with a quantity counter, preventing repetitive entries from overwhelming the table.
• Recent Items Count: A dropdown allows selection of how many recent entries to display, including 1, 5, 10, 25, 50, 100, or 200 entries.
• Search & Exclude Keywords: Use the search box to filter entries containing specific keywords, or the exclude box to hide entries containing particular keywords.
• Fatal Error / Parse Error Filters: Quick links to display only fatal or parse errors in the log.

The action buttons above the customization options include Download Log and Clear Log. When debugging something, it's easier to clear the log before testing so that you don't have to wade through other old errors that do not pertain.

The Activity Log operates slightly differently. Instead of fatal/parse error filters, it uses a color-coded index for different activity types. The table includes line number, date/time, activity type, user performing the action, and notes instead of error messages.

Logs will not load if they exceed the maximum file size defined in the logging settings, ensuring performance and stability.

Metadata (Tool)

The Metadata tool provides a centralized interface for viewing and managing the metadata associated with different WordPress objects. It includes several tabs: User Meta, Post Meta, Term Meta, Comment Meta, and Media Meta.

• User Meta: Search for a user to view all metadata for that account. This includes object meta, custom meta, roles, and capabilities. You can edit object meta and custom meta that are not protected directly from the page. You can also add new custom meta entries, hide transients or UI settings in the custom meta section, and manage user roles and capabilities.
• Post Meta: Search for a post or page to view all metadata. You can edit object meta and custom meta that are not protected directly from the page. You can also manage taxonomy terms associated with the post.
• Term Meta, Comment Meta, Media Meta: Display object meta and custom meta for terms, comments, or media items. Editing and adding custom meta is supported where allowed.

All metadata tabs include options to:

• Show or hide sections of metadata.
• Search for specific metadata keys or values.
• Filter out metadata that is not relevant.

Action buttons include:

• Download Object: Exports all data for the selected object as a JSON file. This includes object meta, custom meta, roles, capabilities, taxonomies, and other associated metadata. You can later use the metadata settings to upload this JSON file to create a new object or override an existing one.
• Reset Object: Clears all custom meta for the selected object. It is recommended to download the object before resetting so you have a backup. Use with caution.

This tool consolidates metadata management into a single interface, allowing you to safely view, edit, and maintain your WordPress objects without directly interacting with the database.

PHP Info (Tool)

The PHP Info tool provides a complete overview of your server’s PHP configuration by displaying the output of the phpinfo() function. This includes essential details about your PHP environment, extensions, and settings.

Information Provided

• PHP Version and Build: The currently installed PHP version, build date, and compiler details.
• Loaded Extensions: A list of all active PHP extensions and modules, along with their configuration settings.
• Server Information: Web server software, operating system, and environment variables.
• PHP Configuration Directives: All PHP configuration options (php.ini values) and their current, local, and master settings.
• Paths and Directories: Locations of important directories, such as include paths, temporary file paths, and extension directories.
• HTTP and Server Variables: Values of global server and request variables available to PHP.

Use Cases

• Debugging: Identify missing extensions or configuration issues that could affect WordPress or plugin functionality.
• Compatibility Checks: Verify that your server meets the requirements for WordPress, themes, or plugins.
• Optimization: Review configuration settings such as memory limits, maximum execution time, and upload sizes to adjust for performance or resource needs.
• Support: Provides a detailed snapshot of your PHP environment that can be shared with developers or hosting support for troubleshooting.

This tool is read-only and does not allow changes, making it a safe way to review your PHP environment in one place.

PHP.INI (Tool)

The PHP.INI tool provides a comprehensive view of all registered PHP configuration options and their current values. It shows each directive along with its active value and the default server value, allowing you to see exactly how PHP is configured for your site. This information includes settings that affect memory limits, execution times, file uploads, and other PHP behaviors.

This tool is useful for reviewing your PHP environment to identify potential configuration issues, optimize performance, check compatibility with plugins or themes, and provide a clear overview when troubleshooting or requesting support. It presents the information in a safe, read-only format, so you can inspect all settings without risk of changing anything on your server.

Post Types (Tool)

The Post Types tool allows you to select any registered post type and view detailed information about it. This includes the post type’s settings, labels, and any taxonomies associated with it.

This tool is useful for reviewing how custom or built-in post types are configured, checking their visibility, capabilities, and labels, and understanding how they interact with taxonomies. It helps with debugging, theme or plugin development, and ensuring proper content organization on your site.

REST APIs (Tool)

The REST APIs tool displays all of the API routes available on your site. You can view each route, check its status, and access it directly in your browser.

This tool is useful for developers who need to inspect, debug, or interact with the site’s REST API endpoints. It allows you to verify that routes are working correctly, test responses, and explore the structure and data available via the API without needing external tools.

Server Info (Tool)

The Server Info tool provides detailed information about your server's CPU and memory. For the CPU, it lists specifications such as the processor model, cores, threads, clock speeds, cache sizes, supported instruction sets, and vendor information. Memory information includes total and available memory, used memory, buffers, cached memory, swap usage, and other key metrics. It also calculates memory usage as a percentage of total memory.

This tool is useful for monitoring server resources, diagnosing performance issues, and understanding the hardware and memory configuration of your hosting environment. Developers and site administrators can use it to assess system capacity, optimize performance, and plan for scaling or troubleshooting resource-related problems.

Sessions (Tool)

Sessions store data on the server to maintain state across multiple pages for the current user. Unlike cookies, session information is not stored on the user’s device but is managed server-side. On most servers, PHP session data is typically stored in a temporary directory such as /tmp.

This tool allows you to view all active sessions in a table, with the ability to clear individual sessions or all sessions at once. You can also create a new test session and automatically monitor for new sessions, making it useful for debugging user activity and ensuring proper session management.

Shortcodes (Tool)

Shortcodes are small snippets of code in WordPress that allow you to add dynamic content to posts, pages, or widgets without writing full PHP.

This tool displays all available shortcodes, organized by WordPress Core, your theme, and installed plugins. For each shortcode, you can see its name, source file path, and search the site to locate where it’s used. Search results include the page ID, title (linked to the page), post type, post status, and the number of times the shortcode appears on the page. You can also filter search results by shortcode attributes to pinpoint specific usage.

Signups (Tool)

Signups are user registration requests submitted on your website. They allow you to monitor and manage new user accounts. Occasionally, activation links may expire or fail, and you may need to clear a pending signup.

This tool displays all signups in a table with columns for signup ID, login, email, registration date, activation status, activation key, and—if Gravity Forms is installed—the Gravity Form activation link. Each signup can be cleared individually as needed.

Site Options (Tool)

Site options are key-value pairs stored in the WordPress database that control various aspects of your site’s configuration and functionality. They can include settings from plugins, themes, or WordPress core itself. Some options are set to autoload on every page load, which can impact performance if they are large.

This tool displays the top 20 autoloaded options sorted by size, showing their size and health status (healthy, moderate, or heavy). Below that is a complete table of all site options with details including source, group, autoload status, size, and value. You can also delete options in bulk, which is useful for cleaning up leftover data from old or uninstalled plugins, improving database performance, or troubleshooting configuration issues.

Taxonomies (Tool)

Taxonomies in WordPress are used to group content together, such as categories and tags. They help organize posts, pages, and custom post types, making it easier to manage and display related content.

This tool allows you to select a taxonomy and view its settings, labels, and the post types it is associated with. It provides a clear overview of how each taxonomy is configured and which content it applies to, helping with site organization and customization.

Transients (Tool)

Transients are temporary pieces of cached data stored in the database, often with an expiration time. They are used to improve performance by reducing repeated queries or computationally expensive operations. In WordPress, transients are typically stored in the wp_options table with names prefixed by _transient_.

This tool displays all transients in a table showing their name, expiration date/time, and value. You can clear all transients, remove only expired ones, or delete individual entries. Additionally, you can create a test transient and enable automatic monitoring to track new transients in real time.

Testing (Tool)

This tool allows you to experiment with HTML or PHP code directly within the plugin. Enter your code in the provided editor and click the "Run Code" button to see the output displayed above.

For PHP code, ensure you include the standard <?php ... ?> tags.

Common use cases include testing snippets before adding them to your theme or plugin, experimenting with new functions or shortcodes, troubleshooting issues in a controlled environment, and previewing HTML without affecting live pages.

WP-CONFIG (Tool)

The wp-config.php file is the core configuration file for your WordPress installation. It defines essential settings such as database credentials, table prefixes, authentication keys, debug mode, and other constants that control how WordPress behaves. Because this file is loaded on every request, errors or syntax issues can render your site completely inaccessible.

This tool allows you to view and edit the wp-config.php file directly from the page. You can adjust syntax highlighting colors, download the current file for backup, use a raw editing view, or manage predefined code snippets.

• The Raw Editor includes a wp-config.php Cleaner that reformats and tidies the file using utilities configured in the Config Files settings. This helps make the structure more readable and consistent. Any edits made in the Raw Editor are lint-checked before saving; the save is blocked if any syntax errors are detected.

• The Snippets section detects common code blocks or constants in your file and allows you to add, remove, or modify them without having to remember their exact syntax. Select the actions you want, and the tool rewrites the file accordingly.

• Whenever the file is saved, a timestamped backup is automatically created in the same directory as the wp-config.php file. You can view, restore, or delete these backups directly from the tool.
  

⚠ WARNING! Editing your wp-config.php file can break your site if you make incorrect changes or introduce syntax errors. Every site is different, so not all snippets or constants will apply universally. Always create a backup before making any changes. This tool checks for syntax errors before saving, but you should still review your edits carefully. If you’re unsure about what you’re doing, it’s safest to seek assistance or leave the file unchanged.

Resources

The Resources page offers a curated list of valuable links for web development, WordPress management, and related tools. Each resource includes a description and direct access to the site, allowing you to quickly reference documentation, tutorials, or utilities. You can add, remove, or reorder links via drag-and-drop to fit your workflow.

This page centralizes key references, saving time and providing immediate access to the most useful resources for developers, administrators, and content managers.

Links are also included in the admin bar resource drop down, which can be enabled in the admin bar settings.

If you are looking for a way to add notes to pages or your own set of help guides, we recommend taking a look at our Admin Help Docs plugin.

Hidden Back-End Features

• Dark / Light Mode: By default, the plugin is in dark mode. Version 3.0 brings you a light mode version which can be switched by clicking on the bug icon on the top left of the page header.
• Test Mode: Clicking on the version in the header will enable/disable test mode, which is really just used by us to display information in the console log regarding which plugin scripts are firing, etc. You can keep it disabled unless support asks you to enable it temporarily when something isn't working as expected.