I'm having some issues with a DateRange field in one of my setups. The data is simply dropped on save in some cases. It seems like not even the validation code is executed. I can enter anything and the objects save successfully but the field remains empty.
I put a mysql dump for testing here on antwerp: /home/stefan/provenienz.sql. You can log in with stefan/stefan.
Try filling out the date ("Datierung") field on the "Info" screen for the objects BT_O_172 or BT_O_190.
Latest cleanup branch
This looks like the result of a bug that was fixed a couple of weeks ago, that had to do with how attributes are stored when "mustNotBeBlank" is not set and the date is blank. I see that the date element in question does not have this set so it was a candidate for the problem.
In the data itself you definitely have the results of this old bug. What happened, basically, is that when the value with "mustNotBeBlank" not set is saved without a value and exists on its own (not in a container), the ca_attributes record gets created but the ca_attribute_values record does not. The problem is that when the ca_attribute_values record fails (which it should) the ca_attributes record is not removed and you end up with ca_attributes records that have no corresponding values. It is this situation that causes subsequent saves to silently fail, and it also prevents the UI from removing the blank attribute.
This was fixed and should not be a problem going forward. For your data running the following query should solve the issue:
delete from ca_attributes where attribute_id not in (select distinct attribute_id from ca_attribute_values);
Please back up your data before running this
Alright, I will give this a shot once I'm home again. Thanks for the super quick answer!
Looks like this was it .... thanks!