In this commit: - Updated Table 12 HSN Summary to classify HSN data separately for B2B and B2C as per the latest GST advisory. - Previously, all HSN summary data was pushed into Table 12 without distinction. - Now, HSN summary is categorized into B2B and B2C for accurate reporting. Task ID: 4465102 Forward-Port-Of: odoo/enterprise#84215 Forward-Port-Of: odoo/enterprise#80738

In this commit:
- Updated Table 12 HSN Summary to classify HSN data separately for B2B and B2C as per the latest GST advisory.
- Previously, all HSN summary data was pushed into Table 12 without distinction.
- Now, HSN summary is categorized into B2B and B2C for accurate reporting.

Task ID: 4465102

Forward-Port-Of: odoo/enterprise#84215
Forward-Port-Of: odoo/enterprise#80738

Scenario: create a long blog page article and enable comments Result: there is a grey unusable textarea with o-mail-Composer-fake over the blog content. Issue: in 7710c3331ebd22f8396870bd0731f8c1152d9c41 the fake textarea used to compute the height of the real textarea, had a position of -10000px, which make sense in the backend to make it hidden. But in 18.0 with 368eb78a9cedfce0802b64fd2782e1c018541e40 we use the backend composer on portal, where a page could be higher than 10000px and the f

Scenario: create a long blog page article and enable comments

Result: there is a grey unusable textarea with o-mail-Composer-fake
over the blog content.

Issue: in 7710c3331ebd22f8396870bd0731f8c1152d9c41 the fake textarea
used to compute the height of the real textarea, had a position of
-10000px, which make sense in the backend to make it hidden. But in
18.0 with 368eb78a9cedfce0802b64fd2782e1c018541e40 we use the backend
composer on portal, where a page could be higher than 10000px and the
fake textarea can be shown.

Fix: hide it better (also to the left, and in case there was a
10000x10000 pixels page with comment at the bottom right, make it
invisible).

opw-4719975

Forward-Port-Of: odoo/odoo#207054

Description of the issue/feature this PR addresses: mailing.mailing model is reused between Mail Marketing and SMS Marketing apps, however warning message defined in Mail Marketing about incorrect mail server is not relevant for SMS Marketing. Affected versions : 16.0+ (probably since v13.0 but older versions not maintained anymore) Current behavior before PR: In some cases, you can end up with a warning on SMS mailing form stating "This email from can not be used with this mail server.[..

Description of the issue/feature this PR addresses:
mailing.mailing model is reused between Mail Marketing and SMS Marketing apps, however warning message defined in Mail Marketing about incorrect mail server is not relevant for SMS Marketing.
Affected versions : 16.0+ (probably since v13.0 but older versions not maintained anymore)

Current behavior before PR:
In some cases, you can end up with a warning on SMS mailing form stating "This email from can not be used with this mail server.[...]"

For instance you can end up in this case if : 
- You have defined an ir.config_parameter mass_mailing.mail_server_id
- from_filter from this mail_server does not match email_from from user creating SMS Marketing

Desired behavior after PR is merged:
The above warning is only relevant for Mail marketing but not for SMS marketing.

This PR therefore proposes to generate warning message only if mailing_type == "mail"




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

Forward-Port-Of: odoo/odoo#205912