Today in a Friday Case category, which features support cases causing to pull my hair out, a very interesting issue I’ve had with a customer reporting that unapproved content was going live quite unexpectedly.
After witnessing the issue with my own eyes when an item just created and not pushed via workflow was magically showing up in production after a few minutes, I decided to investigation Sitecore configuration. This revealed a PublishAgent that was enabled to run frequently, but nothing else.
Top 5 posts
-
Hi there, Today I am proud to announce a preview release of a component that extends the standard Sitecore Searching mechanisms, specifica... -
I have a rule of thumb. If I am being asked the same question twice a week, I am writing a blog post. Today I have been asked the same quest... -
Greetings, Back in 2010 at the first Dreamcore conference, I was honored to present on two topics: ” Data Retrieval Techniques with Sitecor...
-
I have more than 30 Sitecore instances on my laptop, and I often need to have a clean of a specific version/revision of the product done qui...
-
Greetings, Today I would like to present to you a prototype I have been working over past couple of weeks. This solution is built around a ...
Friday, August 26, 2011
Wednesday, August 24, 2011
Partial Language Fallback Module Update
Today I pushed a small update to the Partial Language Fallback module which I introduced a while back. Check out this quick screencast below. For the full list of changes hit “read more”.
Friday, August 19, 2011
Sitecore Output Caching: Kick it up a Notch
Ever wondered how Sitecore caches works? It is pretty cool, actually. Sitecore can cache the output of any presentation component that it is aware of (Sublayout, WebControl, XSL Rendering). Basically, this output may vary on data context (Context Item or Datasource), device, whether user is logged in or not, parameters passed to the rendering, query string and Context user: This gives a ton of options and in most cases this is sufficient, but what if the output of your rendering depends on inner logic embedded within the control? Sometimes you could solve this with VaryByParm and by passing different parameters to the rendering, but what if that’s not the case?
This is exactly the use case I have been presented during another onsite visit with a customer.
Here is a very simple way of extending the cache variation logic for a Sublayout.
Monday, August 01, 2011
Web Forms File Upload: 2 Exceptions [Common Errors]
If you are having trouble with the File Upload field within the Web Forms for Marketers module, specifically the form submission fails with a generic error, check your Sitecore log file. If you see either of the following two exceptions, there is a solution! Read on.
Subscribe to:
Posts (Atom)