Problem, tips and trix when migration an EPiServer 4 to CMS 5 site.
Overall
The upgrading from EPiServer version 4 to CMS 5 is a hard to do upgrade that has very many breaking changes and takes a long time to do so don’t under estimate the work.
Known problems
Windows integrated security the VPP functionality has a bug that makes it impossible to mix anonymous and windows integrated users in the same VPP.
Calling custom .ASPX pages with the id parameter
In EPiServer 4 it was possible to link to other pages in the EPiServer installation with the id parameter as a normal .aspx page. In CMS version 5 and above this has been changed to support multiple page types for one content page.
Example:
The link should be "/MyNonEpiServerPage.aspx?id=3&orderBy=price
but it's renderd as "/en/?orderBy=price"
To fix this
1) Change the behaiviour of the .aspx page so it uses another parameter name than id
2) Create a new CustomProperty that inherit from PropertyXhtmlString
3) Change all links in the database or override the LoadData of the custom property and make it replace the "id" with the new parameter
public override void LoadData(object value)
{
value = ChangeMyIdParameterToNewParameter(value);
base.LoadData(value);
}