[repo] fix warning message and implementation of bw compat unsafe_execute

stable is now 3.7

oldstable is now 3.6

backport stable

merge

Added tag cubicweb-debian-version-3.6.3-1 for changeset f9fce56d6a0c

Added tag cubicweb-version-3.6.3 for changeset 9c342fa4f1b7

Added tag cubicweb-debian-version-3.7.1-1 for changeset 9194740f070e

Added tag cubicweb-version-3.7.1 for changeset 6b0832bbd1da

backport debian control changes done in 3.7

3.6.3

ticket #636927, add ajaxhtmlhead in controller js_component

[widget] allow kwargs passed to Select widget

take care to empty breadcrumbs

fix bug with damned transmutation functionality, occuring when using an INSERT query which also add relation to the entity

update skeleton for __pkginfo__.py

don't use optional on final relation

fix security issue introduced by 4967:04543ed0bbdc: attributes explicitly set by hooks should not be checked by security hooks

[form js] apply vgodard patch fixing #750056: reorderTabindex js function crashes when form dom id is not 'entityForm'

missing unittest_main

[server] add unit tests for storages

[registry] trigger reload events on set_schema()

[source] only consider edited_attributes in source.preprocess_entity()

[source] implement storages right in the source rather than in hooks The problem is that Storage objects will most probably change entity's dictionary so that values are correctly set before the source's corresponding method (e.g. entity_added()) is called. For instance, the BFSFileStorage will change the original binary data and replace it with the destination file path in order to store the file path in the database. This change must be local to the source in order not to impact other hooks or attribute access during the transaction, the whole idea being that the same application code should work exactly the same whether or not a BFSStorage is used or not.

i18n update

3.7.1

backport stable

[etwist] cleanup, use cProfile instead of hotshot

[repo] start looping task on repo only config (though I bet more work is needed to get it actually working

[repo] call server_startup event in start_looping_task the repo is fully started (registered in pyro for instance)

[security] take care uidrels may contains a relation targetting something else than a constant node (eg IN function)

[ms] this test is already done before putting a relation in uidrels

cleanup

[security] experimental rqlst cache for read security: to activate using a 'security-rqlst-cache' flag in transaction data when you'll issue a lot of identic queries with only kwargs varying

[read security] minor optimizations

[web] get rid of spurious '[Errno 2] No such file or directory' on load This was caused by can_do_pdf_conversion() which tries to use '/usr/bin/fop'. When fop was not available, an OSError was raised by suprocess.Popen. This changeset first checks for /usr/bin/fop presence, then tries to run fop. If an error occurs, log it instead of printing it. NOTE for later: why do we test explicitly for "/usr/bin/fop" rather than simply "fop" ?

backport stable

[schema sync] fix another potential name error on synchronizing rdefs

[schema sync] don't try to synchronize infered relation defs, fixing a name error on the way

cleanup

don't update constraints when it's not necessary

[repo] don't call server_shutdown hooks when creating/repairing instance to be consistence with server_startup hooks

[migration] new build_descr argument to rqlexec on the migration helper

fix migration when upgrading from cw < 3.6 to cw 3.7

disable security when undoing

merge

[sql] fix FSPATH implementation plpy.execute() returns a list of dictionaries with column names as keys and corresponding values as values.

[web deletion] must use set_message

fix limited_rql w/ UNION query

backport stable

fix import

Fixed some of the documentation warnings when building the book with sphinx.

move pdf icon component with it's template so we don't see it when the template isn't available due to missing dependancies

backport stable

add missing warn imports

add missing warn imports

improve documentation for uicfg and rtags

backport stable

merge

[cleanup] objtype not used

[schema sync] test and fix bug when updating multiple constraint for the same rdef in the same transaction

3.6 want __regid__, not id

[migration] disable notification by default during migration

[session] fix hijack_user: most transaction_data should be copied (everything but the entity cache

Added tag cubicweb-debian-version-3.7.0-1 for changeset 0c9ff7e496ce

Added tag cubicweb-version-3.7.0 for changeset 270aba1e6fa2

fix control file by using virtual packages

fix common/rql dependencies

3.7.0

test fixes

merge

fix tests

fix test broken by recent rql rewrite / querier changes

backport stable into default

server/web api for accessing to deleted_entites

[R] dataimport: changes - deprecate checkpoint() in favour of commit() - filter on None value in mk_entity - rearrange log messages order

#750055: make it easier to change post logout url

[web auth] fix authentication pb when anonymous are allowed, avoiding the first authentifier to return an anon connection while a following one may find correct authentication info. This make things simpler (eventually)

[web server] simplify base-url handling on startup. Ensure config['base-url'] is correctly set once started

[rql rewrite] until a better solution is found raise BadSchemaDefinition when two inlined relations with security on an optional variable is used, explaining how to bypass it

[rql rewriting] handle case where we've and optional inlined relation in the original query. Also, we should append EXISTS even in subquery to avoid inserting duplicates in results

[rql rewriting] handle case where we want to insert snippet on a variable that has previously been moved to a subquery

backport stable

[backup] fix misplaced paren

fix bad conflict resolution

backport stable

LazySuggestField : remote version of RestrictedSuggestField

typo

backport stable

Add a rssitem_id attribut to RSSView to easly choose the view used for items.

[web] start a new message system based on id of message stored in session's data instead of using __message as today, which is problematic (allow message injection). Also we can have html in messages. Removed the __createdpath hack used to escape those limitation. The old system should still work though (and will probably for a while, though we should progressivly move to the new system where it's possible). Cleanup request paramaters handling on the way.

[notification] fix dumb name error in hijack user

[dbapi] return default argument instead of None when no connection set yet

[cleanup selectors] use authenticated_user, check for form params instead of handling potential key error on missing params

[db backup] fix name error in backup_to_file: we've to pass .confirm all along the chain as for restore

[cleanup] use iteritems

[url] new rebuild_url method on base request

typo

fix apycot detection

provide logilab.database compat when creating database

update debian changelog

[db creation] fix some bugs introduced by the migration to logilab.database

[debian] packaging fixes * remove postgresql-contrib from cubicweb dependency (using tsearch which is included with postgres >= 8.3) * add postgresql-client | mysql-client to cubicweb-server dependencies, necessary for dump/restore of database

[web] yes this is used

[web] cleanup: move delete_entities to the edit controller

[web] stop using deprecated merge_dicts

[utils] improve dump_class by copying back original class doc and module name

[utils] make_uid imrovment: using .hex already remove '-', make key argument optional, document it

deprecates merge_dicts

kill unused method

merge

Added tag cubicweb-debian-version-3.6.2-1 for changeset f3b4bb9121a0

Added tag cubicweb-version-3.6.2 for changeset bfebe3d14d53

[form] fix bug introduced by 4871:a34b76593ab2 with field using multiple input with different suffix: the suffix should be considered in the cache key

i18nupdate

prepare 3.6.2

[form fields] fix severe memory leak due to @cached on field.input_name occuring on forms with persistent fields. Has been triggered in 3.6.1 on our public sites because: * the login form use persistent field since 3.6 * it's displayed on every anonymous request * another bug (fixed during the latest mini-sprint) made it also displayed for authenticated user see explanation in code for more detail. moral: be very careful with @cached...

[debug] allow to specify maxlevel to gc_info

[write security] we must check perm with read security disabled + add missing eid argument to check_perm

merge