Forums / Setup & design / Did the working of roles and policies change in 3.6??

Did the working of roles and policies change in 3.6??

Previous topic

Setup & design

Next topic

Author	Message
Bernhard Reiter	Wednesday 15 June 2005 12:58:16 pm Hello, I have a VERY strange problem. I had my site working fine with 3.5. I now upgraded to 3.6 (needed some new features) and now i cannot access my site anymore without logging in (as admin). I have not changed anything in my roles and policies. If i want the anonymous role now to see anything i must change its contet/read limitation from 'Section(Standard)' to 'any'. I first thought i somehow borked up my installation at the upgrade process, but then i tested it with an new instalation and its the same. As long as something is in the standard section it works, but as soon as i create a new section, assign some nodes to it, and grant access to the section for the anonymous role, i get access denied. So my question is has something changed in 3.6 regarding access and roles stuff or am i just really stupid.
Bernhard Reiter	Friday 17 June 2005 5:26:28 am Well, i now made a test with clean installations of 3.5.2 and 3.6.0. And the behavior of 3.6 did definitely change! Its of no more use to assign a section with limitatiosn to an user(group). Instead i have to edit the content/read policy. Still there seems to be no mentioning of it. I think this is a conspiracy ;-)
Paul Borgermans	Friday 17 June 2005 7:15:20 am Oops That's a bug then, please report it in the bug section Regards -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans

Author

Message

Bernhard Reiter

Wednesday 15 June 2005 12:58:16 pm

Hello,

I have a VERY strange problem.
I had my site working fine with 3.5.
I now upgraded to 3.6 (needed some new features) and now i cannot access my site anymore without logging in (as admin).

I have not changed anything in my roles and policies.
If i want the anonymous role now to see anything i must change its contet/read limitation from 'Section(Standard)' to 'any'.

I first thought i somehow borked up my installation at the upgrade process, but then i tested it with an new instalation and its the same.

As long as something is in the standard section it works, but as soon as i create a new section, assign some nodes to it, and grant access to the section for the anonymous role, i get access denied.

So my question is has something changed in 3.6 regarding access and roles stuff or am i just really stupid.

Bernhard Reiter

Friday 17 June 2005 5:26:28 am

Well, i now made a test with clean installations of 3.5.2 and 3.6.0.

And the behavior of 3.6 did definitely change! Its of no more use to assign a section with limitatiosn to an user(group). Instead i have to edit the content/read policy.

Still there seems to be no mentioning of it.

I think this is a conspiracy ;-)

Paul Borgermans

Friday 17 June 2005 7:15:20 am

Oops

That's a bug then, please report it in the bug section

Regards

-paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans