Caching Pitfalls When Rendering Assets That Use Dimensions (Translations)
Last updated on NOVEMBER 14, 2016
Applies to:Oracle WebCenter Sites - Version 7.6.0 and later
Information in this document applies to any platform.
A cached page is not updated when a new translation of an asset is created which would be used by the page (and be a dependency) if it existed at the time the page was rendered.
a) Template RenderLocalContent renders particular content depending on the locale.
e.g when the page is called with the French locale, the french translation of the asset is rendered:
b) RenderLocalContent falls back to the default locale content (master asset) if no translation of that content exists.
e.g. Suppose en_US is the master asset. If no fr_FR translation exists, the en_US asset is loaded and rendered.
c) Now the rendered page is cached.
e.g. The page that should be the French version of the page is cached with the US English version of the content, since the French version did not exist at the time the page was rendered.
- So, pagename=RenderLocalContent&c=Content_C&cid=1234567890123&locale=fr_FR is cached with en_US content.
d) This causes an issue when newly created translations of assets are made, as they are not reflected in the page, until the master asset has been updated, or the page cache has been flushed.
e.g. Even after a fr_FR translation of the master asset (en_US) is made, the page still returns the previously cached content.
- pagename=RenderLocalContent&c=Content_C&cid=1234567890123&locale=fr_FR returns the previously cached en_US content.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms