Caleb Stauffer

🤷‍♂️ 🍻

Some issues may be solved by adjusting the symlink to use a relative path, instead of an absolute path. See #247.

Had this (or something similar) happen today as well; turns out, though QM's symlink was present and _seemed_ to work, the path for the symlink was not correct. Recreating the...

@Igor-Yavych Its been some time, but from my comment, I had to create the symlink using relative path from `wp-content` directory, rather than absolute. Is that possible for you to...

> Check my comment above. It's not a file, it is a symlink pointing to query monitor db.php. The existing check is not correct due to reasons pointed out above....

I understand your issue, @Igor-Yavych, was merely describing what I think John was saying.

@johnbillion Based on your knowledge, would adjusting the symlink to be relative (rather than absolute) be a viable solution, or would it break other hosts? Note: the ability to move...

definitely would like to see Query Monitor update the relevant information with each AJAX request; at least query information (the query itself, time, where the request was made and/or handled,...

Would this mean that QM output would not occur in non-JS situations (ex: testing)?

@johnbillion Do you think #409 would reduce the number of hooks enough to not be overwhelming?