Tue, 23 Feb 2010 20:23:46 +0100 auto-delete relation with single cardinality using execute, not unsafe_execute, so permissions are correctly checked stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 20:23:46 +0100] rev 4673
auto-delete relation with single cardinality using execute, not unsafe_execute, so permissions are correctly checked
Tue, 23 Feb 2010 20:22:40 +0100 fix tests stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 20:22:40 +0100] rev 4672
fix tests
Tue, 23 Feb 2010 18:21:30 +0100 add */*.py to default MANIFEST.in to avoid pb such as #719282 in the future stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 18:21:30 +0100] rev 4671
add */*.py to default MANIFEST.in to avoid pb such as #719282 in the future
Tue, 23 Feb 2010 17:39:13 +0100 fix #615379 by checking admin user exists instead of making think everything is fine stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 17:39:13 +0100] rev 4670
fix #615379 by checking admin user exists instead of making think everything is fine
Tue, 23 Feb 2010 17:32:43 +0100 cleanup, typos stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 17:32:43 +0100] rev 4669
cleanup, typos
Tue, 23 Feb 2010 17:32:31 +0100 [form] fix #719285, due to multiple calls to restore_previous_post, by proper refactorings stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 17:32:31 +0100] rev 4668
[form] fix #719285, due to multiple calls to restore_previous_post, by proper refactorings * move __init__ code from FieldsForm to Form. Must behaviour here should actually be in the Form base class * avoid buggy duplicated call to restore_previous_post * move some code that was in the form renderer to the form'__init__ method (__redirectpath & __form_id hidden input handling)) * 'formvid' should now be specified on form selection, not on form rendering
Thu, 18 Feb 2010 14:30:23 +0100 [fix] Apply fulltextindexed change in the actual index stable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 18 Feb 2010 14:30:23 +0100] rev 4667
[fix] Apply fulltextindexed change in the actual index Change of the fulltextindexed attribute of a CWAttribute did actually change anything for already existing entity (but apply to new one). This patch fix this behaviour: * A new SingleLastOperation, UpdateFTIndexOp, to reindex entity whose ftindexation changed during a commit. This data is read from session.transaction_data['fti_update_etypes'] * The SourceDbRDefUpdate operation to store Etype who modify they fulltextindexed of attribute in session.transaction_data['fti_update_etypes']. * A new test is added to check the behaviour
Tue, 23 Feb 2010 13:40:55 +0100 3.6 api update (introduced by merge) stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 13:40:55 +0100] rev 4666
3.6 api update (introduced by merge)
Tue, 23 Feb 2010 13:19:16 +0100 when validating a form, we should properly call 'actual_fields(form) on edited field else compound field are not correctly processed stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 13:19:16 +0100] rev 4665
when validating a form, we should properly call 'actual_fields(form) on edited field else compound field are not correctly processed
Tue, 23 Feb 2010 12:59:30 +0100 #714109: [selectors] non_final_entity should implement score_class stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 12:59:30 +0100] rev 4664
#714109: [selectors] non_final_entity should implement score_class
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 tip