Found a solution: I reassigned the section "Standard" to the top node of the content tree (to newbies: you need to navigate one level up using the little folder-top-arrow), flushed the cache and all was well - hopefully..
Can't say I like this behaviour in eZp: It seems it was my new section (section id=7) that started this trouble. Is this a bug?
This issue could be related to this forum posting: http://ez.no/developer/forum/setup_design/role_caching_problem
PS! Happy New Year by the way!
------------------------
I made eZ run on www.eigersund.kommune.no, bjerkreim.kommune.no, lund.kommune.no and sokndal.kommune.no. Municipalities should use open source!
When you create a new section, it is considered as "private". You have to allow anonymous users to read it. In "roles and policies", give them something like that : "content read Section( YourSection )"
Hi, yes that's true. What I didn't expect was that assigning a subtree to a new section would strip it from its relation to the original section. I actually had to reassign both the "Standard" and the section "Restricted" to my member area as well, to return my site to the original state.
Now I'm setting up the necessary access limitation through the use of roles alone.
------------------------
I made eZ run on www.eigersund.kommune.no, bjerkreim.kommune.no, lund.kommune.no and sokndal.kommune.no. Municipalities should use open source!
You're right, you can't assign several sections to an object.
By the way, the session are related to the object and not to the node. It seems that if you have a multi-location content, you can't have one section by location.
Hope this helps... Laurent
You must be logged in to post messages in this topic!