Hey, Wonder if any of you fine people can help/advise on this one...
Today we made a simple change to a dropdown data type and added in two new values, one to the top of the list and one to the bottom.
When we went in to our Umbraco backend, the child nodes which contain this property had their values changed? the value which they had been changed to was the next one down from what it should be.
I had a google about for this but the only real relevant post I cam across was from Kevin Jump and it was a uSync bug from last year. We don't use uSync.
Anyway, sort of, hope someone else has experienced this issue and knows of a way to resolve it.
Are you able to provide a bit more information about your setup - e.g. what version of Umbraco you're running, maybe a screenshot of the datatype configuration (if it's not too sensitive to post here) etc.
My first suggestion would be to restore a database backup from just before the change if possible? If the content nodes have had their property values updated by changing the datatype there may not be a simple way to revert them, other than by repicking the content and republishing it.
You could also look in the database and maybe see what's happened to the IDs of the prevalues themselves, and compare that to a previous backup version - might shed some light on what actually happened.
You can find those in the cmsDataTypePreValues table, each one has an id, the node id of the datatype they belong to, the value (which is the text you see in the dropdown option), and a sort order.
Yesterday the new values were added in to the dropdown data type on our staging environment. One new value re-ordered to the top of the list and one at the bottom. Within the database and cache it looked like the values were correct but in Umbraco, the nodes had the next value down in the list from what it was previously, if that makes sense?
We tried different ways to revert this without having to restore live from a database backup or having to go through every single node and pick the correct values again, clearing cache, rolling back the new values on staging and couriering over to live again but neither of these worked.
So we ended up just re-picking the correct values from the list on every node. Unfortunately for us this property exists on two tabs within product child nodes so quite a bit of time to go through and re-select/re-publish. It would still be good to understand what we did wrong though as I'm sure this scenario will arise again in future.
Shouldn't we be able to edit a dropdown list of values without affecting published nodes which already have a value set against them?
Dropdown Datatype Doom
Hey, Wonder if any of you fine people can help/advise on this one...
Today we made a simple change to a dropdown data type and added in two new values, one to the top of the list and one to the bottom.
When we went in to our Umbraco backend, the child nodes which contain this property had their values changed? the value which they had been changed to was the next one down from what it should be.
I had a google about for this but the only real relevant post I cam across was from Kevin Jump and it was a uSync bug from last year. We don't use uSync.
Anyway, sort of, hope someone else has experienced this issue and knows of a way to resolve it.
Thanks Stuart
Are you able to provide a bit more information about your setup - e.g. what version of Umbraco you're running, maybe a screenshot of the datatype configuration (if it's not too sensitive to post here) etc.
My first suggestion would be to restore a database backup from just before the change if possible? If the content nodes have had their property values updated by changing the datatype there may not be a simple way to revert them, other than by repicking the content and republishing it.
You could also look in the database and maybe see what's happened to the IDs of the prevalues themselves, and compare that to a previous backup version - might shed some light on what actually happened.
You can find those in the
cmsDataTypePreValuestable, each one has an id, the node id of the datatype they belong to, the value (which is the text you see in the dropdown option), and a sort order.Thanks Chris,
We're on v7.10.5 at the moment.
Yesterday the new values were added in to the dropdown data type on our staging environment. One new value re-ordered to the top of the list and one at the bottom. Within the database and cache it looked like the values were correct but in Umbraco, the nodes had the next value down in the list from what it was previously, if that makes sense?
We tried different ways to revert this without having to restore live from a database backup or having to go through every single node and pick the correct values again, clearing cache, rolling back the new values on staging and couriering over to live again but neither of these worked.
So we ended up just re-picking the correct values from the list on every node. Unfortunately for us this property exists on two tabs within product child nodes so quite a bit of time to go through and re-select/re-publish. It would still be good to understand what we did wrong though as I'm sure this scenario will arise again in future.
Shouldn't we be able to edit a dropdown list of values without affecting published nodes which already have a value set against them?
Thanks Stuart
is working on a reply...