In the merge partner wizard, there's a button in the footer which
trigger the method `action_close`. This method is decorated by
an api.multi and begins with an ensure_one() and if you click
on close directly after opening the wizard, self.ensure_one
fails.

The thing is, `action_close` only return an ir.action.act_window_close
action and there's a special attribue you can set in the form
view button to make it return an ir.action.act_window_close directly.
If we use this technique, then there's no traceback anymore. So this
is the fix.

Since 85bcd6fd, the field `paypal_account`
has been removed. The field `paypal_url` cannot be computed correctly
anymore.

This reverts commit 2ab68047.

As you open the lots in a raw material move in a production order,
you should not see the temporary stock move lots from the work order.
Also the quantity_done should not take into account those.  They will
when they press 'Done' on the workorder.

When posting inventory, the temporary stock move lots on the workorder,
should be transferred to the split move.

For splitting and unreserving, some optimizations are done.

background and color snippet options

The background and color snippet options communicate so that if a
color is set while a background is already set, the backgrond is
removed. The problem is that the event propagation was not stop
so if a snippet had a background and one of its child set a color,
the background was removed.

2 rules were defined with the same id thus only one was loaded in
database, resulting in missing read access on model
'project.task.history.cumulative'.

This patch fixes the ids of these rules and clarify their names

When we were trying to delete a stage in project where there were
some tasks, an error was raised because of the 'project.task.history.cumulative'
records that inherit 'project.task.history' which have a compute method on
on end_date.
To fix this, we set the 'compute' attribute to 'None' and the readonly
'attribute' to 'True'.

Use HTML version instead

[IMP] mrp: use decoration-danger for not available raw materials even if it gives the same color as when you consume more than foreseen

When the routing of the phantom bom is the same as the parent BoM,
the phantom BoM should not recreate the work orders, but use the same
work orders as the parent BoM.  That way, you can create one master
routing and the "consumed in operation" of the phantom bom can be used
linking to the master routing.

If the phantom bom has no routing or the same, it can also use
the "consumed in operation" of his parent bom line if none is defined.

[FIX] website_project: override get_access_action to redirect to my/tasks,projects

[FIX] project_issue: Don't send notif template to portal customers if no website

[FIX] website_project: Portal users can receive notif template

[FIX] sale: Don't display 'View quotation' button on email if no website
If the website module is not installed, the button 'View Quotation' will lead to the backend chatter page, which is not very useful in our case.
As the quotation is already attached in the mail as a pdf, just don't display the button if the website module is not installed

[FIX] account,sale: Don't send notif template to portal customers if no website

[FIX] account: Don't display 'View Invoice' button on email if no website
If the website module is not installed, the button 'View Invoice' will lead to the backend chatter page, which is not very useful in our case.
As the invoice is already attached in the mail as a pdf, just don't display the button if the website module is not installed

[FIX] website_sale: override get_access_action to redirect to my/invoices

Currently as no portal backend view exists anymore, the method 'get_access_action' will return a url to the backend.

For example, if you have only sale installed (with portal_sale in auto install mode), you'll get access rights to sales orders in read mode in backend. The correct way to handle this is to return an access error and give the access rights to these documents only in website_portal_sale is installed, i.e. when the portal view is accessible in frontend under my/orders/ controller.

portal_sale: Remove invalid 'get_formview_action' overwrite

This commit https://github.com/odoo/odoo/commit/ecd58457ed2311cfec8cae9d01b04ce995b31ec7 has removed some backend portal actions, but didn't remove them from the template links.

In some snippets, the parent hierarchy has many elements. So, when
selecting a deep child of one of those, the customize dropdown had
many dropdown headers showing the parent hierarchy but without any
option for many of them.

Commit de0d9fd6 already fixed the case
where the dropdown only contains dropdown headers. This commit is an
adaptation to hide these headers one by one.

The feature was lost because of a programmation error (use of this in
a non-binded function).

When use t-set the value is replaced by an empty list and can't be use inside the t-set.

Issue: <t t-set="bibi"><t t-raw="bibi"/> other</t> => ["\n "] other

* Archive isn't working properly because doesn't show elements of
  last day of the month in the wrong month
  Change the domain to take the good days.

It was impossible to pass from  an archive to another because of
the keep_query in the url generated that set multiple times the
same argument in the url. Removing this allow to have a 'date_begin'
and a 'date_end' corresponding to the selected archive.

using the --uses-first parameter on msgmerge this time

Forward-port of dc975f3b which have
been forgotten during previous commit

If a budget line has no analytic account id, the code is intentional
about returning a value of 0 for it.  It is possible, that in some
cases, depending on the order of lines processed, the routine returns
the previous value, as it does not initialise an important
variable on each iteration of the loop.

Closes #13303

This reverts commit c34972a2.

Please check what you are doing or stop committing in official branches.

Add label for usability, didn't understand what was the date field e.g.

Fix bug when no priority, 'priority' field was not submitted -> save function crash
Fix bug textarea, if title_action is False, not textarea, so no field
title_action submitted -> save function crash

After this commit, we can click on save and it should work...

No priority or 0 => 0
No title or "" => ""

/mail/view?model=blog.post&res_id=1

crash in 'res_id': self.id

AttributeError: 'blog.post' object has no attribute '_ids'

Feedback: 10 is very few

Account uses this field from purchase module, but account don't depend of
 purchase.

Already done for sale_ok previously.

See #13268 #315 #13271