-
- 24,544 Posts
It does sound like something is broken (as you suggested). Double check the ACL entries for the anonymous User Group. Check the policy or Policies involved (Should be Load -- or Load, List, and View for everything). Then look at the permissions on the specific Policies themselves to make sure there aren't any permissions that shouldn't be present.
It's possible (though frankly it seems unlikely) that you have one or more corrupted files in your MODX install. It's common if you upload them individually with FTP, though usually, that breaks things in a much more obvious way.
-
- 74 Posts
Thanks for the suggestions @jgulledge19, @BobRay, I'll give those a try.
@BobRay, don't forget this problem exhibits on both the live site and the development server. On both of these, MODX updates are applied by unzipping the files directly into the web root, and not via individual upload. On the dev server, the MODX update file is downloaded directly via WGET.
I did notice that 2.3.5 was just released, I really wish there was a mailing list I could get on to be immediately notified of these :-(
I might try updating to 2.3.5, I'm not holding out hope though, and sometimes MODX updates can break the Articles extension.
-
- 74 Posts
Also, updated to MODX 2.3.5 – the problem persists.
-
- 74 Posts
Also, uninstalled all Extras, problem still persists.
AdvSearch
breadcrumbs
formit
gallery
getpage
login
personalize
pthumb
quip
resizer
revossl
simplesearch
taglister
tinymce
firstchildredirect
articles
wayfinder
-
- 24,544 Posts
Are the users' group memberships the same in both sites -- especially the (anonymous) user?
The only thing I can think of is that MODX somehow thinks it's running in CLI mode. In that case no permissions are enforced. I can't imagine how that could happen, though. Otherwise, I'm stumped.
Since we're grasping at straws, you might create a fresh install on the same server where you have the problem and see if it still happens. I dimly recall someone with a similar problem who solved it by starting over with a fresh install of MODX.
-
- 24,544 Posts
How do I tell if MODX is running in CLI mode? Is there a specific line of PHP code that triggers it?
It's decided by PHP at some point early in the request. What you really care about, is whether MODX thinks it's in CLI mode. You should be able to check both with a snippet like this (untested):
$output = '';
if (php_sapi_name() == 'cli') {
$output .= '<br />PHP is in cli mode';
} else {
$output .= '<br />PHP is NOT in cli mode';
}
if (XPDO_CLI_MODE) {
$output .= '<br />MODX is in cli mode';
} else {
$output .= '<br />MODX is NOT in cli mode';
}
return $output;
I'll be really surprised if either one comes back as cli mode, but it's worth checking.
☆ A M B ☆