I've just upgraded an existing umbraco 3.0.6 site to umbraco 4.0.1, the upgrade wizard appeared and it went through the 5 steps without any obvious hassle. The only issue I am having is that the templates have not been changed into masterpage files, they're still the old umbraco v3.x templates, and when i create a new template it, it's using the old umbraco 3.x templates.
I've tried running the upgrade on a staging environment as welll as on my local machine; the upgrade wizard appears to run smoothly but the templates are not being upgraded.
Has anyone else come across this issue/know it's cause and know how to fix it?
there's nothing obvious in the log table. which files wouldn't have been copied?
I didn't upgrade to v 4.0.2.1 because I wasn't sure if you could go straight to it from 3.0.6. I have since upgraded to 4.0.2.1 but it still hasn't resolved the issue. Does anyone know which step of the wizard the upgrade on the templates are performed - I don't remember any step that indicates when this is done, it's more confirming DB details, running scripts and checking file permissions?
This might help someone else if future - it is not quite relevant to this thread, but will probably be found.
Before upgrading any site from v3 to v4 make sure that you remove any colons ( : ) from the template alias names. The alias names are used to create the masterpage file names and of course a colon, and in fact any other bad character in file names causes the process to fail without any message.
I had a lot of templates with alias such as:
Page: Master Content: Snippet etc.
I renamed them to:
tp_page_master tp_content_snippet etc.
I not tested the conversion again yet and I have run out of time today, but I will hopefully post my success here tomorrow. I've registed the bug in CodePlex
Upgrade to V4 - Templates not changed to ASP.NET Masterpages
Hi,
I've just upgraded an existing umbraco 3.0.6 site to umbraco 4.0.1, the upgrade wizard appeared and it went through the 5 steps without any obvious hassle. The only issue I am having is that the templates have not been changed into masterpage files, they're still the old umbraco v3.x templates, and when i create a new template it, it's using the old umbraco 3.x templates.
I've tried running the upgrade on a staging environment as welll as on my local machine; the upgrade wizard appears to run smoothly but the templates are not being upgraded.
Has anyone else come across this issue/know it's cause and know how to fix it?
Cheers
I presume you copied accross the masterpages folder and set the correct permissions?
Yep, the masterpages folder is there, and I gave necessary permissions to NETWORK_SERVICE / ASP_NET.
check the log table, see if it has anything indicated.
it's possible that not all the files were copied. Also, why didn't you upgrade to 4.0.2.1?
there's nothing obvious in the log table. which files wouldn't have been copied?
I didn't upgrade to v 4.0.2.1 because I wasn't sure if you could go straight to it from 3.0.6. I have since upgraded to 4.0.2.1 but it still hasn't resolved the issue. Does anyone know which step of the wizard the upgrade on the templates are performed - I don't remember any step that indicates when this is done, it's more confirming DB details, running scripts and checking file permissions?
Check your umbraco.config. Does it have a line: <useAspNetMasterPages>true</useAspNetMasterPages>?
HTH,
PeterD
This might help someone else if future - it is not quite relevant to this thread, but will probably be found.
Before upgrading any site from v3 to v4 make sure that you remove any colons ( : ) from the template alias names. The alias names are used to create the masterpage file names and of course a colon, and in fact any other bad character in file names causes the process to fail without any message.
I had a lot of templates with alias such as:
Page: Master
Content: Snippet
etc.
I renamed them to:
tp_page_master
tp_content_snippet
etc.
I not tested the conversion again yet and I have run out of time today, but I will hopefully post my success here tomorrow. I've registed the bug in CodePlex
Cheers
Steve
Just to follow up - that was the problem.
Cheers
Steve
is working on a reply...