Component caching across sites?

My understanding of components is that each component is cached (depending up on the cache timeout set) for the whole site.

For example if I have a component that has one boolean Datum, that if I select "true" on one page, that component will be pulled from cache regardless of which page it's on as long as "true" was selected. (If that's not true - correct me now and stop reading.)

What happens if that same component is used on two different sites? Are components cached across sites or not?

Find more posts tagged with

Comments

Garth McMillan

Generally components have a parameter "ls-page-name" which contains the path the the .page that contains the component. The hash that represents the component cache contains all the component parameters, so I don't think it would be cached across sites.

However, we are currently having issues with the component caching in 7.3.1. The cache hash isn't being generated correctly and thus components are caching across sites - eg. we are getting navigation/other information from a different site (based on which ever page the user first hit on the server).

We have a support case in progress to try and correct this.

kaleemS

Have you found the solution for it?

Actually, we are also having the same issue, where common components are getting cached across the sites.

Garth McMillan

Our "solution" (if you can call it that) was to do this:

Add 2 External Datums to the relevant components eg:

[HTML]

[/HTML]

And override the classes com.interwoven.livesite.external.ParameterHash and com.interwoven.livesite.runtime.model.page.RuntimeComponent to generate the cache hashes with the site name in addition to the page name.

It's a dodgy hack and we submitted our "fix" back to Autonomy a long time ago - they may have implemented some solution in a subsequent update.