Toronto Sitecore Technical User Group is Meeting May 30, 2012

These user group meetings are great places to meet others working with Sitecore and to learn some new things
as well.

Here are the details:

Toronto Sitecore Technical User Group - May 2012
Wednesday, May 30, 2012 from 5:30 PM to 7:30 PM (ET)
Toronto, Ontario

Click here to register.  Look forward to seeing you there.

Sitecore 6.2 and Change Password link on Login Page broken

I found in an installation of Sitecore 6.2 that the Change Password link on the Login page was broken.
Instead of going to sitename/sitecore/login/changepassword.aspx it was going to sitename/sitecore/changepassword.aspx

The fix is to look in the \Inetpub\wwwroot\sitecore\Website\sitecore\login folder and open the ChangePassword.aspx page.  Search for "ChangePassword" Change the a href to read:


<a class="LoginOption" href="login/changepassword.aspx">Change Password</a>

This will resolve the issue and you will get the change password page.

If you have any tips, tricks or resources you would like to share with the Guild, please email sitecoreguild@outlook.com

Installing Glass

For fans of SkyRim you may know that Glass is the weapon of choice.  In the Sitecore Realm the same applies.

Glass Sitecore Mapper is an object mapping framework for mapping Sitecore items directly onto an object model allowing you to model your entire Sitecore solution as a data model. The framework handles converting data to and from fields and pulling data from related items.

Instructions to install Glass

1. Join the Glass Google Group.  Its the place to go for support:
   
2. Install Powershell 2.0 if you don't have it already.
   It is available at: http://support.microsoft.com/kb/968929
   
3. Install NuGet Package Manager for Visual Studio. Available at:
   
   http://visualstudiogallery.msdn.microsoft.com/27077b70-9dad-4c64-adcf-c7cf6bc9970c
   
   
4. The following link provides detailed information on installing NuGet:
   
    http://docs.nuget.org/docs/start-here/installing-nuget
   
   
5. Make sure you open your solution in visual studio you want to install glass on.
   
6. Install Castle.Core from Nuget using "Install-Package Castle.Core"
   This is required because Glass is build upon these base classes.
   
7. Install Glass from Nuget using "Install-Package Glass.Sitecore.Mapper".
   If it installs correctly go to step 9.  If not check step 8 below.
   The following link has more information on how to do this:
   
    http://www.glass.lu/?page_id=462
   
   
8. When installing the package you may get an error like the following:
   

   Could not install package 'MostAwesomePackageEvar 1.0.0'. You are trying to install this package into a project that targets '.NETFramework,Version=v3.5', but the package does not contain any assembly references that are compatible with that framework. For more information, contact the package author.

        Don't fret it just takes a manual step.
   
   •  Click on your project and click on the reference to Castle.Core
   • Right click and click on properties.
   • Copy the reference path.
   • Remove the reference and attempt to re-add it by pasting the path you copied but remove the filename.
          Navigate up a directory and choose the net40-client directory.  You will end up with a path ending in \packages\Castle.Core.3.0.0.4001\lib\net40-client\Castle.Core.dll
   • Redo the install in step 6
9. Visit The Glass Google Group and Glass.Sitecore.Mapper Wiki and read up on usage.

If you have any tips, tricks or resources you would like to share with the Guild please email them to sitecoreguild@outlook.com

Sitecore custom error pages

In ASP.NET its as simple as a single web.config key (customerrors), but for Sitecore there
are a few added steps that need to be done like making sure your page is in the ignoreurls and
changing the other Sitecore Custom Error settings.

I found a really good article that walks you through this step by step:

Sitecore Custom Error Pages

If you have any tips, tricks, articles or resources you would like to share with the guild,
please email them to sitecoreguild@outlook.com or post them as comments.

The security settings for the current language prevent you from seeing this item. To continue, select another language from the Language drop-down list on the Versions tab.

I saw a few blog posts on this error but took me a while to figure out what the real solution was.  Here is a description of the error and how to resolve it.

Problem: A user is assigned access to edit content in the Content Editor but when they click on an item to edit they get the following error:

The security settings for the current language prevent you from seeing this item.
To continue, select another language from the Language drop-down list on the Versions tab.

Reason: In the content editor on the Master database there is a folder  at /system/languages
This folder has a new security key called language:read and language:write.  By default this is assigned to sitecore\everyone.  This is fine provided that only local users are accessing the content editor but if you are using ad domain\everyone will be default be denied.

Solution: Click on security and access viewer.  Navigate to /system/languages.  click on assign and assign the {your domain}\everyone access to language:read and language:write.   If you want to do this for a specific language you can open the folder click on the language and set these access properties there.

302 object moved for temp/iconcache images

Sometimes when you log into the Sitecore Admin you may see that icons are not loading.  When you look in fiddler you will see that its returning a 302 - Object moved message.

I found a few other causes to the problem stated on other blogs and in some cases this may solve your problem.
These range from missing images in the temp/IconCache folder to missing zip files in the "sitecore\shell\Themes\Standard" folder.  Once the icons exist in both places if they still will not show up then
you will need to try my solution below:

The solution is to stop IIS, delete all the files in the temp/iconcache folder then restart IIS.  Now when you log into the admin, this will force sitecore to refill the iconcache and the icons will show up again.

If you have any tips, tricks or resources you would like to share with the Guild please email them to sitecoreguild@outlook.com and we will post them here.
You can also tweet them referencing @sitecoreguild

Tips On Setting up Sitecore Content Delivery Server

Setting up a Content Delivery Server the first time is not easy but there is help.

Firstly, download the Sitecore Scaling Guide and the SwitchMasterToWeb.Config

from this SDN Link

Once you have followed the above steps you may get the following error:

Exception: System.InvalidOperationException
Message: Could not find configuration node: databases/database[@id='master']

If you are running Sitecore 6.5 the fix is to open the SwitchMasterToWeb.Config and paste this at the bottom just inside the  </sitecore>
tag:

<settings>
<!– extra setting to bypass analytics error –>
<setting name=“Analytics.DefaultDefinitionDatabase“ value=“web“ />
</settings>

If you still get the error or are running 6.4 or lower then there may be references to master in the web.config that were added after the standard install.  One example is the news mover module.  The solution is to find all references to these (<database>master</database>) in your web.config and comment them out.