John Blackbourn
John Blackbourn
I would be in favour of removing these inaccessible nodes by default. Perhaps with a config flag to not exclude them in cases where they are needed?
If it breaks anybody's code then they can ask Viktor for a refund.
Yeah there's been several reports of this over the years. Unfortunately there's no way for a PHP script to know the total size of the headers being sent (including cookies)...
I had planned on adding a limit of 10 errors to this header output, but even 10 errors can exceed 4KB.
> I as a user of QM, would love to know the message, file and line but I might not need a hundred frame stack trace This is understandable but...
Feel free to paste the payload here and we'll see what effect compression has on it
This is certainly something I'm keen to address in Query Monitor but it won't happen for a while yet. Once the client-side rendering work is complete (which is still dragging...
I've used [Error Log Monitor](https://wordpress.org/plugins/error-log-monitor/) in the past for this but I think it could be useful to have in Query Monitor too. I'll have a think about it.
Action points for me: * Split up the build workflow in plugin-infrastructure so it can be used to build the plugin without also creating and pushing a tag * Confirm...