Thu, 18 Feb 2010 12:57:57 +0100 Sylvain Thénault when modifying a persistent schema, erschema may miss some permissions which wil trigger a key error, but we don't want to crash on such cases stable
Thu, 18 Feb 2010 12:52:34 +0100 Sylvain Thénault fix #694445: related entity generates weird RQL which in turn generates weird SQL which fails on SQL Server stable
Thu, 18 Feb 2010 12:13:36 +0100 Sylvain Thénault fix 4626:c26b4df9fc90 (#703911): use can't rely on peid since it's not an actual eid when we're creating the parent entity stable
Thu, 18 Feb 2010 11:08:00 +0100 Sylvain Thénault [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
Thu, 18 Feb 2010 11:06:40 +0100 Sylvain Thénault minor cleanup: don't use builtin 'id' as variable name stable
Thu, 18 Feb 2010 10:57:50 +0100 Sylvain Thénault [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
Thu, 18 Feb 2010 10:55:41 +0100 Sylvain Thénault this is not the form renderer responsability to check for update permissions. Move this to autoform editable_attributes relation stable
(0) -3000 -1000 -300 -100 -30 -10 -7 +7 +10 +30 +100 +300 +1000 +3000 tip