Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
v8 - Remove legacy drop downs #3414
This removes all of the legacy drop down property editors and deprecated logic. We now only have one Drop down property editor and it only stores values in the database and cache in a single way which is the string values that have been selected. There is no more 'publishing keys' type of stuff and we no longer store the INT ids that were based on the pre-value items (which also no longer makes sense because pre-values are just json configuration in v8). There are various other fixes too like the 'multiple' option for drop downs was broken.
@Shazwazza I had the following issue/s after the migration had run
All properties were converted to use the
Next issue is that my page was no longer in the cache, so I republished the node and got the following exception (see screenshot) where it was not expecting a string but an integer instead.
I then thought OK I would remove these properties from my doctype so I could sucesfully publish the node without an error being thrown, however the node was still reporting that it was published but not in the cache.
After going to the settings section and using the Published Status dashbaord aka NuCache. Clicking the Reload button throws the following exception - see YSOD below. So I currently can not see my page & values rendering out from the template to see if some of this was sucessful or not.
I get similar test results as Warren.
I created a doctype with one of each dropdown type. After upgraded they were correctly updated to the new flexible dropdown type. My data on the node didn't get updated correctly and I lost the selection of most of my property editors.
If I try to republish the node I get a YSOD: