GitLab

--HG--
branch : stable

[dbapi] load_appobjects must attempt to load available cubicweb configurations to avoid error when some object use a persistent propery (CWProperty) defined there. Closes #2497697

--HG--
branch : stable

[misc/scripts] a slightly experimental script to help repair LDAPUser cwusers suffering from split-brainite (closes #2497108)

--HG--
branch : stable

--HG--
branch : stable

--HG--
branch : stable

--HG--
branch : stable

The recent split of patches for session refactoring broke this.

--HG--
branch : stable

--HG--
branch : stable

--HG--
branch : stable

[session] fix arguments default value and promote usage of security_enabled as session method. Closes #2481820

One should use session method rather than direct usage of the context manager
of the same name.

Fix default argument values for consistency with the context manager: when one
omit an argument, meaning is "keep the current value", not "disable security".

[session] promote usage of [deny|all]_all_hooks_but session methods rather than hooks_control context manager directly

[db creation test] more testing of db initialization: call build_db_cache and ensure admin user exists

They are broken if launched during repository initialization (this was not the
case yet, but will be soon...). Add additional checks to ensure one doesn't try
to store system source config in the database, as it will be ignored in favor of
the "sources" file.

Users should now use cubicweb.validation_error helper function that will activate the feature
with other handy behaviours. Also test testing for message in errors should call
exception.tr(unicode) before comparing.

Using bare ValidationError keep backward compat.

passlib can raise ValueError when it can't recognized a hash.  Treat
that as a wrong password.

--HG--
branch : stable

this simplify code and make it more consistent

this avoid error due to implementation details of session

This decouple thing and make code easier to understand. Previous behaviour was fine
w/ validation error that were translated on the server side, but isn't satisfying for
notification and all. Now:

* translations should be done on the ui side (see previous validation error
  refactoring)

* consistent behaviour: each side (web/repo) is responsible to deal with its
  request/session of language, no weird interaction between them on this topic

* drop on the way the 'session properties' api, used only for that matter.

-> much simpler/cleaner/saner api

The thing missing being a way for user to tell "My favorite language is xxx but I also
want cw to consider my http language header)

[config] turn internal configuration methods building appobjects search path into normal method rather than class method

as this is useless and make path filters difficult to override (we had to
override the class attribute, as instance attributes were not seen).

Also rename related methods for consistency with current vocabulary

--HG--
branch : stable

--HG--
branch : stable

--HG--
branch : stable

Closes #2465904

--HG--
branch : stable

[repo pyro] fix previous commit: should not import Pyro in remoterql module/base class, it may be missing

--HG--
branch : stable