Thu, 18 Feb 2010 11:08:00 +0100 [form fields] nicer behaviour of the password field: don't put internal field value on edition (triggering validation error if one validation without removing the value, due to confirmation mismatch), and don't show the field as required in such case stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 11:08:00 +0100] rev 4628
[form fields] nicer behaviour of the password field: don't put internal field value on edition (triggering validation error if one validation without removing the value, due to confirmation mismatch), and don't show the field as required in such case
Thu, 18 Feb 2010 11:06:40 +0100 minor cleanup: don't use builtin 'id' as variable name stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 11:06:40 +0100] rev 4627
minor cleanup: don't use builtin 'id' as variable name
Thu, 18 Feb 2010 10:57:50 +0100 [forms/inline] fix #703911: add new link disappears if inline box removed. Since we've the information, we must specify the target type else we get random cardinality on ambiguous relations stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 10:57:50 +0100] rev 4626
[forms/inline] fix #703911: add new link disappears if inline box removed. Since we've the information, we must specify the target type else we get random cardinality on ambiguous relations
Thu, 18 Feb 2010 10:55:41 +0100 this is not the form renderer responsability to check for update permissions. Move this to autoform editable_attributes relation stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 10:55:41 +0100] rev 4625
this is not the form renderer responsability to check for update permissions. Move this to autoform editable_attributes relation
Thu, 18 Feb 2010 10:54:50 +0100 turn default logging threshold to warning (we usually want them), and log 'no schema for eid' pb using warning instead of error, so we see them in logs but not during migration stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 10:54:50 +0100] rev 4624
turn default logging threshold to warning (we usually want them), and log 'no schema for eid' pb using warning instead of error, so we see them in logs but not during migration
Thu, 18 Feb 2010 09:26:04 +0100 pfff, sorry to keep messing with default/stable... stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 09:26:04 +0100] rev 4623
pfff, sorry to keep messing with default/stable...
(0) -3000 -1000 -300 -100 -30 -10 -6 +6 +10 +30 +100 +300 +1000 +3000 tip