Jannick,

You need to provide more info than this. What is disappearing? Is it full pages, do they result in 404?

Is it pages output via xslt?

Do the missing pages appear in umbraco.config on republish, if not what's the status of the nodes in the umbraco tree?

Cheers,

Chris

Its not whole pages that are doing the magic trick, its fx. the title of the page or an element that has been updated that switches back and forth between the old and the new content.

Is this reproducable in your development environment?

When content disappears, what does the umbraco.config show? Does it have the old or new content?

This sounds like a caching issue. Have you tried shift-F5 refreshing your pages, and does the old content still appear?

Chris

I've tried clearing the browser cache, pressed ctrl+F5, deleted the umbraco.config and republished the entire site and I still get the problem.

An example is a submenu where the items are rendered then when I press F5 they sometimes dissapear and then reappear when I press F5 again.

Does that happen in all browsers? (Try firefox, chrome and IE). If things aren't visible, can you check the source-code if it is missing there?

It happens in all browsers and on different computers.

The source  code shows that the list items aren't even rendered with no content.

This is the XSLT I'm using to output the specified menu, id 1126 is the parent folder that the items live in:

<xsl:variable name="root" select="umbraco.library:GetXmlNodeById('1126')" />
<div class="hd">
<p>
<xsl:value-of select="$root/data [@alias='title']"/>
</p>
</div>
<div class="links">
<ul>
<xsl:for-each select="$root//node">
<li>
<a href="{umbraco.library:NiceUrl(@id)}">
<xsl:variable name="title">
<xsl:choose>
<xsl:when test="./data [@alias='title'] != ''">
<xsl:value-of select="./data [@alias='title']" />
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="@nodeName" />
</xsl:otherwise>
</xsl:choose>
</xsl:variable>
<xsl:attribute name="title">
<xsl:value-of select="$title"/>
</xsl:attribute>
<xsl:value-of select="$title"/>
</a>
</li>
</xsl:for-each>
</ul>
</div>

I've now turned off cache on macros and set the xml cache setting in the config to false.

The issue is still not solved, the problem occurs with macros and umbraco:items.

Hi Jannik,

Are you running on a webgarden (multiple worker processes)? That wil cause this to happen.

Ron

Yes Ron, thank you for pointing that out :) That little invisible '2' instead of '1'.

The problem have dissapeared, and now I will most certainly never forget that again.

Thanks!

is working on a reply...