Hello,
I don't know if this bug (I dont know if it is a bug) is already known, but when upgrading modx 2.2.2 to 2.2.4 a new default access policy named "Developer" is added. The interesting thing is when you install modx 2.2.2 or modx 2.2.4 without upgrading the "Developer" policy is missing...
Can anybody duplicate this?
Are you sure you didn't create that policy yourself? I have a site that I upgraded to 2.2.4 and I don't see it.
------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone:
http://bobsguides.com/modx.html
Hey BobRay,
yes, I'm 100% sure. I had this "bug" on two modx installations on my web server. I was also able to reproduce this on my local xampp installation...very strange!
It even has an "official" description. See attached screenshot...
[ed. note: paul_kemp last edited this post 14 years, 2 months ago.]
-
☆ A M B ☆
- 24,524 Posts
From where did you get the version of 2.2.4?
-
☆ A M B ☆
- 24,524 Posts
Ahah!
core/packages/core/modAccessPolicy/23330ac341fb8cf2bf042708cbaa7617.vehicle
-
☆ A M B ☆
- 24,524 Posts
How interesting. Examining the setup/includes/upgrade.install.php script I found this line
if ($settings->get('installmode') == modInstall::MODE_UPGRADE_EVO) {
More to the point of this thread, however, it appears that the developer policy is added during an upgrade, but is not installed on a fresh installation.
Interesting. I've done a bunch of upgrades, but I don't remember ever seeing that Policy.
It would be useful as an intermediate Policy between ContentEditor and Administrator, since ContentEditor is often missing important permissions and you seldom want to make someone else an admin Super User.
------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone:
http://bobsguides.com/modx.html
-
☆ A M B ☆
- 24,524 Posts
I got this from looking at the unzipped archive of the standard download from the MODx site.
@sottwell
Same here. I'm using the packages from the official modx site.
@BobRay
Maybe it only happens when you upgrade these particular version: 2.2.2 -> 2.2.4
