### Issue - Install eCommerce with any theme - Website > Enable optional product - Create a SO with an optional product - Save > Customer Preview - Mobile view with inspector - Click on the shopping cart icon in the optional product line Quantity selector is not correctly displayed ### Cause First, the input width is 50%, which means very small on mobile and there are paddings on the input and the buttons ### Solution Remove the 50% width and paddings on

### Issue

	- Install eCommerce with any theme
	- Website > Enable optional product
	- Create a SO with an optional product
	- Save > Customer Preview
	- Mobile view with inspector
	- Click on the shopping cart icon in
	  the optional product line

	Quantity selector is not correctly
	displayed

### Cause

	First, the input width is 50%, which
	means very small on mobile and there
	are paddings on the input and the buttons

### Solution

	Remove the 50% width and paddings on mobile
	It allows to see 3 chars on very small
	mobile screen.

**OPW-2220893**

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#48092

- Install CRM, sales and Automated Action - Create the automated action * Model -> Sale Order * Trigger Condition -> On creation * Action To Do -> Add followers * Add Channels -> sales - Create a new CRM opportunity with a partner set, Save - Click on the "New quotation" - Save A Traceback "Error: A follower must be either a partner or a channel (but not both)." will popup, blocking the user from completing the action. This occur because the context flag default_partner_i

- Install CRM, sales and Automated Action
- Create the automated action
  * Model -> Sale Order
  * Trigger Condition -> On creation
  * Action To Do -> Add followers
  * Add Channels -> sales
- Create a new CRM opportunity with a partner set, Save
- Click on the "New quotation"
- Save

A Traceback "Error: A follower must be either a partner or
a channel (but not both)." will popup, blocking the user from
completing the action.

This occur because the context flag default_partner_id is used by
the model to override the empty partner_id which should remain empty

Other use case (2210285):
After adding a channel as a follower to a sales team it is not
possible to create a sale order from a contact or opportunity. You can
only create a sale order from the sales app in that case.

Adding related test

opw-2200219
opw-2210285

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#47761
Forward-Port-Of: odoo/odoo#46818

Commit https://github.com/odoo/odoo/commit/bb0cdec4594fab8c22265ed8af0c2d431a263b72#diff-e4ca107fe5c84ec39ba346fb90d1bdf6R76 added strange code affecting the whole editor when website_blog was installed. To stay consistent, commit https://github.com/odoo/odoo/commit/80f54f563a3917828c5f67dfe9c44d0f6b0c5324 moved it in standard website and marked it as to review. It is in fact the cause of a bug: *all* drop areas appeared with a big editor text "Drag and drop a building block here" because

Commit https://github.com/odoo/odoo/commit/bb0cdec4594fab8c22265ed8af0c2d431a263b72#diff-e4ca107fe5c84ec39ba346fb90d1bdf6R76
added strange code affecting the whole editor when website_blog was
installed. To stay consistent, commit https://github.com/odoo/odoo/commit/80f54f563a3917828c5f67dfe9c44d0f6b0c5324
moved it in standard website and marked it as to review.

It is in fact the cause of a bug: *all* drop areas appeared with a big
editor text "Drag and drop a building block here" because of this code.

As a fix in stable, this commit solves the code so that it works as
intended: adding an editor message on a normal .oe_structure makes it
an .oe_structure.oe_empty automatically. In master, this code will
simply be removed and it will be up to the devs to not make errors in
their xml so that the editor messages appear.

Related to task-2210733

Forward-Port-Of: odoo/odoo#48450

### Issue When you send a form which create a customer from the website, you get a 400 error. I used the customer database to reproduce the issue. I guess this is due to specific settings who set a value for `meta` here https://github.com/odoo/odoo/blob/5381e9d900b344e7d48a6b347c5fc551d433b15e/addons/website_form/controllers/main.py#L187 ### Cause The cause is the same than the one for fc8a0474b4 Here, we use sudo: https://github.com/odoo/odoo/blob/5381e9d900b344e7d48a

### Issue

	When you send a form which create a customer
	from the website, you get a 400 error.

	I used the customer database to reproduce
	the issue. I guess this is due to specific
	settings who set a value for `meta` here

https://github.com/odoo/odoo/blob/5381e9d900b344e7d48a6b347c5fc551d433b15e/addons/website_form/controllers/main.py#L187

### Cause

	The cause is the same than the one for fc8a0474b4
	Here, we use sudo:
https://github.com/odoo/odoo/blob/5381e9d900b344e7d48a6b347c5fc551d433b15e/addons/website_form/controllers/main.py#L211

	sudo adds a flag "su" and does not replace the user in env
	So we have "public user" who doesn't have email instead
	of OdooBot who has an email, there is a raise who explain
	the issue but it's not forwarded to the error in the website

### Solution

	Use with_user(SUPERUSER_ID) instead of sudo, in order to have
	the right user (as it is done few lines above.

**OPW-2220816**

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#48470

### Issue - Install Mass Mailing - Activate debug mode - Create a mass mailing - Select any template - Go in codeview The snippets hide a part of the code ### Cause The snippets container is not hidden when toggling codeview ### Solution Hide it when we toggle the codeview if it exists. This solution could solve other similar case if there are any too. **OPW-2220639** **OPW-2220639** -- I confirm I have signed the CLA and read the PR guidelines at ww

### Issue

	- Install Mass Mailing
	- Activate debug mode
	- Create a mass mailing
	- Select any template
	- Go in codeview

	The snippets hide a part of the code

### Cause

	The snippets container is not hidden
	when toggling codeview

### Solution

	Hide it when we toggle the codeview
	if it exists. This solution could
	solve other similar case if there
	are any too.

**OPW-2220639**
**OPW-2220639**

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#48073

There is a discrepancy between what country is used to compute the fees for a transaction depending on where we are in the payment flow. At rendering, the country of the order's shipping partner is used (since it is set as the main partner in the rendering values dict through `render_sale_button`). At creation, the country of the partner is used (since the `payment.transaction` record is created with the order's main `partner_id` in `_create_payment_transaction`). This is unfortuna

There is a discrepancy between what country is used to compute the
fees for a transaction depending on where we are in the payment flow.

At rendering, the country of the order's shipping partner is used (since
it is set as the main partner in the rendering values dict through
`render_sale_button`).

At creation, the country of the partner is used (since the
`payment.transaction` record is created with the order's main
`partner_id` in `_create_payment_transaction`).

This is unfortunate and can cause issues with payment flows if there is
a mismatch between countries of the shipping/invoice/main partner, as
the fees may be computed as 'international' in one case and 'domestic'
in another - this causes the values sent to Paypal to differ from those
saved on the transaction, which causes the transaction to be rejected
upon return from Paypal because of an amount mismatch.

Since the transaction is created using the main partner of the order,
I believe it is preferrable to use it for the rendering as well. Some
may dislike this choice, as it means that if you use these fees to
manage your delivery fees, a customer with a shipping address to is not
the same as the company's country will pay domestic fees, while they
should pay international ones. However, this is mitigated by the fact
that:
- this did not work before this commit (hell of an argument)
- the delivery module is there to handle those cases with much higher
configurability
- having a consistent computation is more important than managing this
case

opw-2225023

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#48499

During the recent refactoring, the order reversal of the post messages was dropped by mistake; Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45817

During the recent refactoring, the order reversal of the post messages
was dropped by mistake;

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#45817

We update the hence of the view to take into account the original invisible domain plus the domain we need for journals that use documents Before  After  -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo

We update the hence of the view to take into account the original invisible domain plus the domain we need for journals that use documents

Before
![image](https://user-images.githubusercontent.com/7593953/77002636-952d1200-693a-11ea-9926-8476c5f26ccd.png)

After
![image](https://user-images.githubusercontent.com/7593953/77002579-7fb7e800-693a-11ea-8794-a7a78252cdec.png)




--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#48113
Forward-Port-Of: odoo/odoo#47962

Bug === Can not copy a `mailing.mailing`. In ffe1d4047da181f97fafe2a69f64e6f283fbeb0e "onchange" were replaced by computed fields. But in 950296f661499f499b0a5776ce7fd91a66c2a63f, they use manually this onchange method in the copy, which is not needed with computed field (bug introduced certainly during a forward port). Task-2226235 Forward-Port-Of: odoo/odoo#48478

Bug
===
Can not copy a `mailing.mailing`.

In ffe1d4047da181f97fafe2a69f64e6f283fbeb0e "onchange" were replaced by computed fields. But in 950296f661499f499b0a5776ce7fd91a66c2a63f, they use manually this onchange method in the copy, which is not needed with computed field (bug introduced certainly during a forward port).

Task-2226235

Forward-Port-Of: odoo/odoo#48478

In a planning > schedule by project, with the gantt view, start date is automatically includes in domain. But with other view, start date is not always in domain. Now, we manage the case where the start date is not in domain. Task ID 2222973 Forward-Port-Of: odoo/enterprise#9466

In a planning > schedule by project, with the gantt view, start
date is automatically includes in domain. But with other view,
start date is not always in domain. Now, we manage the case where
the start date is not in domain.

Task ID 2222973

Forward-Port-Of: odoo/enterprise#9466

The product prediction could produce a traceback if the content of the description contained special characters such as '%'. Forward-Port-Of: odoo/enterprise#9506

The product prediction could produce a traceback if the content of the
description contained special characters such as '%'.

Forward-Port-Of: odoo/enterprise#9506

TaskID: 2225737 Forward-Port-Of: odoo/enterprise#9518

TaskID: 2225737

Forward-Port-Of: odoo/enterprise#9518

TaskID: 2225736 Forward-Port-Of: odoo/enterprise#9504

TaskID: 2225736

Forward-Port-Of: odoo/enterprise#9504