Developer Debug Tools

Yes! It is always best to back these files up when making updates to them. You can do so on the config file pages or all together with your functions.php in a zip file from the dashboard.

Yes, but you should always make a backup of your site before using functionality that makes changes to your core files or database.

The file editors have been improved to include a code/lint checker and other checks to ensure that they include certain working pieces. However, nothing is full-proof, so in the case that something happens, a backup is automatically stored in the same folders as the originals before being saved. The backups are named with the date and time from which they were replaced. For example, the wp-config.php file will have been renamed to wp-config-2022-08-22-15-25-46.php and replaced with a new file. Simply log into your FTP or File Manager (from your host), rename the current file to something else such as wp-config-BROKEN.php (just in case you need it), and then rename the version you want to revert back to as wp-config.php . If everything looks good, then you can either delete the broken file or send a copy of it to PluginRx so we can figure out what went wrong.

Click on the bug icon in the header. 😉

If you are seeing that Test Mode is Active in the header, you likely accidentally clicked on the version number. Test Mode is for our developers only. If you contact support with an issue you are having with the plugin not working the way it should be, we may have you activate Test Mode with additional instructions on what to provide so we can handle it promptly. It is of no use to you otherwise. Just click on the version number in the header again to disable it.

Some hosts will not allow you to update a user’s username directly from WP. In order to do so, you’ll have to update it in your database directly.

Viewable only on the front-end, there is a link on the admin bar that shows + Off . Click on it and it will add a semi-transparent bar with lines on it at the top of the page underneath the admin bar. If you click on this bar it will expand all the way down the page. Click on it again and it will minimize back to the top. You can click on the + On link from the admin bar to make it go away.

You have to enable them on the Developer Debug Tools settings first under the Admin Menu tab. Once they are enabled, an “ID” column will be added to the corresponding admin list pages. Next to the user or post’s ID you will see a lightning bolt icon. Clicking on the lightning bolt will redirect you to the Metadata page on the plugin where you can view and edit all of the meta easily. Links are also added to the user profile and post edit screens.

You can get there directly by going to https://yourdomain.com/wp-admin/admin.php?page=dev-debug-dashboard . Be sure to bookmark it next time like the instructions say to do!

If you password-protected your options.php page like you should have (included by default), then you will need to log in directly to your database and clear the password manually ( {prefix}_options table > delete key ddtt_pass ). We used to have a forgot password option that would email a reset link to the devs, but it’s easy to intercept that email with various email logging plugins if you have access to the admin area of your site.

The SEO tool fetches your robots.txt and sitemaps over HTTP, just like a search engine would. If your staging site uses basic authentication or your host blocks requests from the server back to itself, those requests will fail. The diagnostics table shows the exact error so you can work out the cause.

We recommend using our website support forum as the primary method for requesting features and getting help. You can also reach out via our Discord support server or the WordPress.org support forum , but please note that WordPress.org doesn’t always notify us of new posts, so it’s not ideal for time-sensitive issues.