I have a website using Umbraco 4.7.2 and uBlogsy 2.0.0.1 - I need to upgrade it to MVC Umbraco 6. From the posts, I understand that uBlogsy need upgrade to version 3 for mvc support. However there's no clear answer to questions:
1) Can uBlogsy 2.0.* work with Umbraco 6.0.5 at all? [looks like blog posts work ok with umbraco 6, but not sure if that's a preferred way to go with the rest of the website in MVC, and if any custom blog changes in macro scripts will work]
2) Upgrading to uBlogsy 3 completely breaks the old posts created using v2. Are there any clean steps to guide us how to upgrade a website with uBlogsy2 to uBlogsy3?
3) Are there any chances that at some point in future uBlogsy support for older versions is halted for MVC projects?
1) Can uBlogsy 2.0.* work with Umbraco 6.0.5 at all?
No. Umbraco 6 brought in some breaking changes. You need to use uBlogsy 3
2) Upgrading to uBlogsy 3 completely breaks the old posts created using v2. Are there any clean steps to guide us how to upgrade a website with uBlogsy2 to uBlogsy3?
There are some doctype changes here and there. "Upgrading" is not really easy. I would do the folloing...
Package up your ublogsy 2.0 content tree
Install uBlogsy 3 on a fresh Umbraco 6 MVC
Install the uBlogsy content tree package you made in step 1
Deal with any issues involving changed doctype aliases
3) Are there any chances that at some point in future uBlogsy support for older versions is halted for MVC projects?
I'm currently supporting mvc and webforms in v3. I will fix major bugs in v2. I would recommend not migrating a site from webforms to mvc unless it gives you REAL business value. Migrating any site to MVC can be a real pain. Upgrading Umbraco versions is not such a big deal. However, uBlogsy did have some significant changes so it will unfortunately be a bit time consuming.
We took the approach of 4 steps you mentioned. And we figured that brought more than just doctype alises. We hve to deal with the conversion of macros, custom templates built on uBlogsy doc types with a hierarchy, and few other integrated parts involving the migration from WebForms to Mvc.
...and that brought much hope to us. Unfortunately we are neither located close to UK, nor may get chance to attend it being a non-profit organisation. Are you kindly going to share the outcome of that session out to everyone?
The session will be about how I personally migrated uBlogsy to Umbraco 6 and MVC. The migration itself was simple but time consuming.
The refactoring of doctypes, and moving functionality into packages was a choice that I consider a breaking change. Upgrading is "possible" but time consuming, and will require considerable of Umbraco and uBlogsy knowledge and experience.
Part of my presentation will be if it is actually worth migrating a webforms site to mvc. Most of the time the answer will be "hell no", as it can be like migrating from php to .net. It's not a migration, but a rebuild.
Probably not the answer you were looking for.
There are many options rather than a rebuild though. What exactly is your objective? What is the business value you are trying to acheive in upgrading?
Umbraco 6.0.5 and uBlogsy 2.0.0.1
I have a website using Umbraco 4.7.2 and uBlogsy 2.0.0.1 - I need to upgrade it to MVC Umbraco 6. From the posts, I understand that uBlogsy need upgrade to version 3 for mvc support. However there's no clear answer to questions:
1) Can uBlogsy 2.0.* work with Umbraco 6.0.5 at all? [looks like blog posts work ok with umbraco 6, but not sure if that's a preferred way to go with the rest of the website in MVC, and if any custom blog changes in macro scripts will work]
2) Upgrading to uBlogsy 3 completely breaks the old posts created using v2. Are there any clean steps to guide us how to upgrade a website with uBlogsy2 to uBlogsy3?
3) Are there any chances that at some point in future uBlogsy support for older versions is halted for MVC projects?
Eagerly awaiting your reply, Thanks!
Hi
Here are answers to your questions...
1) Can uBlogsy 2.0.* work with Umbraco 6.0.5 at all?
No. Umbraco 6 brought in some breaking changes. You need to use uBlogsy 3
2) Upgrading to uBlogsy 3 completely breaks the old posts created using v2. Are there any clean steps to guide us how to upgrade a website with uBlogsy2 to uBlogsy3?
There are some doctype changes here and there. "Upgrading" is not really easy. I would do the folloing...
3) Are there any chances that at some point in future uBlogsy support for older versions is halted for MVC projects?
I'm currently supporting mvc and webforms in v3. I will fix major bugs in v2. I would recommend not migrating a site from webforms to mvc unless it gives you REAL business value. Migrating any site to MVC can be a real pain. Upgrading Umbraco versions is not such a big deal. However, uBlogsy did have some significant changes so it will unfortunately be a bit time consuming.
Thanks for the clarity Anthony!
We took the approach of 4 steps you mentioned. And we figured that brought more than just doctype alises. We hve to deal with the conversion of macros, custom templates built on uBlogsy doc types with a hierarchy, and few other integrated parts involving the migration from WebForms to Mvc.
However we came across this: http://umbraco.com/follow-us/blog-archive/2013/3/5/codegarden-session-migrating-ublogsy-to-umbraco-6.aspx
...and that brought much hope to us. Unfortunately we are neither located close to UK, nor may get chance to attend it being a non-profit organisation. Are you kindly going to share the outcome of that session out to everyone?
The session will be about how I personally migrated uBlogsy to Umbraco 6 and MVC. The migration itself was simple but time consuming.
The refactoring of doctypes, and moving functionality into packages was a choice that I consider a breaking change. Upgrading is "possible" but time consuming, and will require considerable of Umbraco and uBlogsy knowledge and experience.
Part of my presentation will be if it is actually worth migrating a webforms site to mvc. Most of the time the answer will be "hell no", as it can be like migrating from php to .net. It's not a migration, but a rebuild.
Probably not the answer you were looking for.
There are many options rather than a rebuild though. What exactly is your objective? What is the business value you are trying to acheive in upgrading?
is working on a reply...