explodybits
Forum Replies Created
-
Forum: Reviews
In reply to: [WP Inspect] Currently Completely Broken – Do not tryGeig3r,
Sorry for the inconvenience.
Because this plugin is capturing every hook called during the request, it requires this information to be loaded into memory, which is why your memory was exhausted.
How much memory is allocated to PHP? How many plugins do you have active? Any information would be appreciated.
Forum: Plugins
In reply to: [WP Inspect] Bug: CSS being applied when disabledSo I’m looking through my CSS and I’m not seeing that. I have two stylesheets, one for frontend, another for the admin.
The screen.min.css (frontend) & screen-admin.min.css (admin) each only having one reference to max-width, which applies to the pre element in the popups:
.qtip-content pre{text-overflow:ellipsis;line-height:1.25;<strong>max-width:100%</strong>;padding:.25emI’m running the plugin under a vanilla install of WordPress with no other plugins enabled. Any additional information would be helpful, but I’m not seeing it on my end.
Forum: Plugins
In reply to: [WP Inspect] Show WP Inspect in modal windowsI believe this modal is generated via JS. To prevent any performance issues, or breaking the UI, I disallow WP Inspect from injecting itself into inline <script> tags.
I’ve toyed with this in the past, and it’s just too brittle and error prone.
Forum: Plugins
In reply to: [WP Inspect] Memory HoggingGarikai,
As I mentioned in my comment on the original article via WP Tavern, the only recourse you have is to adjust WP Inspect’s settings to achieve the desired memory usage:
-Disable plugins that you are not debugging
-Enable only actions or filters
-Toggle contexts, headers, middle, footer & off-screen
-Disable backtraceAlso, I do not recommend running this in a production environment, as this is a debug tool and does require in-memory operations to run.