XML schema has some major changes that affect XSLT scripts.
Custom generic properties are no longer accessed via /data [@alias = 'aliasName'] snippet. From now on you can use /aliasName to select custom data. This means that every custom property is now described by separate XML node with alias as its name.
Merging lots of scripts can be a pain. There are to solutions for this. Easy one: switch UseLegacyXmlSchema setting to true in umbraco.Settings.config. This will support old scripts.
And solution which will take time and effort: merge scripts. Tommy Poulsen posted a link to his web-tool that provides automated script merging. Although this way will need testing and some scripts has to be fixed manually anyway.
Also there's an issue with media files scheme. From now on if you need to access media file in a folder you have to
- Use GetMedia providing folder ID
- Access file via /File/umbracoFile XPath.
Second part was a troublesome for me. Supposedly this way you can get file path:
<xsl:value-of select="umbraco.library:GetMedia
($currentPage/panel1, 'false')/File/umbracoFile"/>
* This source code was highlighted with Source Code Highlighter.
But nonetheless this didn't work for me. Took some time to get this solution:
<xsl:value-of select="umbraco.library:GetMedia
($galleryRoot/imgFolder, 'true')
/descendant-or-self::*[@nodeTypeAlias='File']/umbracoFile"/>
* This source code was highlighted with Source Code Highlighter.
And last one. Previously we could use this code to get related nodes:
select="$currentPage/node
[@nodeTypeAlias = 'SomeGallery' ]"
* This source code was highlighted with Source Code Highlighter.
Now we need to use this:
select="$currentPage/descendant-or-self::*[@isDoc]"
* This source code was highlighted with Source Code Highlighter.
Or:
select="$currentPage/docAliasName[@isDoc]"
* This source code was highlighted with Source Code Highlighter.
Where docAliasName is document alias. This caused by another naming convention change: now every document is saved in xml node named by document type alias.
Anyway, that's the biggest trouble, Umbraco is fast and stable, everything else is done as usual.