Documentation clarity, improved error handling, media migration questions, member migration failure. #490
Description
Feedback, Questions, and Issues
Hi, team. I have several topics after syncing with a user working with the migration tool.
Feedback: More clarity or warnings that the XbyK project should not be upgraded past the version that is required for the latest version of the migration tool.
Feedback: Improved error handling and error messaging. Documentation clarifying the logging settings in the tool configuraiton.
Questions: How does the migration tool handle assets that are stored in Azure Blob Storage? Are there any special considerations that are not covered in this page of our documentation?
Bug report: User/member migration fails if there is trailing whitespace certain fields, such as email.
Feedback context
Some users might get the wrong idea about keeping up with the latest version of XbyK, and unintentionally leave their project incompatible for continued migrations. (This can also become documentation feedback for the Kentico docs.)
A couple of examples on error handling:
1. If there is a version mismatch for the tool, it should clarify both the current incorrect version, and the version the tool is expecting.
2. When performing the migration, errors and the stack traces that are being logged are important. But while the tool is running, it may help to know how to view clearer logs. Additionally, providing likely causes of certain errors may help users fix issues. No expectation to cover every possible outcome, of course.
Questions context
A lot of users use Blob storage for media in X13 and older. It is unclear if there are special steps that must be taken or if the migration guide linked above is suitable enough. (This can also become documentation feedback for the Kentico docs.)
Bug report context
In this user's particular case, the project is a K12 instance. Problem users had email fields that were stored like "[email protected] ". Note the additional whitespace. This would cause users to fail to migrate, and then additionally caused content made by these users to also not migrate. A possible solution would be to include whitespace trimming when the migration tool runs.