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
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
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 17:32:43 +0100] rev 4669
cleanup, typos
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
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
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 13:40:55 +0100] rev 4666
3.6 api update (introduced by merge)
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
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
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 12:52:57 +0100] rev 4663
merge
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 12:52:40 +0100] rev 4662
add XXX note
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 12:51:20 +0100] rev 4661
[form] cache field value in form.formvalues using (field, form) key since in some case the same field instance may be shared accross multiple forms, which may share the formvalues dict in case of sub-forms
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 12:49:37 +0100] rev 4660
cleanup
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 12:46:56 +0100] rev 4659
[form] complete 25de2eb0432b by ignore req parameters by default for all hidden fields
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 12:43:15 +0100] rev 4658
[form] add a new ignore_req_params attribute on field controlling value's retreival
for such field, such as eid/__type in entity forms, we don't want to consider values
from req.form since we may get undesired value (as reported by #714766). This new
attribute allow do specify that we don't want to consider req.form in such case.
Also, it seems that retreival of form values after a validation error suffer from
the same problem, so don't use form_previous_values for field with ignore_req_params
set to True (XXX though I suppose that may not be correct in some cases).