Could you tell us more about the fetch function used to retrieve and display the children of the My Stories folder ? Any chance the 'limitation' parameter is used ? (feel free to paste the call to the fetch function here).
Cheers,
--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board
thank you for your quick reply. I really appreciate it.
Actually I haven't touched the template yet regarding the fetch function. I assumed that I could control the content through roles and policies only.
I'm using ezPublish 4.2011 and created a user group "reporters" with policy setting "Content read Owner (self)". Also I use the standard user class to create reporter objects. I figured that just by using Owner (self) would display only the content that a user created. So whenever a user creates an article he is the owner, I guess. After login only those articles of this specific user should be shown.
What is the purpose of having Owner(self) if it doesn't list me only the objects related to a specific user?
If I have to use a fetch function how would that look like?
Hm, maybe your users have some other role assigned that allows them to read articles.
For example they can have the Anonymous role assigned which can have the content/read/* policy. In that case every user would have access to all the articles regardless of any other new roless you assign.
Also, you should be clear about what you want to do:
a) restrict logged in users so that they can read only their articles and in no way to be able to read any other article
b) allow logged in users to read any article but have a special box in one part of the page where they can see only their articles
If yours is case a) then you should use the roles and policies to restrict it.
But if yours is case b) you should change the templates and use template fetch functions with attribute filtering. See here for the docs about template fetch functions:
Disabling cache is not a good solution, you should use ViewCacheTweak configuration setting and set it to pr_user.
By default the cache in eZP is not generated per user but you have the same cache for the users that have the same set of roles. This ViewCacheTweak settings allows you to have a per user cache.
The setting is not documented in the official eZ docs but you can find some info about it here: