We have noticed in development that on updating Obsolete Content Picker to Content Picker, any content we have set up is removed. This is far from ideal as would be a fairly large job for us to go through and re-add the content for all cases in all our environments.
We have not noticed the same behaviour for Media Picker. Content is not affected as we have found for content picker.
Are we missing something or is there no way around this and will we have to go through the content and re-populate it following the data type updates?
Changing the editor for a data type doesn't change the stored data for any existing content using that data type. So you still have the integer IDs stored in the database, but the editor now expects to be given a UDI so it displays nothing selected.
Unfortunately I don't think v7 provides a way to convert the existing data. I've submitted a pull request here to handle the conversion during the migration to v8.
Hello, we are also facing the same issue where on changing obsolete content pickers to new content pickers, the values are not showing in the interface and the site also breaks.
As per Umbraco upgrade process to V8, they strongly suggest to first change these obsolete properties.
But if we change, our values are getting lost (not sure in the DB but in the UI at-least its not showing.
Content lost when updating from (Obsolete) Content Picker to Content Picker
We are looking to upgrade Umbraco from v7 to v8 and to prepare for the content migration discussed here: https://our.umbraco.com/documentation/getting-started/setup/upgrading/migrating-to-v8 we are following instructions to update all Obsolete Data Types to their updated counterparts.
We have noticed in development that on updating Obsolete Content Picker to Content Picker, any content we have set up is removed. This is far from ideal as would be a fairly large job for us to go through and re-add the content for all cases in all our environments.
We have not noticed the same behaviour for Media Picker. Content is not affected as we have found for content picker.
Are we missing something or is there no way around this and will we have to go through the content and re-populate it following the data type updates?
Many Thanks, Ben
Changing the editor for a data type doesn't change the stored data for any existing content using that data type. So you still have the integer IDs stored in the database, but the editor now expects to be given a UDI so it displays nothing selected.
Unfortunately I don't think v7 provides a way to convert the existing data. I've submitted a pull request here to handle the conversion during the migration to v8.
Thanks for the clarification Steve. Will look out for approval of the pull request!
Hello, we are also facing the same issue where on changing obsolete content pickers to new content pickers, the values are not showing in the interface and the site also breaks.
As per Umbraco upgrade process to V8, they strongly suggest to first change these obsolete properties.
But if we change, our values are getting lost (not sure in the DB but in the UI at-least its not showing.
Any help would be greatly appreciated.
Did you end up resolving this? I'm experiencing the same issue.
is working on a reply...