Global Office Directory
More Products
Share this page
Home > Community > Technical Blogs > Sitecore, What's New
Recent Posts
Sort By: Most Recent | Most Read | Highest Rated
This short post is about HTML tables in the Rich Text Editor (RE) in Sitecore v6.5.
Read More
Sitecore Rocks is the new black in the Sitecore world, and I do encourage all Sitecore developers to use this tool.
However, if you are still using the good old Developer Center, you have probably run into the problem of creating a SubLayout and want to have a codeBehind file.
Do you also work with lots of Sitecore sites locally and a partner license that expires each year?
I know this is not rocket science, but I want to share this little include config file that lets me have one license file in a default location and point all my sites to that license file. This way I only have to update one file when my license is renewed each year.
Below is the config file that you just need to put in the App_Config/Include folder of your Sitecore sites:
<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"> <sitecore> <settings> <setting name="LicenseFile" value="C:\inetpub\wwwroot\license.xml"/> </settings> </sitecore> </configuration>
Enjoy
This is my first blog post on the Sitecore Comunity hub. I will be moving all my old posts from mortenljungberg.blogspot.com over the comming weeks and shut down that blog, so if you were following my blog on blogspot, please update your feed ;)
Next blog post will probably be about my first Shared Source module which is in the making... more to come!
Update; the relevant posts from my old blog has now been moved! It was not that many, I gotta be more productive in the future ;)
I am mostly writing this post because I keep forgetting how to get a language different from the current context language through the Sitecore API based on a string value. So to remind myself; here we go:Language lang = Sitecore.Globalization.Language.Parse("da-DK");Sitecore.Context.SetLanguage(lang, true);From here on the language will be set as da-DK no matter what the current language is.(Remember this blog is for new Sitecore developers! So all you hardcore Sitecore developers don't give me heat for writing about too basic stuff ;))
Just a quick post about the new Icons in Sitecore 6.2. The new icons is actually just an update of the old ones to have a more Windows 7/Vista look (see small sample below). They can be found in the Website\sitecore\shell\Themes\Standard folder as zip files together with the old icons. The icon folders have the same names as the old ones just with "V2" appended. But when you want to use the new icons for example for a template they are not visible in the icon selector. You will still see the old ones! To use the new ones instead of the old, rename the zip archives of the old icon zip folders to something else and then unzip the "V2" zip archives, delete the V2 from the folder name and re-zip the folder. Now you should see the new icons
I know that most of you probably already know the importance of actively using the data source attribute on renderings. This has become even more important with the Online Marketing Suite.
So if you are new to Sitecore or just haven't thought about using the data source yet, read on. I am going to use the Nicam site as an example and show how we can use the same control to output different content based on the source attribute.
In the Above image there is a control outputting the text "D3X" on a red background with a link to the D3X page. The content item that holds the information for the control is not the current context item, but rather an item that the developer has pointed to when chosen to output that control on this specific page.
Now to change the content I could just change the values of the content item, but if I have used the "D3X - red" content item on other pages and wants to keep the content it would be smarter to use the data source attribute to point to another content item like the one above "D3X - grey". This way I can reuse the same control over and over on different pages (or on the same page) but change the actual content by pointing to different content items through the data source attribute. The data source attribute is found in the "Layout Details" when clicking on a control or in Design mode when highlighting a control and then clicking on properties. Setting the data source attribute actually means that you point to a different "context" item than the one requested by the URL. So you don't need to specify anything when extracting content from a field. for example outputting the text from a single line text field would just be: <sc:text field="field name"> Omitting the "select" statement means that Sitecore will use the context item. Online Marketing Suite Creating controls that uses the source attribute is especially important when using the OMS (Now called DMS) for personalization or multi variant testing. This is because the Personalization rules and MV testing both uses the data source to change the content item displayed through a control based on the rules that the user set up. Drop me a comment if you want more info about using the data source when setting up MV testing or personalization rules.
New functions, features, tips and tricks from Sitecore International Solution Architect Morten Ljungberg.
This website is designed to be fully functional with scripts disabled in browser. Please contact the webmaster for any suggestions