Thanks!

To simplify your implementation, you may consider the latest version of the staging module. It incorporates the partial cache clearing and the movement of files.

Since Sitecore Stage is Shared Source (and, hence, unsupported), getting on track with the latest version of the Staging Module may be the way to go.

Best wishes,
Derek

Really nice blog!

We are also facing same kind of issues sometime our front end servers shows “504 – Gateway Timeout” error. But we have configured something different which is as below:

1. Staging Module : – For upload and download sublayout files.
2. Stager Module :- For clearing cache partially. http://trac.sitecore.net/SitecoreStager

Now, our cache clearing stuff is totally managed by SiteCoreStager module. But sometimes our published changes dosen’t reflects up on front end servers which forces us to iisreset — which we would like to avoid.

Can you pls help us out. How it should be managed?

Thanks a lot,
Kiran Patil

thanks very much for this info.. from almost 3 hours I am fighting with this error and now your solution works.

thanks again

Thanks for your thoughtful analysis of the Sitecore Staging Module in this and in Part II. If you are using Sitecore 6, you might consider trying the Sitecore Stager, which can be found in Sitecore’s Shared Source Library. The Stager provides item-level cache clearing and, as a result, does not trigger the full cache clearing that you describe in your article.

Two more notes: 1) The Sitecore Stager does not replace the FTP/SOAP file transfer functionality that is part of the Staging Module. 2) The Sitecore Stager does clear the HTML cache, but not the item cache. So, if you use XSLT, the transformations will be processed again; but the database won’t be hit as with the standard Staging Module.

Best wishes,
Derek