Hi all

My question is about how to get around a tricky caching problem in umbraco.

I'm using v 3.04 and are making use purely of the API to insert and update content. This all works

perfectly... but

When adding a new content item, it takes anything from 1-5 minutes for the page links to appear in the Umbraco UI. During this time I try opening new windows (IE and FF) and switching between the browsers and nothing seems to 'force' Umbraco to make my new content nodes ready to view through the browser.

What I have noticed is that when I create these document nodes in my web app and login to Umbraco, I can see the nodes there ( not greyed out ) but just missing the page link at the bottom of the document.

If I click Republish Entire Site in the UI this is all fine and the links appear. I'm trying to understand the mechanism that causes this and if its possible to short circuit the delay (from code not manually)

I've making calls like content.instance.RepublishNodesAsync after node creation with no luck , does anyone have a programmatic method for telling umbraco to immediately or just quickly publish the links?

Cheers

Mike Wheelaghan

dedicated umbraco head

:d/ :d/

Hi Dirk, thanks a lot for your quick response!

I'll try that out and let you know how it goes. I have been using

{document}.Publish( {user}) do you know the difference between these methods?

Thanks again