Cache problem with content(read) owner(self) role

Author Message

Benjamin Selmer

Monday 05 February 2007 12:16:02 am

I have set up a user role with content(read) owner(self).

But when a user logs on to view nodes that he is the owner of, he only sees the nodes of the previous user who logged on. If I clear the cache he can see his own nodes. But then the next user gets the same problem.

Is there anything I can do to avoid this? Some cache-block setting?

I'm running ezp 3.8.3.

hikesh hasmukh

Monday 05 February 2007 2:00:47 am

Maybe a cache-block closing tag is missing!

http://www.mzbusiness.com/

André R.

Monday 05 February 2007 3:08:21 am

Are you talking about the content view itself or the navigation.

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Benjamin Selmer

Monday 05 February 2007 3:47:03 am

The content view.

Benjamin Selmer

Tuesday 06 February 2007 12:06:58 am

The same problem occured on a clean installation.

Is it a bug?

Kristof Coomans

Tuesday 06 February 2007 12:26:08 am

If you use the owner limitations, then you need to globally disable view caching, or disable it in the view template:

{set-block scope=root variable=cache_ttl}0{/set-block}

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

André R.

Tuesday 06 February 2007 12:59:42 am

Then you can cache the content view using cache block with user id as key instead, if necessary.

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Benjamin Selmer

Monday 12 February 2007 12:48:15 am

{set-block scope=root variable=cache_ttl}0{/set-block}
did the job.

Thanks!

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 30 2025 21:44:54
Script start
Timing: Jan 30 2025 21:44:54
Module start 'layout'
Timing: Jan 30 2025 21:44:54
Module start 'content'
Timing: Jan 30 2025 21:44:54
Module end 'content'
Timing: Jan 30 2025 21:44:54
Script end

Main resources:

Total runtime0.0247 sec
Peak memory usage8,192.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0059 588.2656151.2266
Module start 'layout' 0.00590.0044 739.4922220.7344
Module start 'content' 0.01030.0129 960.22661,005.8359
Module end 'content' 0.02320.0014 1,966.062541.9922
Script end 0.0246  2,008.0547 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002811.2275140.0002
Check MTime0.00114.5125140.0001
Mysql Total
Database connection0.00103.895910.0010
Mysqli_queries0.003012.355430.0010
Looping result0.00000.085010.0000
Template Total0.00104.110.0010
Template load0.00072.902310.0007
Template processing0.00031.208110.0003
Override
Cache load0.00052.006410.0005
General
dbfile0.00166.607880.0002
String conversion0.00000.036740.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs