Migration Module Changelog

Hello all,

We will be posting the Migration Module changes and improvements in this thread. We will also link this thread from the Migration Module. The post will be updated with the next Migration Module release.

Best wishes, 
Sitefinity team

Hi,

We have just rolled out an internal build - 4.2.1679.0 - containing improvements to the Migration module:

THIS IS A DEVELOPERS VERSION ONLY, BACKWARD COMPATIBILITY FOR YOUR DATABASE WILL NOT BE SUPPORTED WITH FUTURE VERSIONS. PLEASE DON'T UPGRADE YOUR PRODUCTION OR DEVELOPMENT WEBSITE WITH THIS RELEASE. USE ONLY TO TEST THE LATEST FUNCTIONALITY AND REMOVE ROADBLOCKING BUGS SO THAT YOU CAN CONTINUE WRITING YOUR CODE. THUS IT IS SUITABLE FOR DEVELOPMENT PURPOSES ONLY.


Release Notes

This Internal build improves the migration for Pages, Libraries and News. As a result of popular demand, Sitefinity 3.x .NET3.5 is now supported. There are number of bug fixes and improvements in Sitefinity as well.

Full list of changes:

What's New in the Migration Module

Pages
- Assemblies for Sitefinity 3.x .NET3.5
- Migrating Pages keeping their original and additional URLs with their extensions
- Migrating Pages and keeping their advanced settings from 3.7 - Caching options, head tags, Indexing options, SSL, ViewState
- Migrated Pages now appear published (used to be drafts before)

Metafields
- MetaData migration – Migrating 3.x metadata - metafields and values.Definitions of 4.x are updated, so the 3.x fields are visible in 4.x backend. Currently  implemented for blog posts, news & libraries.

Improvements in the Migration Module

Libraries
- Libraries migration improvements – bug fixes, better handling for image links and urls in content items.

Other
- Dates handling improvements
- The user is now notified when some of the selected modules for migration has been disabled in 3.7
- The user is now notified that the migration module does not support migration of multilingual projects if the 4.x is not configured to contain the same languages.
- Added "Test Connection” and “Check items count in module to migrate” functions
- The migration log is now visible in an auto-scroll window
- Stability fixes

Full changes can be found here - 4.2.1679.0 build details

Hello,

The 4.2 SP1 release delivers fixes for the following issues in the Migration module:

• The Migration Module now supports Sitefinity 3.7 Community and Standard edition projects, both .NET35 and .NET40
• Migration of pages fails when executed 2 times sequentially

• Images are not imported from all providers in 3.7
• Images attributes are not preserved (alt, custom sizes)
• Library size limitations are not migrated properly.
• Comments creation date is wrong.
• Visibility of migrated comments is not persisted

Hello all,

With this internal build we introduce the following improvements in the migration process:

THIS IS A DEVELOPERS VERSION ONLY, BACKWARD COMPATIBILITY FOR YOUR DATABASE WILL NOT BE SUPPORTED WITH FUTURE VERSIONS. PLEASE DON'T UPGRADE YOUR PRODUCTION OR DEVELOPMENT WEBSITE WITH THIS RELEASE. USE ONLY TO TEST THE LATEST FUNCTIONALITY AND REMOVE ROADBLOCKING BUGS SO THAT YOU CAN CONTINUE WRITING YOUR CODE. THUS IT IS SUITABLE FOR DEVELOPMENT PURPOSES ONLY.

What's new:

• Setting up the Migration service in SF 3.7 from the 4.2 Project Manager “Actions” menu. 
• Full support for all content modules and Lists. This covers Custom fields, urls, and all meta data.
  
• Categories are migrated with their original hierarchy for all modules.
• Tags – the migrated tags are associated across the different modules. 
• Tags & categories are added for Generic content module (Content Blocks) in 4.2 to reflect the functionality from 3.7.
• Authentication in the Migration service for SF 3.7. Please check the documentation on the Migration Module for more information.

Fixed:

• Problem with the Images Upload and migration from 3.7 resulting in generic GDI error and exception.
• Fixes in metadata migration – DateTime values are now correctly migrated
• Fixes in the transactions during the migration process.
• Fixed migration of urls containing non ASCII characters.

Please let us know how the migration process goes.

Hi all,

Sitefinity 4.3.1926.0 Internal build is released and ready for download in your accounts. It introduces many new features in the Migration Module.

THIS IS A DEVELOPERS VERSION ONLY, BACKWARD COMPATIBILITY FOR YOUR DATABASE WILL NOT BE SUPPORTED WITH FUTURE VERSIONS. PLEASE DON'T UPGRADE YOUR PRODUCTION OR DEVELOPMENT WEBSITE WITH THIS RELEASE. USE ONLY TO TEST THE LATEST FUNCTIONALITY AND REMOVE ROADBLOCKING BUGS SO THAT YOU CAN CONTINUE WRITING YOUR CODE. THUS IT IS SUITABLE FOR DEVELOPMENT PURPOSES ONLY. 
 

