[edit controller] fix handling of removal of subentities from an edit form In CubicWeb 3.18 the semantics of dropping a composite relation were changed. It had before the effect of deleting the subentities. Now the edit controller must handle this by itself (it was not adapted then by mistake). So if it detects the removal of a composite relation (on the browser side, the user clicked on the "remove" action), the subentity is now explicitly deleted. It was chosen not to change the form generation but the EditController: - to ensure pre-3.18 forms backward compat - to avoid the introduction of a specific entity-deletion API (RQL is probably our best API for complex DB operations) Related to #8529868.

.TH cubicweb\-ctl 1 "2010-01-14" cubicweb\-ctl
.SH NAME
.B cubicweb\-ctl
\- cubicweb control utility


.SH SYNOPSIS
.B  cubicweb-ctl <command>
[
.I OPTIONS
] [
.I <command arguments>
]

.SH DESCRIPTION
.PP
CubicWeb utility to create and control instances, and more generally do all
cubicweb's related tasks you can have to do using the command line. Available
commands will depends on which part of the framework are installed.
.PP
Type
.B "cubicweb\-ctl <command> \fB\-\-help\fR"
for more information about a specific command.

.SH COPYRIGHT 
Copyright (c) 2003-2010 LOGILAB S.A. (Paris, FRANCE).
http://www.logilab.fr/ -- mailto:contact@logilab.fr