Are there any errors showing up in the developer console?
Anything 404s or 500s being triggered?
Which other plugins are you running?
I’ve kinda same issue. Plugin is fine unless I make some ajax call using the standard admin-ajax.php method. I get a 500. Error logs reports Premature end of script headers: admin-ajax.php (WP 3.7.0)
Sorry for the delay.
Yea, I’m getting a 502 on admin-ajax.php. Usually associated with javascript breaking somewhere. It’s certainly triggered by activating the plugin.
It’s anywhere in the admin where ajax is used e.g. moving widgets or jetpack dashboard widget.
I’m not seeing anything else of use I’m afraid so will just give as much as I can…
WP: 3.7.1 – Multisite
Plugins:
– Arqam (codecanyon plugin)
– BWP Google XML Sitemaps
– Comments advanced
– Gravity Forms
– Gravity Forms Mailchimp Add-On
– Gravity Forms User Registration Add-On
– Image Widget
– Jetpack
– Limit Login Attempts
– Meta Box
– Network Nginx Proxy Cache Purge
– Nginx Hosting Tweaks
– Posts 2 Posts
– Quick Page/Post Redirect Plugin
– Remove Dashboard Access
– RSS Multi Importer
– Simple Local Avatars
– Strictly Auto Tags
– Redirection
– Usernoise
– Usernoise Pro (Codecanyon addon)
– User Switching
– WP Author Slug
– WP Glossary
– WordPress MU Domain Mapping
…. wow, just realised how many plugins I have running :S
I’m not seeing anything else of use I’m afraid so will just give as much as I can…
…by this I mean, no other js errors or notices or issues with the admin. The Query monitor plugin works well but I need to disable it when I’ve stopped debugging things (probably not a bad thing)
Thanks guys, I think I’ve tracked this down. I’ll be pushing out an update in the next few days that fixes various issues.
Great news! Cheers for the plugin is massively useful in helping me (front-end developer) understanding things above my paygrade.
I’ve just pushed an update which may or may not fix these AJAX issues. If the issues are still occurring after you update Query Monitor to 2.5.5 then let me know and I’ll have to get some more debugging info from you.
Version 2.5.6 fixed my problem.
Thanks
2.6.6 is still causing AJAX issues for me. =/ “520 (Origin Error)“.
It looks like the only mutual plugin I share with riseofflex88 is Jetpack.
Thanks AppleBag. Someone else has reported seeing “520” errors too: https://github.com/johnbillion/query-monitor/issues/57
Apparently a 520 is a specific status code used by CloudFlare (it’s not a standard HTTP status code). Are you using CloudFlare?
Hi John,
That was me actually, came across both sites while studying up on this and ya never know which site(s) an author pays attention to. =)
I’ll continue the discussion over at Github.
