Hi,
We are in the processing of QA a site we are upgrading from V13 to V17 and we found fields in V13 we could leave blank and update the page did not throw an error message.
But in 17 they are displaying an error message.
But if we put 1 in the the input area that showing the error then update, then go back in and remove the 1. it updates with out a problem no error message.
But if we then go back in and say add a second item to the control, and leave the col number empty / blank, then it throws an error.
It never did this in 13 what is going on???
Thanks.
Darren
Pretty sure I raised this as a bug already and it’s been fixed. Let me have a look.
Are you on latest v17?
Sorry - related but not quite the same - this was for dropdowns.
opened 03:38PM - 23 Sep 25 UTC
closed 07:49AM - 24 Sep 25 UTC
type/bug
release/16.3.0
### Which Umbraco version are you using?
16.2
### Bug summary
Related to bug … #20029
Following a migration / update from a v13 site: when I upgrade the “legacy option” is still selected for dropdowns which won't allow the page to be updated and published. Though these are highlighted in red - for editors this means trawling through tabs and block lists trying to find which property and then selecting blank again(which they won't understand).
The Blank default option is in the list after the fix on #20029 so can be selected and then the page published but I believe the migration should be setting this not whatever is forcing the (Legacy option).
<img width="440" height="475" alt="Image" src="https://github.com/user-attachments/assets/6d86be04-6403-4f02-b017-c08f0d60a040" />
Looking at the raw DB - looks like
[""]
is stored in earlier versions where as this blank is not stored at all (so no row in [umbracoPropertyData] for this property types if drop down is empty).
For my migration testing I guess I can just delete all instances of [““] in the tables but it would be a smoother upgrade if the dropdowns can either handle the old empty or they are deleted as part of the migration? This will lead to editor frustration if a dev updates and then leaves lots of older pages having to manually make these changes in dropdowns.
### Specifics
_No response_
### Steps to reproduce
Take a v13 site with a dropdown - leave some to the default blank option then upgrade to v16.2+
Try to publish and upgraded page and you'll get the error as the legacy option is selected.
### Expected result / actual result
Following migration the dropdowns will be set to the blank value (not sure if this should be a migration step or just making the backend cope with the [""] value?!)
Suggest you raise a bug with the steps. Doesn’t sound like the validation is right there.
I am running 17.6.2.
We also got some thing similar with color pickers.
V13 allowed blank values v 17 dose not.
Luuk
September 15, 2026, 7:35pm
6
I’m not sure if this is the case here, but you will find SOME differences between v13 and v17 here and there.
For your numeric field, it feels like there is a value ‘stuck’ under water that is not displayed, but triggers the validation. On that field that give you the error, if you enter ‘1’, save it and then empty it again, does that work?
If I set the filed to 1 and then save and publish, then go back in and clear the value and save and publish it works.
But If I go back in after that and say set the Auto flag I get the same error again, when the numeric value is empty.
