Plugin conflict

[benfavre]

Not compatible with this commercial plugin : http://codecanyon.net/item/layerslider-responsive-wordpress-slider-plugin-/1362246

No output on any page accross the whole site (blank page) even with wp_debug enabled.

[johnbillion]

@benfavre are you able to take a look at your error logs please? Sounds like a fatal error or a 500 error is being generated. It would be really helpful if you could let me know if there are errors being logged and what the error messages say.

[johnbillion]

Please try the latest version of Query Monitor (2.5.5). If the issue persists then I'll need access to that plugin in order to debug it, otherwise I'll just be stabbing in the dark.

[benfavre]

Hey, so the latest update fixes the issue , except there is a javascript issue

Console output :

=== PHP Error in AJAX Response === query-monitor.js:141
null query-monitor.js:142
Uncaught TypeError: Cannot read property 'type' of null 

The line is qm.ajax_errors[error.type] = true;

Don't know what's going in on in the script but you there should be a check to see if error is an object and type is a property but i suppose you know that.

Thanks for looking at this, i know you had no data to work with, given how lousy my bug report was.

Also thanks for the great plugin, seriously top notch 👍

[johnbillion]

The error variable here should be an object. If it's null then something's going wrong.

@benfavre could you send me the response HTTP headers from the AJAX request please? In Chrome and Firefox you can get this from the Network tab in developer tools (and then click on the AJAX request at the bottom).

[benfavre]

No ajax request is made.

[johnbillion]

There must be an AJAX request being made otherwise this JavaScript doesn't get called.

[benfavre]

Hey there, when i said there is no ajax request made i actually meant it. Sorry the details have been so sparse.
I have woocomerce installed and it's getting a cart fragment via ajax.
The js is picking up on the wrong ajax request and is not making it's own one;

[johnbillion]

Oops, didn't mean to close this ticket. Thanks for the update. I'll take a look at WooCommerce at some point and see what's going on.

[johnbillion]

Can you update to 2.6.2 and let me know if this issue is fixed?

[johnbillion]

This should be fixed in 2.6.3.

[benfavre]

Working fine, I confirm. Thanks.