Florent Cayré <florent.cayre@logilab.fr> [Mon, 21 Jan 2013 16:34:09 +0100] rev 8666
make ui configurations selectable (closes #2406609)
* introduce a new 'uicfg' registry (storing instances)
* use the relevant new APIs from lgc.registry to manage the new
registrable uicfg objects
* cw event manager useage is gone; instead thze standard registry
reloading mechanism is used
* ensure i18n commands still work (devctl)
* introduce dynamic uicfgs use whenever possible (various views), even
though sometimes the classic 'static' usage remains
Aurelien Campeas <aurelien.campeas@logilab.fr> [Thu, 10 Jan 2013 18:34:10 +0100] rev 8665
[uicfg] uicfg.py moves from web/ to web/views/ (prepares #2406609)
We are about to make uicfg selectable. Registrable / selectable views
and helpers live in web/views. Hence the move.
Backward compat is put in place. However CubicWeb imports of uicfg are
updated to the new location.
Aurelien Campeas <aurelien.campeas@logilab.fr> [Thu, 10 Jan 2013 13:03:38 +0100] rev 8664
[appobject] introduce RegistrableObject base class (prepares #2406609)
Aurelien Campeas <aurelien.campeas@logilab.fr> [Mon, 21 Jan 2013 13:55:25 +0100] rev 8663
[cwvreg] introduce lgc version 0.59 and remove unneeded method redefinition (prepares #2406609)
The new logilab.common.registry makes this moot.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 23 Nov 2012 18:27:35 +0100] rev 8662
[BFSS] mark fs_imported value as uncachable
This will finally fix the `test_bfss_fs_importing_transparency` pass again.
Regression was introduced by 4ba11607d84a
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 18 Jan 2013 18:48:15 +0100] rev 8661
[entity] add a "repo_side" parameter to `_cw_dont_cache_attribute`
This parameter (defaulting to `False`) is used to inform cubicweb that we really
really do not want to cache a value during creation or update. This will be used
by a storage that may do very specific processing on attribute values that result
in a stored value different than the provided one (e.g. BFSS `fs_importing`
mode).
Aurelien Campeas <aurelien.campeas@logilab.fr> [Fri, 18 Jan 2013 18:31:51 +0100] rev 8660
[merge] backport stable fixes
Aurelien Campeas <aurelien.campeas@logilab.fr> [Fri, 18 Jan 2013 18:31:25 +0100] rev 8659
[entities] fix test failures introduced by fixes in workflow related message strings (completes 9bb93efa1952)
Vladimir Popescu <vladimir.popescu@logilab.fr> [Fri, 18 Jan 2013 16:40:11 +0100] rev 8658
[doc/book/] Corrected typo in en/tutorials/base/customizing-the-application.rst, for the add_cubes function call
Aurelien Campeas <aurelien.campeas@logilab.fr> [Fri, 18 Jan 2013 17:37:35 +0100] rev 8657
[entity,views/json] backout 353bbd17a8b6 (reopens #2559931)
Calling .complete() unconditionnally from the json encoder is unsafe
since on entity creation validation:
* an eid may have been drawn (hence even .has_eid() would not help)
while processing form data in the edit controller
* a ValidationError may have been raised and the entity-creating
transaction rollbacked
This leads to a crash on the return path from the validation to the
browser, where the json_dumps((status, args, entity)) call will
stumble upon the .complete() call which will fail because the entity
does not (any more) exist in the database.