Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.if I change the description of a field, all the nodes which were created sort of break. I no longer tell which choise the user entered since the actual stuff that is stored in the database is the string itself...
A hackish fix would be to update all nodes when the admin changes the string.
A real solution would require storing IDs of the choices.
Comments
Comment #1
killes@www.drop.org commentedwas wrong module
Comment #2
karens commentedFixed in latest commit. I decided the best option was to store meaningful option keys that won't break if option list is altered by using drupal_map_assoc() on the option list. This way an option list for a number field like 10, 15, 20 will store those values instead of 1, 2, 3 and and option list for a text field like 'First', 'Second', and 'Third' will store those values in the text field.
Comment #3
karens commentedHmm, maybe not. It was already storing the array index as the value but that wasn't working reliably since the index value can change, but my new method doesn't really address what you were saying either. The better solution is probably something like what is discussed at http://drupal.org/node/89172. This needs more investigation, which could be discussed more in that thread.
Comment #4
(not verified) commented