Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Apr 2013 14:51:06 +0200] rev 8942
[test] stop deepcopying for nothing
Aurelien Campeas <aurelien.campeas@logilab.fr> [Fri, 26 Apr 2013 12:10:37 +0200] rev 8941
drop xhtml content-type support (closes #2065651)
* HTMLStream does not care about xml any more
* reqquest.demote_to_html and .xhtml_browser are deprecated
* web config: drop force-html-content-type option
* adjust tests
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 26 Apr 2013 11:53:47 +0200] rev 8940
[htmlparser] exclude <script> tag from html source
lxml are confused by them :-(
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 26 Apr 2013 11:52:35 +0200] rev 8939
[htmlparser] store unaltered source in pageinfo.source
Do not store the parser to preserve the source aspect. Store the initial input
in the source argument instead.
This is very useful when parsing html. In such case we need to drop ``<script>``
tag.
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Apr 2013 18:38:47 +0200] rev 8938
[htmlparser] rename SaxOnlyValidator to XMLValidator
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Apr 2013 17:46:28 +0200] rev 8937
[htmlparser] add missing deprecation message
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 25 Apr 2013 16:55:12 +0200] rev 8936
[form] remove hard coded id
html id should be unique. It is clearly not achieved here.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 26 Apr 2013 11:08:06 +0200] rev 8935
[server/test] use server config in migration
This allows a lighter initialisation (no rtag needed).
Execution of those test move from 300 secondes to 220 seconds here. A 25%
speedup
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 22 Apr 2013 17:57:46 +0200] rev 8934
[session] deprecate `hijack_user` method
The semantic of this method is wicked and lead to very hard violation of sanity.
(multiple transaction using the very same cursors). We deprecated the API to be
able to drop it as soon as possible.
The method was added long ago for some notification trick. It is not needed
since we sent notification on ``postcommit_event``.
(closes #2781782)
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 25 Apr 2013 12:24:26 +0200] rev 8933
[mail] drop hijack_user usage
The transaction is now commited before notification. We can create a new session
directly and drop `hijack_user` usage.
This prepare #2781782
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 25 Apr 2013 13:35:02 +0200] rev 8932
[notification] merge BaseNotificationView and NotificationView
They are in the same module now.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 25 Apr 2013 13:34:48 +0200] rev 8931
[notification] move notification view in ``sobject.notification``
It has no user outside this module. This enforce serversideness of
notification and allow future cleanup.
No backward compat is set up to prevent circular import. The class has no other user
anyway.
(closes 2845144)
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 25 Apr 2013 14:10:55 +0200] rev 8930
remove unused import
pyflakes say they are unused. Tests suite confirms.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 25 Apr 2013 17:30:09 +0200] rev 8929
one more merge
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Apr 2013 16:10:56 +0200] rev 8928
[notification] introduce an official `notify_on_commit` function
It provides a proper notification api instead of replacing it by yet another
clumsy one.
Closes #2837251
Vladimir Popescu <vladimir.popescu@logilab.fr> [Thu, 25 Apr 2013 10:57:01 +0200] rev 8927
[cubicweb/doc] Replace dc_type() by cw_etype
dc_type() is may be translated. Leading to terrible terrible damage.
Vladimir Popescu <vladimir.popescu@logilab.fr> [Thu, 04 Apr 2013 11:58:41 +0200] rev 8926
[dataimport] backout 6947201033be (related to #2788402)
(and add a try: except to cache the intended error)
The problem actually comes from the ``MassiveObjectStore``
in the ``dataio`` cube, so it should be corrected there.
Here, we only protect it with a ``RuntimeWarning`` so that
the user can see the problem.
``value`` is set to ``None`` (whence to ``NULL`` from
a database standpoint), so that the data can be nevertheless
inserted in the database. However, only the keys present in
``row`` are actually non-'``NULL``'.
The real solution is to work out the issue in ``MassiveObjectStore``
directly.
The current try/except should only be a temporary hack.
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Apr 2013 15:45:38 +0200] rev 8925
merge default heads
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 05 Apr 2013 14:44:03 +0200] rev 8924
[c-c serverctl] import locally to speed up c-c
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Apr 2013 12:12:15 +0200] rev 8923
[facet js] minor refactoring and cleanups
* extract facetCheckBoxSelect and facetCheckBoxUnselect
* use $ as prefix for jQuery variable (facet -> $facet)
* other minor rephrasing
David Douard <david.douard@logilab.fr> [Wed, 24 Apr 2013 18:11:37 +0200] rev 8922
[ldapfeed] Add support for LDAP groups (closes #2528116)
Groups from the LDAP server are imported as CWGourp entities, and in_group relationships are created between existing CWUsers and CWGroups
Unit tests have been refactored a bit, especially ti add helper methods to manage LDAP database.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 24 Apr 2013 17:57:14 +0200] rev 8921
[test/ldap] small improvement to ldapfeed unit tests
better group testing and further testing of imported user life cycle.
David Douard <david.douard@logilab.fr> [Wed, 24 Apr 2013 17:48:08 +0200] rev 8920
[ldap] prepare import of CWGroup
All CWUser specific code is put in dedicated sections.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 24 Apr 2013 17:40:49 +0200] rev 8919
[ldap] handle modification date
We are now able to import modification date from ldap.