Hi Brady, I really appreciate your feedback!
I have a couple of suggestions, though. When I have the WP_DEBUG constant set to true, this plugin outputs quite a few notices, mostly for undefined indexes and variables, which makes it hard to develop other plugins with Memory Viewer enabled.
I’ve been noticing that when the plugin is enabled, it overtakes dashboard in numerous places. Is this what you referring to? I was thinking to disable the plugin for the dashboard side.
And, I think the query results would be more useful if they were automatically ordered by speed (slowest to fastest) so it’d be easier to identify queries that might need to be optimized.
I was kinda thinking this myself too, nice to see someone else mention it. I’ll let you know when I can get to those changes.
Thanks again!
No, I think it’s useful in the dashboard in certain instances. When developing other plugins or themes in debug mode to make sure they don’t produce any errors, Memory Viewer causes a few notices of its own.
If you change WP_DEBUG to true in wp-config.php, you should see the notices. Here are a few that show up for me so you can see what I’m talking about:
Notice: Undefined index: mvimh_last_total_queries in /wp-content/plugins/memory-viewer/memory_viewer_imh.php on line 120
Notice: Undefined index: mvimh_last_hook_cpu_time in /wp-content/plugins/memory-viewer/memory_viewer_imh.php on line 129
Notice: Undefined index: last_mysql_time in /wp-content/plugins/memory-viewer/memory_viewer_imh.php on line 157
Notice: Undefined index: mvimh_logged_first_queries in /wp-content/plugins/memory-viewer/memory_viewer_imh.php on line 167
