avoid to see the same warning twice, one for 3.6 another for 3.3

backport stable

fix session's commit handling: when an operation failed in [pre]commit, call rollback_event as well for already processed operation, not only the revert<event> callback

race condition may makes this assertion fail, we don't want that

unvisible field may have been modified, for instance relation added by an hidden input

AdaptedList -> SameETypeList *NO BW COMPAT*, benefit from cw 3.6 releasing of folder,file and blog which use it to get update at the same time. CMHN and PEGASE will need update (but won't go to 3.6 without update, so seem fine).

now raise UnknownProperty, not KeyError

fix test broken by introduction of ViewSameEType action

kill register_appobject_class method, simplifying autoregistration. Update test accordingly (test which manually registers object should also properly call there __register__ method). Drop the disable-appobjects config file entry: no one used it since its introduction years ago.

backport stable branch and some vreg cleanups: * move initialization_completed from cwvreg to base VRegistry class allowing simplification of CWVregistry * cleanup initialization process: __registered__ is now called after initialization completed, by the relevant registry. * fix/remove deprecated tests

fix security issue #36564 (integrity error w/ RQLUniqueConstraint) by using a global lock serializing commit when some RQLUniqueConstraint is encountered.

errors on postcommit should never occurs, log it as critical

missing test data

reminder, cleanup

initialize property once initialization has been fully completed, close #666573

fix duplicated vregistry initialization during tests

cleanup, don't fail if no context set on the sourcecode directive

we should not use inheritance there but proper view redirection, so if one adapt listitem view, he gets the same thing by default with the adapted list

hidden usage of datetime function which has been moved to lgc

i18nupdate

replace DevCubeConfiguration/DevDepsConfiguration by a single DevConfiguration, fixing recently introduced by w/ i18ncube command on the way

moved to lgc.date as well

oops, forgot that part of 3.2 bw compat

hercule (aka c-c client command) have not (ever?) been used for years, stop supporting it

kill most pre 3.2 bw compat code

kill mx compat code (dropped since 3.2), more efficient merge_args implementation

this test is now useless here

3.6 test api update

db fill api has changed, update test accordingly

no needs for a views package, 3.6 api update

need post_build_callbacks attribute with earlier yams version

update yams/rql dependencies

fix long-waiting symetric typo: should be spelled symmetric. Add auto database migration on schema deserialization

moved generic datetime manipulation function to lgc

fix wrong autoclass inclusion

fix rest syntax error

more selectors doc in the book, mostly extracted from code

reorganize, cleanup and properly document base selectors. Kill the may_add_relation selector.

3.6 api update

clear rest_path __unique cache in clear_all_caches, fix related test

backport stable

copy back __doc__ for proper sphinx doc generation

mimick actual request set_header method

fix typo

[views/treeview] fix non-ITree nodes last element computation

[request] add a note about the encoding mgmt (or lack thereof)

[views/plot] replace bogus jsoncall computation by something (statistically) more reliable (json_request being set to True in the JSoncontroller

[doc] small fixes on security part

misc typos found on my way: NameError / SyntaxError / double __select__, <sigh ...>

fix bad rest

fix bad rest

more details on selectors debugging

add_state/add_transition are now deprecated, only add_workflow remaining

damn me, more stupid sed fix...

add note telling you don't et an UStreamIO for binary views

document the ~ operator

start documenting forms

fix stupid sed

moved content to the dbapi section

nicer docstring

live-server doesn't work, don't make think it does

more stuff in doc's README

update exemples using the 3.6 api and add/fix some sections (schema, vreg, talk about CW_MODE in concepts...). So much to do :'(

backport stable

discriminate against None, not False-ish values

Improve the schema command with filtering option. meta data and workflow data are hidden by default. show-meta and show-workflow option are added to display them. Another "hide-type" option allow to hide additional entities type.

Added tag cubicweb-debian-version-3.5.12-1 for changeset 4281e1e2d76b

Added tag cubicweb-version-3.5.12 for changeset 98af3d02b83e

Updated CW tutorial. * Summarized the list of steps to create a new cube. * Added a subsection on writing entities. * Added a subsection on modifying the schema and updating the corresponding instance.

le patch added_tips a été importé

le patch admin_tips_for_backup a été importé

Add a ``schema`` command to cmd ctrl to generate schema image. This changeset add the new commande and do some refactoring in cwconfig and schema.py to allow the use of CubicWebNoAppConfiguration with CubicWebSchemaLoader.

fix rset.related_entity with variables coming from subquery while some others not

3.5.12

cleanup

fix spurious http cache bug: sometimes last-modified headers is generated using non-english local, which ends up in a date that twisted can't parse and make it feels the page may be cached while it may not

simpler last_modified implementation

merge

fetch all forms, avoid potential initialization pb

missing jsonize, avoid spurious error w/ ff

refactor to use the 3.6 API

merge

merge

partial backport of support for adbh's new interface to backup_command and restore_command these methods can return lists or strings which are passed to subprocess.call without or with the shell=True parameter respectively.

more escapes for the backslashes

escape the backslashes

bugfix

add action to list entities of the CWEType currently displayed

should take arbitrary arguments

i18nupdate

calling unicode instead of gettext...

[entity] small optimization: once an entity has been completed, don't redo it (for nothing)

[treeview] ensure items are ordered according to their dc_title, we can't rely on an ordered rset * is_last has to be computed on the caller now, not possible in the callee * rely on b3f61c38526b to use entity.view() with vid in *view*'s arguments

[entity] rename vid argument of .view(...) into __vid to avoid potential conflicts with kwargs

eschema view is gone away

remove misnamed argument

add version number to deprecation warning

[entities] fix CWUser.is_in_group implementation use self.groups property instead of self._groups which might not be initialized.

missing import

must check for relation inlined in main form type

skip final relations at this point

add missing errno import in etwist/server.py

should not raise KeyError if key's missing

choices function should now take the field as argument

cleanup

missing import

systematically call bool on BooleanField values

by default this is not the widget responsability to turn empty string into None, move this behaviour to the field.

ensure we get a correct key

test fixes

useless, same as test_nonregr_eetype_etype_editing

[forms] propagate aguments given to .vocabulary to .choices if it's a callable. So we can properly uses vocabulary(limit=xxx) in places where we used to call .choices(limit), since field.choices is not meant to be accessed directly. Also, document expected behaviour for custom choices method for relation fields.

reorganize code: move everything related to inlined forms and generic relation from editviews/editforms where there are used, eg in autoforms

[forms] fix backward compat for field.choices arguments

use field.vocabulary instead of field.choices, skip already related eids. Also consider vocabulary when no etype specified

[primary view] activate toolbox

it seems that prefixiter is expected to return child *folder* but was relying on a specific .children implementation, fix this

3.6 api update, cleanup

[forms] let the autoform specify the generic relation field label, no need for a custom fieldset, may be handled as for other fields by the renderer.

simplify messages used for inlined forms

should have been in previous commit (moved below in the module)

[forms] the last touch: handle inlined relation forms as fields by introducing a simple InlinedRelationField. This makese things more flexible while removing a lost of overriding necessary.

fix label handling: when label is explicitly set to None, don't try to guess it

surrounding div necessary for proper error localization

cleanup base class

by default use new jquery widgets for Time/Date/DateTime fields

new jquery based widgets for Time/Date/DateTime, backported from crm

introduce a default render implementation on the base widget, which add_media and then call the newly introduced method _render(form, field, formrenderer), abstract of the base widget class. This allow a litle code factorisation and avoid to forget the call to add_media in subclasses.

[forms] new optional suffix attribute on widget objects, used to generage input name / dom id. Ease reuse of widgets from another widget. Also move base values computing to a separated values(form, field) method.

introduce new _ensure_correctly_typed method on fields, responsible to ensure the value return by the widget is suitable for that kind of field. Also factorize date and time fields.

fix typed_value implementation w/ eidparam field which are actual entity's relation and have .value set for their initial value

cleanup module namespace but only importing the formwidgets module

fix deprecation warnings

fif inlined relation forms pb w/ new ajax forms. We've to ensure the varmaker is properly initialized when generating a form where we may add new subentities, which will use ajax call to generate the subform while this subform expect a varmaker to be set.

now that we are property initializing autoform_section for the 'inlined' form type, use it...

[uicfg] fix autoform_section rtags initialization 1. when a relation is marked as inlined in the 'main' form type, we want its opposite (eg when one the other side of the relation) to be marked as hidden in the 'inlined' form type 2. when no section is specified for the 'inlined' form type, use the same as in the 'main' form type to do this properly, we need two initialization stages. The first one to handle 1., the second to handle what was done before and 2. We can't do this in a single stage because we've to know the bare value of the "opposite" tag.

cache result of the COUNT query used to see if a non unique attribute may be used as rest path on the entity instance to avoid recomputing it later

incontext view of EmailAddress is a mailto: link

add CWProperty for_user CWUser when on the user primary view

move CWProperty rtags from autoform to cwproperties module.

fix Bytes submission pb on POST, due to multiple call to field.process_form_value for a same field. In the case of file, stream.read() doesn't return file's data the second time (since the cursor is at the end of the file). Fix this by having a generic process_form_value method that cache field's value in form.formvalues[field] and so _process_form_value is only called once. You should then override that later method on custom fields.

must skip internal field value from the generic relations combobox

case where 'w' argument is None should be handled in do_paginate

[uicfg] clean dead code, fix indexview_etype_section for ExternalUri and Bookmark

[uicfg] fix reloading pb with the indexview_etype_section

must catch UnmodifiedField exception in has_been_modified

command may now officially be either a string or a list, don't make think it's for backward compat

nicer usage for cubicweb-ctl

get back iterparents implementation from folder cubes

eschema view has been removed

[bfss] make it works when adding/updating entities with an attribute using bfss

d-t-w

fix copyright

XXX quick fix html validation by removing <canvas>

skil internal field value, else we get an error

add source in backup/restore failure message

introduced dependency to lgc > 0.47 for new stacklevel argument to deprecated + new db backup/restore api

handle lgc.adbh api changes within regards of backup/restore: * new backup_commands method instead of backup_command * some backend still return command as string as expected by os.system, not subprocess.call

match_rtype hook selector now accepts frometypes/toetypes optional arguments to match only given subject/object entity types

a selector MUST NO return None

some fixes so that deprecation warning are properly localized

to ease overriding of field.choices using *function* (set using autoform_field_kwargs), give the field as named argument

refactor attributes'value generator to deal with yams special Attribute/NOW/TODAY values that may be used on [Interval]BoundConstraint (BoundConstraint wasn't handled btw, fix this). Besides passing 'entity' to generate_* function (needed to get value for another attribute when computing one for instance): * set nicer method names and makes clearer what's private/protected/public * properly handle choices, constraints on float/date/datetime fields

backport stable

backport stable

3.6 api update

[vreg] object_by_id should not have been deprecated. Fix facets. it was *designed* to be able to force an object retreival when selection is potentially not possible. For instance using select instead of object_by_id in get_facet totally breaks the implementation since in get_facet we've not context result set, and we ends up with a NoSelectableObject exception.

fix stupid typo ...

fix condition to paginate a result set

make rollback available in shell (as commit is)

add a reminder

fix indentation / tab pbs

fix name error

add approximated version number to deprecation warning

oops, missing return

we need extrapath when trying to import site_cubicweb files

move extra path computing as a configuration class property so we can reused it

first draft for a simple hooks based custom attribute storage, with a BytesFileSystemStorage POC implementation. Basically: * a dictionary contains maps from which attribute of which entity types are mapped to which custom storage * hooks check for one of these entity type being added/modified/deleted * read is based on the sql generator callback mecanism (used in vcsfile for instance) * all storages have the same basic interface (read, add, update, delete), and should be pluggable in a transparent way (except at migration time when one want to change from a storage to another) * the sample BytesFileSystemStorage: * may store Bytes attributes content of any entity type as file on the file system * is based on one FSPATH rql/sql function and another _fsopen only available in sql * has a dumb file name allocation algorithm

d-t-w

closes #345410: two_lines_rset, two_cols_rset, two_etypes_rset are badly named replaced by multi_lines_rset, multi_columns_rset, multi_etypes_rset, all taking optional 'nb' argument allowing to specify and exact count. Bw compat is kept, usage of deprecated function updated in cw itself. Also drop custom at_least_two_columns selector (in views.plots) since it was the same as multi_columns_rset. Hopefuly the renaming will help in avoid such pb... We should now decide if we want to deprecate one_* selector in favor of multi_*(nb=1). See note on this at then end of selectors.py

fix #636936: read_permission relation should not be mandatory

fix #615848: undefined 'new' variable was refering to the newly introduced subquery / remove_subquery doesn't take an undefine argument (probable copy/paste from the remove_node call)

some docstring

[doc] reformulate dependencies

[views] FinalView should display an empty string if value is None

merge

move base form renderer label handling into a function to reuse it in CompositeFormRenderer and avoid seeing a tuple in column headers...

minor schema deserialization optimizations

oopb, widget has been renamed

specify formvid=edition to get multiple edition working w/ 3.6

reminder

this clutter startup screen for little benefit, remove it