We upgraded to 3.2.3 a few weeks ago and thought all was well but on logging in yesterday I found that the resource tree wasn’t expanding properly. Elements and files were fine but not Resources. Also the MODX news feed was not loading.
Step to reproduce
How to reproduce the issue, including custom code if needed.
I know nothing about the HTTP versions but I’d be a little surprised given that the manager was working after the upgrade and has only recently failed. Trouble is I am not sure exactly when we did the upgrade or how much we have changed in the database since then because version X is not accessible.
When I run Version X I get this error “A server error prevented this grid’s content from loading. Refer to your browser’s console, manager logs, and/or php server logs for more information.”
My browser console errors are:
window.controllers/Controllers is deprecated. Do not use it for UA detection. ace.min.js:1:18512
Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. modernizr.custom.js:4:2077
The issue with the HTTP versions was actually an issue with hosting providers who use LiteSpeed. A recent upgrade to LiteSpeed has caused a problem that manifests in MODX as the resource tree not showing up and grids being empty.
Don’t know if those VersionX errors are related or not.
I heard that but what I don’t have is a solution. I understand that MODX developers are working on one but I haven’t found a timescale. I have also heard of a workaround plug-in but haven’t been able to track that down either.
We may be talking about different things. My understanding is that it’s a bug in LiteSpeed, not MODX, so MODX devs would not be working on a solution. The solution is to reach out to your host and ask them to roll back the update until LiteSpeed releases a patch. All of which is in that thread I linked.
