eZ Publish 4.1 alpha2 and object states

Wednesday 18 February 2009 11:46:48 am

Hi !

I tested the alpha2 with the ezwebin package. I tried to change the object state of the frontpage (lock). After this I couldn't do anything. But I had an administrator account.

Finally I added a new policy to the administrator role (content - edit - no limitations) and I could modify the frontpage.

This is strange not ? Because the administrator role has a "all modules - all function - no limitations" policy...

I think that the new object state feature don't respect the all modules and all functions policy. Is this a bug ?

I'm excited to play a little bit with this new feature :-)

http://www.wess.ch
eZ Publish Certified developer : http://auth.ez.no/certification/verify/272583

Friday 06 March 2009 3:20:59 am

I found a even stranger situation.

By default admin role has following policy (and lock state objects can't be edited):

1 "all modules - all function - no limitations"

But if you create a second policy again with:

"all modules - all function - no limitations" (deafult policy)
"all modules - all function - no limitations" (added policy)

the locked objects can be readed! So the second "all modules - all function - no limitations" policy works like it should...

eZ Partner in Madrid (Spain)
Web: http://www.atela.net/

Saturday 07 March 2009 9:39:42 am

Hi

The lock state you used is not supposed to be used by end users, it's an internal state that will be used by WebDAV and the policy limitations for it are implicit (they do not have to be added to all roles by the admin, they are automatically inserted by eZ Publish). Unfortunately the current code still allows this state group to be used in the GUI, didn't have time to finish it before I left eZ Systems. So the issue is valid and will hopefully be tackled before a release candidate.

independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org