best practise

MVP Nomination

21.01.2015 — Leave a comment

Wohooooo, awesome things happened to me! On November 27th 2014, I received an email from Sitecore Headquarter. They nominated me as MVP (Most Valued Professional).

I hope I doesn’t end up like Leonardo DiCaprio… always nominated for an Oscar, but never won. 😀

My hope that it’s folding this year, is rather low, because I don’t have much Blog entries, Stackoverflow comments or even Sitecore Forum threads and comments, but nevertheless at least one great Sitecore Translation module on Sitecore Marketplace!

We have 3 huge Sitecore projects of global playing customers in the company I work and my focus is on: Work! Work! Work! Do some new best practices! Work! Work! Dive into the deeps of Sitecore! Work! Family! Work! 😀

No fun! Even in my free time (mostly at night) I work on a Sitecore project which will be released in March and just believe me, this project is full of Sitecore best practices like Dynamic Key Placeholder (for sure), a great structure, forms created with Web forms for Marketers (read my next blog about WFFM), Glass.Mapper with Interface based Models and inheritance templates, Customer data imports through scheduled tasks and many more!

Uhm, lots of stuff to write hundreds of blogs! The day should have 48 hours to find the time to wrote blogs. 😉

Stay excited 😉

Best regards Dirk

Advertisement
Sitecore

Sitecore and Bundling

23.03.2014 — 1 Comment

A short note on Sitecore and Bundling.

If you use Bundling within your WebApplication you will maybe wondering why your Script and css files not rendered properly:

 Failed to load resource: the server responded with a status of 404 (Not Found)
 http://YourDomain/sitecore/service/notfound?item=%2fbundles%2fmodernizr&user=sitecore%5cadmin&site=YourSiteName

or

 Failed to load resource: the server responded with a status of 404 (Not Found)
 http://YourDomain/sitecore/service/notfound?item=%2fcontent%2fcss&user=sitecore%5cadmin&site=YourSiteName
–

Sitecore tries to resolve your Bundles as an item. But you can get rid of this with a simple setting adjustment in web.config.

<setting name="IgnoreUrlPrefixes" value="/sitecore/default.aspx|/trace.axd|/webresource.axd|/sitecore/shell/Controls/Rich Text Editor/Telerik.Web.UI.DialogHandler.aspx|/sitecore/shell/applications/content manager/telerik.web.ui.dialoghandler.aspx|/sitecore/shell/Controls/Rich Text Editor/Telerik.Web.UI.SpellCheckHandler.axd|/Telerik.Web.UI.WebResource.axd|/sitecore/admin/upgrade/|/layouts/testing" />
–

Here we go! Just add your bundle-urls pipe-separated to the IgnoreUrlPrefixes-value

<setting name="IgnoreUrlPrefixes" value="/sitecore/default.aspx|/trace.axd|/webresource.axd|/sitecore/shell/Controls/Rich Text Editor/Telerik.Web.UI.DialogHandler.aspx|/sitecore/shell/applications/content manager/telerik.web.ui.dialoghandler.aspx|/sitecore/shell/Controls/Rich Text Editor/Telerik.Web.UI.SpellCheckHandler.axd|/Telerik.Web.UI.WebResource.axd|/sitecore/admin/upgrade/|/layouts/testing|/bundles|/Content/css" />
–

Best practise:

It’s highly recommended to patch such Settings in your own Settings.config-file in App_Config/Include-Folder like this:

<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
  <sitecore>
   <settings>
       <!-- IGNORE URLS
       Set IgnoreUrlPrefixes to a '|' separated list of url prefixes that should not be
       regarded and processed as friendly urls (ie. forms etc.)
       -->
       <setting name="IgnoreUrlPrefixes">
         <patch:attribute name="value">/sitecore/default.aspx|/trace.axd|/webresource.axd|/sitecore/shell/Controls/Rich Text Editor/Telerik.Web.UI.DialogHandler.aspx|/sitecore/shell/applications/content manager/telerik.web.ui.dialoghandler.aspx|/sitecore/shell/Controls/Rich Text Editor/Telerik.Web.UI.SpellCheckHandler.axd|/Telerik.Web.UI.WebResource.axd|/sitecore/admin/upgrade/|/layouts/testing|/bundles|/Content/css</patch:attribute>
       </setting>
     </settings>
   </sitecore>
</configuration>