Wed, 24 Apr 2013 17:39:10 +0200 [ldap] refactor attributes mapping handling
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 24 Apr 2013 17:39:10 +0200] rev 8918
[ldap] refactor attributes mapping handling * use explicit attributes lists when calling ldap search * direct and reverse attributes maps contains now the same elements.
Wed, 24 Apr 2013 14:00:52 +0200 [ldapfeed] add support for multiple email addresses from ldap
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 24 Apr 2013 14:00:52 +0200] rev 8917
[ldapfeed] add support for multiple email addresses from ldap Multiple emails case was ignored before this change. email test
Wed, 24 Apr 2013 15:37:43 +0200 merge 3.16.x fix in 3.17.x branch
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 24 Apr 2013 15:37:43 +0200] rev 8916
merge 3.16.x fix in 3.17.x branch
Wed, 24 Apr 2013 15:33:49 +0200 [session] fix hooks_control backward compat
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 24 Apr 2013 15:33:49 +0200] rev 8915
[session] fix hooks_control backward compat Session object have no ``hooks_control`` control method. it has ``allow_all_hooks_but`` and ``deny_all_hooks_but`` ones. Regression introduced in bd5b5759c9b3.
Fri, 19 Apr 2013 16:25:45 +0200 [facet js] fix reordering of facet check boxes. Closes #2732947 stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Apr 2013 16:25:45 +0200] rev 8914
[facet js] fix reordering of facet check boxes. Closes #2732947 Before this patch, when one select an element, it's moved to the top of the select content. Fine. But when it's later deselected, it stays there instead of moving back to its original location. This patch fixes that by introducing a facetCheckBoxReorder function which properly reorder the whole facet, instead of buggy attempt to locally reorder.
Wed, 24 Apr 2013 14:40:09 +0200 [vreg] (re)build entity classes cache after registry initialization. stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Apr 2013 14:40:09 +0200] rev 8913
[vreg] (re)build entity classes cache after registry initialization. This fix potential memory fragmentation issue. Closes #2719113
Wed, 24 Apr 2013 12:10:12 +0200 [task] allow negative intervals for add_looping_task (closes #2818280)
Julien Cristau <julien.cristau@logilab.fr> [Wed, 24 Apr 2013 12:10:12 +0200] rev 8912
[task] allow negative intervals for add_looping_task (closes #2818280) Instead of rejecting values < 0 with a ValueError, we ignore tasks with a negative interval. This introduce a simple way to disable task from configuration.
Wed, 24 Apr 2013 11:58:49 +0200 [task] allow interval=0 for looping tasks
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 24 Apr 2013 11:58:49 +0200] rev 8911
[task] allow interval=0 for looping tasks There is valid usecase for perpetual running task.
Wed, 24 Apr 2013 14:45:13 +0200 [portable dump] skip virtual relations, they have no table associated. Closes #2841199 stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Apr 2013 14:45:13 +0200] rev 8910
[portable dump] skip virtual relations, they have no table associated. Closes #2841199
Wed, 24 Apr 2013 14:37:48 +0200 [test] fix skipIf import, currently failing if unittest2 is not there stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Apr 2013 14:37:48 +0200] rev 8909
[test] fix skipIf import, currently failing if unittest2 is not there
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 tip