Drupal Association members fund grants that make connections all over the world.
confg->save() is called we call
Ensures that re-inserted keys appear in the same location as before, in order to ensure an identical order regardless of storage controller. A consistent order is important for any storage that allows any kind of diff operation.
However is having some unforeseen consequences in
If we create a text radio list with the following options:
Then the radios on the default setting screen will be:
This definitely matters as the user should be able to define the list in whatever order they choose.
Looking at Zend config and Symfony config components neither of them change the key order. I think the current solution is like altering db_insert data using a hook which would be definitely be considered a bad idea. The config system should take arrays of data and save them - and do nothing to change the array. When a system requires this data again it should return it exactly as it was given.
PASSED: [[SimpleTest]]: [MySQL] 42,070 pass(es). View
PASSED: [[SimpleTest]]: [MySQL] 42,298 pass(es). View
FAILED: [[SimpleTest]]: [MySQL] 42,134 pass(es), 1 fail(s), and 0 exception(s). View
PASSED: [[SimpleTest]]: [MySQL] 42,127 pass(es). View