What’s New in "Migration Module 3.7 to 4.x"

• Users are migrated with their original passwords
• Introduced a new membership provider in 4.x that supports the default 3.7 authentication

• The following membership settings are migrated:  “hashAlgorithType”, “passwordFormat” and “requiresUniqueEmail”

• Generic content: Implemented migration. Shared Generic Content in 3.7 is migrated as Content Block Widget associated to a shared Content Block Item in 4.x.

• Image: Implemented migration of the widget and its association to image library
• List Display control:  Enabled migration of the widget and selected list items setting
• Bloggers list: Implemented migration
• Image gallery, Download list, News view, Blog posts, Events view: Implemented migration of the widgets and their common settings - paging, items per page, and comments.
• Specific settings are migrated for the widgets below:  
  • Image gallery: selected library, gallery template mode
  • Download list: selected library
  • News view: selected categories
  • Blog posts: selected blogs
• Navigation: Implemented migration of Site Menu, Site Panelbar, Site Tabstrip, Site Treeview, Dynamic hyper link, and Hyperlink modes
• Search box: Implemented migration of the widget, result page and word indexing mode
• Search results: Implemented migration
• News archive & Blog archive: Migrated as Archive widget in Sitefinity 4.x.

Content

• Blogs, Lists: Enabled migration of blogs and lists owners

Known Issues

• Migration of user profiles is not supported yet

Regards,
Kalina
Sitefinity Team

Hi all,

The latest internal build is live. With this build, we improve the widgets migration and automatically prevent migration errors in deploying widgets to the 4.x site. 

THIS IS A DEVELOPERS VERSION ONLY, BACKWARD COMPATIBILITY FOR YOUR DATABASE WILL NOT BE SUPPORTED WITH FUTURE VERSIONS. PLEASE DON'T UPGRADE YOUR PRODUCTION OR DEVELOPMENT WEBSITE WITH THIS RELEASE. USE ONLY TO TEST THE LATEST FUNCTIONALITY AND REMOVE ROADBLOCKING BUGS SO THAT YOU CAN CONTINUE WRITING YOUR CODE. THUS IT IS SUITABLE FOR DEVELOPMENT PURPOSES ONLY. 
 

New:

• Migration of 17 new widgets: Video, Login Status, Login Name, Login, Manage Profile, Login view, Create user, Tags list, Categories (list & tree), Subscription form, RssFeed (feeds are not migrated), RadTabStrip, RadMenu, RadPanelBar, XmlDataSource, DetailsView, GridView.
• Automatic compatibility test for custom 3.7 user controls: User controls in templates are automatically tested if they are compatible with 4.x. If the control is not compatible, each user control is wrapped in a special Sitefinity control wrapper that is visible only when editing a page and displays the error. After the user control is fixed, it will be shown instead.
• Automatic migration of widgets with the same type in 3.7 and 4.x. If there is a control with type Mynamespace.MyControl, with the same interface in both 3.7 and Sitefinity 4 this control will be automatically migrated with all the properties.
• Nested master pages and templates are processed in the correct order.
• Public API for migration of custom 3.7 widgets to 4.x - please check the following blog post: Custom widgets migration
• Almost zero configuration for the 3.7 service - The service needed for the migration now needs no special configuration, just this basic section:

  <system.serviceModel>
  <serviceHostingEnvironment aspNetCompatibilityEnabled="true" />
  </system.serviceModel>

  *Customers experiencing problems will have to replace their <system.serviceModel> section with the one from above.

• When “Rewrite user control Register tags for not working controls” option is checked and a master page fails to load during the migration, all the user and custom controls in the master page become commented. Exception makes all Telerik controls.

Fixes:

• Stability fixes in the Migration Module
• Service resolving fixes

Dear all,

Another Internal build is out. This time, it brings significant improvements over the Migration module and the migration process as a whole. Please check the release notes below:

New

The Migration module is now able to migrate multilingual content and user profiles. 

Migration of Multilingual Content 

• Multilingual migration is supported for all 3.7 modules, which were supporting multiple cultures;
• Multilingual modules in 4.x which were mono-lingual in 3.7, are set as multilingual in 4.x. In this case, the content is the same for all the languages. This is done for backward compatibility, so the 3.7 site behavior is intact in the migrated 4.x project;
• Multilingual pages have new main URL, including the current language suffix. The 3.7 pages URLs are added as additional in 4.x, so the old URLs will be still valid and the SEO will not be hurt. The reason for this is architectural differences between 3.x and 4.x.

User Profiles

• Migration of user profiles - Supported are the Asp.Net profiles together with their standard properties(Int, String, DateTime, Boolean);
• The 3.7 "Photo" property is also migrated, but is named "Avatar" in 4.x for compatibility reasons.

Fixes

• Migration of Masterpages and Templates having Ajax panels;
• Migration of external and group pages.