I've done some reading and not found definitive answer. Is there a programmatic way or through the macro/XSLT route to instantly publish content?
Our scenario is this, we have an Umbraco site, which the end user posted a news article through the back end, however the news article did not go live immediately. The user was a little unhappy as it was a time imperetive piece. We spent a little time looking into it and could see the config had been updated with the content, but it was not on the front end.
We recycled the app_pool which caused the article to appear, but this is not an ideal solution as in the future we may not be available to do this and articles may need to go live outside of working hours.
Yes, we follow a standard installation procedure when creating a new Umbraco site.
It appears as though Umbraco caches content for approximately 20 minutes (this is all supposition), we need a way to bypass this without going to the app_pool.
Caching and new content
Hi all,
I've done some reading and not found definitive answer. Is there a programmatic way or through the macro/XSLT route to instantly publish content?
Our scenario is this, we have an Umbraco site, which the end user posted a news article through the back end, however the news article did not go live immediately. The user was a little unhappy as it was a time imperetive piece. We spent a little time looking into it and could see the config had been updated with the content, but it was not on the front end.
We recycled the app_pool which caused the article to appear, but this is not an ideal solution as in the future we may not be available to do this and articles may need to go live outside of working hours.
Appreciate any suggestions you may have?
Thanks,
Darryl
Is all permissions correct on the server folders?
http://umbraco.org/documentation/books/important-files-and-folder-structure
Hi Anders,
Yes, we follow a standard installation procedure when creating a new Umbraco site.
It appears as though Umbraco caches content for approximately 20 minutes (this is all supposition), we need a way to bypass this without going to the app_pool.
is working on a reply...