Exponentcms Exponent CMS → 2.0.3

Comments and changes to this ticket

• 

  dleffler December 2nd, 2011 @ 10:26 PM

  • Milestone set to “2.0.3”
  • State changed from “new” to “resolved”
  • Tag set to “permissions”
  • Assigned user changed from “expNinja” to “dleffler”
  • Milestone order changed from “84” to “0”

  This is fixed/not an issue in current pre-release 2.0.3 develop branch

• 

  dleffler December 9th, 2011 @ 07:30 PM

  • State changed from “resolved” to “open”
  • Assigned user cleared.

  This problem still seems to occur on some installations, but can't be reproduced by developers?

• 

  dleffler December 12th, 2011 @ 08:24 PM

  • Assigned user set to “dleffler”

  speculation...this may be the result of 'manage' permissions set in an earlier version WITHOUT the assoc, 'configure' permission. In the latest versions, the 'configure' permissions is auto-checked as if selected, but UNLESS the user permission is SAVED, the permission is absent from the database table. In the current version, only the specific permission is checked and in the above scenario, would not exist.

  This scenario wouldn't exist once ticket #423 is closed.

• 

  expNinja December 13th, 2011 @ 06:06 AM

  (from [5e1119a6619f52723be3b7aefffd347541f1bf5e]) Implements cascading page permissions (inherited), implements global sidebar permission restriction (doesn't pick up the page permissions which must now be explicitly set at the container or module), Also ensures the manage permission screens better reflect these implied and inherited permissions. Still needs work on cascading container permissions. [#420 #320 #415 #422 #423 #189 #86 milestone:2.0.3 owner:dleffler] https://github.com/exponentcms/exponent-cms/commit/5e1119a6619f5272...

• 

  dleffler December 13th, 2011 @ 06:08 AM

  • State changed from “open” to “resolved”

  If the speculation above is correct, this has been fixed by checking for implied permissions.