Yes, I posted on the Litespeed discussion boards and just got this message from Litespeed:
Hello,
please upgrade to the latest version/build and let us know if this issue persists:
/usr/local/lsws/admin/misc/lsup.sh -f -v 6.3.6 -b 6
I’ll check on my server and see if it fixed the issue
_________________________________
Yes, the manager is working fine now without the plugin fix, so the Litespeed update fixed the problem.
I am with Hosting.com (formerly A2Hosting), and I’m on a shared server environment (not a VPS), so they can’t roll me back to a previous version or downgrade HTTP without impacting the whole environment. They confirmed they are running LiteSpeed 6.3.6, and the problem persists on the two dozen sites I have running on ModX. At this point, their tech support is (predictably) calling this a ModX issue that requires a patch to the CMS.
Is anyone else in this predicament?
M
Litespeed V6.3.6 (build 5) is the version with the problem - and I believe the initial fix was to revert to build 4.
However, Litespeed have now accepted that this was a bug - and have fixed it - so the fix is now to update Litespeed to:
V6.3.6 (build 6)
Maybe your hosts would be more agreeable to that idea?
Ah, let me check with them on that. They may not have been looking at the build version.
Just to follow-up on this, they confirmed they have Build 5 installed, but refused to patch it to Build 6 on-the-fly just because one customer requested it. I can respect that, but if anyone is using A2Hosting (now Hosting.com), just be aware of it. They didn’t say when they planned to patch it, so I’ll limp along with the plugin, which works pretty well.