nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Page cache issue in Sitepublisher page

System

Hi Techies,
I am facing caching issue on .page file when trying to render content based on query string.

I have created xsl component (Do not cache option chosen) to parse the data from DCR using DCR datum and used [QUERY_STRING] to pull the URL query string. Based on query string value I am trying to pull content from DCR on conditional check.

When working in TeamSite preview mode I am able to get expected result. But as soon as I PLC the .page to Stage environment, this functionality breaks and only shows cached version of page irrespective of query string passed, i.e. once published the page and hitting url .page?id=20140314 it shows content as per requested and now when query string is changed to show different content like .page?id=20140211 then it continue to show data of id=20140314.

Please help to disable caching for this scenario, i thought urls are treated different when query parameters changes.

Env details
TS- 7.2.1
LS- 7.2.1
Server Windows IIS 6

Thanks
Manu G

Find more posts tagged with

Comments

Rick Poulin

Was the cache option recently changed? (I'm thinking maybe you didn't update your page with the latest, or maybe you didn't publish the change to the runtime)

Generally speaking, it should work the way you expected here so there must be a small silly thing wrong somewhere. Finding it without having access to your server is difficult. Maybe post your external code and we can see if there's anything wrong there.

nipper

By chance are you using .Net or do you have Tomcat installed ?

Migrateduser

Was the cache option recently changed? (I'm thinking maybe you didn't update your page with the latest, or maybe you didn't publish the change to the runtime)

Initially cache option was set to "Until published" and then I changed to "Do not Cache" and then submitting the component and template to STAGING. Did update template and did PLC of whole page after that.

Generally speaking, it should work the way you expected here so there must be a small silly thing wrong somewhere. Finding it without having access to your server is difficult. Maybe post your external code and we can see if there's anything wrong there.

Only external code written is component is externalized by writing xsl in folder inside the content workarea rather than in component itself.

[html]

[/html]

Please guide.

Manu G

Migrateduser

By chance are you using .Net or do you have Tomcat installed ?

Its .Net environment.

Migrateduser

On the other hand I have not used any pragma cache or cache control tag in head section which is injected from page layouts (customized div layouts)

will it have anything to do from server side cache?

Or can I control a single page cache disable in cache.ccf file?

Thanks
Manu G.

nipper

Its .Net environment.

Thought as much. Cache in .Net is kind of funky.

Have you checked out the best practices for LSDS in .Net ?

Use ASPX controls for all dynamic content. LiveSite dynamic rendering, such
as component externals and page tokens, only render once in the .NET
environment and are then cached until the .page file is modified. IIS handles the caching for performance reasons.

Migrateduser

Hi Nipper,
I dont have best practice guide, can you please share the link. My second question was - is there a way to handle page specific cache disable functionality?

Thanks
Manu

nipper

You have to get it from the support site or have someone with access get it for you.

Look for this manual

LiveSite Display Services for .NET
Version 7.2.1
Technical Note

GRD

Use the XslControl server control that comes with LiveSite.Net. Instructions are in the docs that Andy pointed to. You'll have to do some fiddling if you want in-context editing to work, or create a support ticket for instruction.

The problem is that ASP.NET stores a compiled version of the virtual page and a DCR change, for instance, does not trigger a recompile. I know that in my last project we overrode the Virtual Path Provider to add a dependency on any referenced DCRs, thus causing the page to recompile if you deployed a referenced DCR. (I don't know why it's not like this out-of-the-box.)

There are already dependencies on on default.site and default.sitemap. You'll notice that if you change any one of those, the page gets recompiled.

-Greg

output_columns.jpg

Migrateduser

Hi Nipper/Greg,
Still no luck on how to proceed to solve this.
By any chance did you face caching issue via query string. I am sure using xsl transformation of XSL compontents it ought to work.
I dont have option for dotnet control.

Thanks
Manu G.

UC49_Mica.rptdesign