Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LiteSpeed Cache conflict #770

Open
meirs1 opened this issue Jun 12, 2023 · 3 comments
Open

LiteSpeed Cache conflict #770

meirs1 opened this issue Jun 12, 2023 · 3 comments

Comments

@meirs1
Copy link

meirs1 commented Jun 12, 2023

With LiteSpeed plugin activated query-monitor doesn't show on the frontend. Deactivation of lightspeed solved that.

@johnbillion
Copy link
Owner

Can you provide some more information please? Are there any errors in your PHP error log? Are there any JavaScript errors in your browser console? Is the WordPress admin toolbar enabled on the front end?

@meirs1
Copy link
Author

meirs1 commented Jun 15, 2023

Hey John, thanks for the quick response and sorry for my late one :)

I didn't get any PHP errors in the log, neither JS errors in the browser, and the frontend admin toolbar is enabled. Note that QM does show on the backend correctly, while on the frontend I have the QM menu shown and I can select items but no results shown on the bar itself (see attached screenshot).
The check I made was quite simple: disabling Litespeed made QM show correctly on the FE, enabling it again made it disappear.
Screenshot 2023-06-15 at 15 10 54

@meirs1
Copy link
Author

meirs1 commented Jun 16, 2023

Some more information: the bug occurs on both production and staging. I replicated exact same site on my local env (docker) in order to debug it but then QM works just fine. I guess that's because the docker image doesn't implement LiteSpeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants