Before this patch, the order of a project's task type (its columns)
were defined by a sequence. However, when you quick-create columns,
they have the same sequence value: 1 by default. This results in
weird behavior when you edit a task type (for example, by changing its
tooltips), the column is moved at the end.
By ordering by sequence and id, the behavior is more intuitive
as the colum doesn't move when you edit it.
As we will soon improve the sanitizer we will be able to sanitize email
templates body. However this implies some cleaning in the templates to
be sure mako is not considered as invalid html / xml and therefore removed
from the template body.
* crm, project, website, website_event, website_blog, website_forum,
website_sale
Eg: the tour 'shop_buy_product' is extended by the website_sale_options
addons to add a step to close a modal.
The current solution was requiring the module that defines the tour
to extend, then add/remove steps in the "step" key of the tour
definition.
Some of the problems with this method were:
* The "register" method calls the "update" method to immediately
search for tip to place once registered (as register may be called
after the DOM is ready). So extensions of tours were happening after
the tours were started (and the tours were not restarted).
* The addition/removal of steps was happening after they were filtered
according to the "edition" key.
To allow extension, the system is changed as follow:
* The "register" method now only saves the steps and options without
modifying them and does not call the "update" method.
* Once the DOM was ready, the tour service started listening to DOM
mutations and called the "update" tour method. Now, this "update" call
is replaced by a "_register_all" call, on DOM ready and at the end of
the current call stack (which makes sure all modules are loaded). This
"_register_all" method marks the registered tours as ready after having
filtered the steps according to the "edition" key and initialized the
current step to trigger.
* Also, tours can now define a "wait_for" option which allow them to
be marked as ready for run and update after the given deferred. Those
tours can now also be extended without having to wait for the deferred.
PhamtomJS must wait for the "ready" key to be true to run the tour.
Add a link in the general settings to access easily the default_user form view in order to modify the default access rights
The default_user manager rights declarations in all the applications have been move in a noupdate="1" definition to avoid the manual configuration overwrittings
This reverts commit 45a13cac80.
The commit failed the tour test since there is invisible
".o_kanban_ghost" cards after the last. Since the created new
project is already sorted in the right location, we don't know
if it will be the first or the last.
But if it is the first, we know we will see the help tip.
People tend to click on the gear on the stage column and click
the "Edit" button. There, they think they are creating a task.
- Rename the 'Edit' button into 'Edit Stage'.
- Hide mail_template_id and project_ids fields in technical features.
Commit 9b69184ff. removed field 'state' of model 'project.project', and
converts domains using it to use field 'active' instead. However, the domain
of the many2one field in the task form view hasn't been correctly converted
(['state', 'not in' , ['closed', 'cancelled']] should be ['active', '=', True]).
The module `sale_service` has been merged in the module
`sale_timesheet` in the revision
234f88a6af
We only remove the field from the view due
to the fact saas-11 is a stable. The field
has already been removed from the model
in newest releases (`saas-12`)
opw-682816
The field state was replaced by ‘active’ in project.project (see commit 9b69184).
However, someone forgot to update the arch for the default list view which
was not longer possible to open.
The onchange should have the signature with `ids` instead of `id` for a proper
guess.
Without this, the method can not be overriden with an api.multi (the return
result is a list of dictionnary which is not understood by the ORM as a proper
return format).
Fixes#12856
Simon Lejeune