Cached current_user ??

Tuesday 17 July 2007 1:13:03 am

I'm having a weird problem. I have a node view template that includes a template from design/myaccess/templates/xxx.tpl like so:

{include uri="design:xxx.tpl" somevar="someval"}

Inside xxx.tpl I do:

{if not(is_set($current_user))}
    {def $current_user=fetch(user, current_user)}
{/if}

When I enable caching this template seems to be caching the current user?? Is it supposed to that? Am I doing something wrong? I don't want to disable caching for this template, because it's a bit heavy to process. What can I do?

Tuesday 17 July 2007 3:40:45 am

Ok. I already have that in there, but it's pretty dissapointing because it means that I can't cache a rather complex template just because I want to display the name of the current user in the comments area of the node view :(

Is there something like cache-block that is valid inside a node view template? The user-dependent information is only a small part of the full page, the rest I would like cached.

If this is not possible, this will be the first time eZ is forcing me to redo my layout (as the performance is too poor without view caching), which is a shame really.

Tuesday 17 July 2007 7:13:22 am

Allright. It makes perfect sense to me that you can use cache-block in node templates when view caching is disabled :) Gee, eZ never stops impressing me :) Thanks alot!