It's difficult to know which processor that is. You could try temporarily making yourself a sudo user and flushing permissions and settings. If that fixes it, it's definitely a MODX permission issue (not a file or directory permission issue). If it doesn't, it's more likely a file or directory permission or ownership issue.
Disabling all plugins is another thing to try. You can do it in the modx_plugins table in the DB if necessary.
It doesn't seem to be a plugin issue, I manually disabled them all in the db table.
Hmmm...this isn't looking good for me.
If it requires more drastic measures I'm open to all suggestions. I hope I don't have to completely rebuild the site.
Todd
Are you able to access any resource/elements via resource tree (quick update)?
TinymceWrapper: Complete back/frontend content solution.
Harden your MODX site by
passwording your three main folders:
core, manager, connectors and renaming your
assets (thank me later!)
5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
Actually no. Not even from the Dashboard because the Resource (sliding) panel is missing, no open/close trigger. And all the other Manager pages are blank white.
It's a mess and I don't know why. It was working fine.
Todd
Oddly enough even this file throws a 404. Houston, we have...
Yes this is an htaccess permission thing and/or mgr ACL problem.
Pages cannot be found because they are accessed wrongly.
1. One usual culprit is accessing a site - manager or live - in one these ways:
www or not
www?
2. add mgr load permission to administrator group
TinymceWrapper: Complete back/frontend content solution.
Harden your MODX site by
passwording your three main folders:
core, manager, connectors and renaming your
assets (thank me later!)
5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
Did you try making yourself a sudo user?
User is already a sudo.
I tried something...I removed all the current 2.4.2 folders/files from the server. Nothing MODX-related in public_html, completely fresh. Then I unzipped 2.4.3 in the site root and ran setup. Still it throws a 404.
I also thought it might be a Cloudflare issue.
In any case thanks for the suggestions.
[ed. note: todd.b last edited this post 10 years, 6 months ago.]
Todd
Unless there's an .htaccess file in the root causing trouble, it almost had be a server issue.
I thought that, too. But I removed the .htaccess along with everything else.
Thanks
Todd
discuss.answer
It was in fact a server issue.
The host had made some sudden and unexpected changes which apparently have wreaked havoc with everything from email to Web apps.
Todd