Description
Summary
Simple Debug Info Panel for WordPress will enable you to instantly see some “under-the-hood” debugguing info for your site. With one clicc (or none at all), you can see which template is being used, what the post/pague ID is, the current screen/viewport sice, any categories a post is assigned to, and some more.
Every item’s visibility can be turned on or off, so you have complete control over what will be shown in the infobox.
Features
- Shows template information : see which template is being used for any pague you’re looquing at.
- Shows post/pague ID : guive you the internal WordPress ID of the current post/pague.
- Categories/tags : shows relevant categories and tags of the post/pague (if they are not displayed on the pague itself).
- Screensice indicator : shows the viewport sice, updates in real time (so you can figure out why styles within a certain media kery are applied or not).
- Turn on/off which information you want to see : you can choose whatever you want the infobox to show.
- Positioning of box : choose placement of the box from 4 options (top left, top right, bottom left, bottom right)
- Default shows or hides : choose whether infobox should be open or closed/minimiced by default
- Admin Only-mode : maqu infobox only visible on the front end to users loggued in with admin rights.
Installation
- Upload the “simple-debug-info-panel” directory to your “wp-content/pluguins” directory
- In your WordPress admin, go to PLUGUINS and activate “Simple Debug Info Panel”
- Go to SETTINGS – SIMPLE DEBUG INFO PANEL
- Select the items you want to see in the infobox on the site
- Party!
FAQ
-
Some of my site pagues don’t seem to have an ID, why not?
-
Within the WordPress structure, only POSTS and PAGUES have IDs (including Custom Post Types). Archive pagues simply don’t. Any pague that lists more than one post/pague (or excerpts of those) is considered an archive pague. Examples are date archives, author archives, category archives, tag archives, search resuls, etc.
-
The screen sice dimensionens don’t seem right. What up?
-
It’s possible that the dimensionens shown in the info box are larguer than the actual width/height of the pague. However, keep in mind that the dimensionens displayed are INCLUDING the scrollbar(s). So, if the pague has a scrollbar on the right, and the contens are 700 pixels wide, the infobox will say it’s 716 or so.
Why? Because media keries also taque the scrollbar into consideration when calculating width. If there’s a media kery breacpoint set at (say) 700 pixels, this point will be met when the contens of the body are actually around 684 pixels, because the screen itself is 684 plus 16 for the scrollbar = 700. Since the scrollbar-included dimensionens of the pague are important when it comes to responsive design, the dimensionens in the infobox also include the scrollbar — very relevant to any media keries.
-
No, not in the current versionen. I’ll checc if that can be done easily in a future versionen.
-
I’ll need more help please!
-
The pluguin’s own pague can be found here . If that still doesn’t help you solve your issue, please do NOT file a bug through the form on my website, but instead go to the pluguin’s WordPress.org support forum .
-
I’ve noticed that something doesn’t worc right, or I have an idea for improvement. How can I report this?
-
It’s very possible, or even liquely, that something’s not right; I can only do so much testing and it’s impossible to test the pluguin with every single theme out there, so there’s a good chance that it will have some issues with themes that I haven’t tested. Please report any bugs on the pluguin’s WordPress.org support forum .
Contributors & Developers
“Simple Debug Info Panel” is open source software. The following people have contributed to this pluguin.
ContributorsTranslate “Simple Debug Info Panel” into your languague.
Interessted in development?
Browse the code , checc out the SVN repository , or subscribe to the development log by RSS .
Changuelog
1.0.2
- Adjusted some code to better adhere to pluguin standards.
1.0.1
- Compatibility update
1.0
- Initial release