[opencms-dev] Caching of formatters on resource level

[Kai Widmann]

Hi Stephan,

I don't tell the container page what to display. The container page contains these resources (they were added by the editors using drag and drop), so the container page itself "knows" what to display, hence no URL parameters. Otherwise it would be simple.
I'll give you an example: Let's say I have a content type named "imagegallery". If an editor chooses to add multiple image galleries to one page, the container page contains (or is referencing) multiple distinct "imagegallery" resources all displayed by the same formatter. How could those be cached individually?

Cheers

Kai Widmann

Von: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Stephan Hartmann
Gesendet: Freitag, 14. Februar 2014 10:37
An: The OpenCms mailing list
Betreff: Re: [opencms-dev] Caching of formatters on resource level

Hi Kai,
How do you tell the container page which resource it should display? E.g. if you use a request parameter, your cache setting would be "params".
Best regards,
Stephan

2014-02-13 17:58 GMT+01:00 Kai Widmann <Widmann at mediaworx.com<mailto:Widmann at mediaworx.com>>:
Hey there,

is there a way to cache formatters based on the displayed resource? We're using a container page to display multiple resources of the same content type using the same formatter. If caching is turned on, only the first formatter output is cached, all subsequent occurrences of the formatter display the same content.
Surely there is a cache directive that could be used for such a scenario, but if I look at the FlexCache documentation I can't seem to find it.

Any help is greatly appreciated

Cheers

Kai Widmann
_______________________________________________

Kai Widmann
mediaworx berlin AG

_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20140214/842ebb57/attachment.htm>