Raúl Jiménez

Pianist, geek, Sitecore specialist, loves driving.

So you think Sitecore fast query is faster than 'normal' Sitecore query? Not so fast. Let me act as a myth buster here.

A Sitecore query is evaluated against Sitecore items, and allow you to query items in the tree that meet certain criteria. In order to execute that query Sitecore may look at items in its cache, but if they are not there, it will get them from database. On the other hand, a fast query is always translated into SQL statements. It therefore bypasses caches, it always goes to the database.

This brings some advantages particularly when running in a cold installation where the items are not in the cache. When using a non-fast Sitecore Query the items will get added to the

Read more …

There are some situations where we would like to have multiple Standard Values for the same template. This is not possible with Sitecore. Or is it? The other day, whilst pondering about branches, I thought of this formula: Clones + Branches = Multiple Standard Values So this morning I have done this short video to show it in action: As you can see there are a few issues. I may try to sort them out, although I suspect some of them are

Read more …

30 tweets later we have reached the end of this little series. I confess it has been a bit harder than I anticipated. I had a list of 30 tweets prepared before I started. However only 60% of them actually made it... as I went along, I decided some of them where simply not interesting nor useful enough. This forced me to truly rack my brains in search of some other bits of Sitecore knowledge I could encode in less

Read more …

If you use rendering parameters in you components, you will create a Rendering Parameters Template to allow authors to edit and discover those parameters more easily. Authors can then use the Edit Component Properties option available in the Experience Editor, as long as you have the Designing view enabled. However, through that pop up your authors could modify caching settings, which is not ideal. It is also showing the datasource and placeholder fields, which they should not edit directly. Since

Read more …

URL troubles Nobody wants to see %20, or other strange encodings in their URLs. Some say they are not good for SEO. Some say your users will hate you for it. All I know is that they look ugly. And you will have them in your URLs if you your item names contain spaces. Of course you could train your users not to create items with spaces, but that renders the $name tokens a bit useless, since typically you do

Read more …