Conflict with Query Monitor

  • Resolved optimizewp

    (@optimizewordpress)


    6 years, 8 months ago

    Hi there.

    I’d like to report this conflict between your plugin and Query Monitor (https://www.ads-software.com/plugins/query-monitor/)

    The issue it this:
    When both plugins are active, on a WooCommerce based install, Single Product edit returns “502 Bad Gateway” on Save or Update, as draft too, and related errors are reported on debug.log.
    Some weeks ago this was happening on Quick Edit too.

    I have been able to inspect this on different WP/Woo installs with different plugin assets, and once discovered the conflict, I wanted to deactivate all the plugins leaving only the 4 reported below, so there is no need to indicate the urls of the installs I was working on, since it is easy to reproduce.

    Step to reproduce:

    WordPress v. 4.9.4
    WooCommerce v. 3.3.4
    Query Monitor v. 2.17.0
    WP-Lister Lite for eBay v 2.0.31

    Create or edit a product, on Save or Update, as draft too, the page returns “502 Bad Gateway” reporting the relative error on debug.log (so you can directly inspect it).

    Query Monitor is not essential on our installs, of course it has its roles as debugging tool, so we can keep working and keep it deactivated. But of course, if this conflict can be solved it is better.

    Thanks in advance for your time.

    Paul

    PS: PHP 7.1

    • This topic was modified 6 years, 8 months ago by optimizewp.
    • This topic was modified 6 years, 8 months ago by optimizewp.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support WP Lab Support

    (@wp-lab-support)

    Hello @optimizewordpress

    Thank you for contacting us and reporting this information to us.

    But without an actual error message, there isn’t anything we can do. A “Bad Gateway” or “Service temporarily down” doesn’t mean anything, it’s as useful as “500 Internal Server Error”.

    With that said, if there is something meaningful in the error_log on the server (a PHP error message that points to a specific file within WP-Lister or WordPress) then we can look into this, otherwise there is not anything we can do to help here other than you providing us permission to your site to examine everything ourselves.

    A couple of our users have had issues with Query Monitor, and at that time the developer did look into it and it was due to query monitor causing the server to timeout due to Query Monitor requiring quite a lot of resources.

    Kind regards,
    John

    Thread Starter optimizewp

    (@optimizewordpress)

    Hi John,
    thanks for your kind reply.

    I did a quick test on another install, on the same hosting, but with different server setup, and there the issue was not present.

    So I asked the hosting company to check their server setup and they fixed it in minutes, adjusting some parameters in Nginx, so your hint has been very resolutive.

    Cheers!

    Happy Easter!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Conflict with Query Monitor’ is closed to new replies.