Wednesday, June 9, 2021
13 changes · master
Features or functions removed from Odoo
This change removes an obsolete calendar configuration that was only needed for an older implementation. It should not change how users work with calendar events, but it simplifies the underlying code and reduces maintenance risk.
Original PR description
it was made for old implementation that is changed since Odoo 14.0 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
Outdated web module documentation files were removed because they are no longer maintained or built as part of the project. This reduces repository clutter and helps teams focus on current, supported documentation sources.
Original PR description
AFAIK, this documentation isn't built anywhere and is not maintained anyway. Since the developer documentation was recently removed from odoo/odoo repository, it's the right time to remove this old doc content. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
HTML fields used to have a toggle button for a "code view" (which came from the Summernote library), in debug mode. This allowed the advanced user to edit content with jinja conditions. This was lost with the new editor but reintroduced for Mass Mailing. As it turns out it was needed elsewhere so this makes the code view available as a node option, and already activates it for mail templates. To activate the code view in an html field: ```xml <field type="html" options="'codeview': True"/>
Original PR description
HTML fields used to have a toggle button for a "code view" (which came from the Summernote library), in debug mode. This allowed the advanced user to edit content with jinja conditions. This was lost with the new editor but reintroduced for Mass Mailing. As it turns out it was needed elsewhere so this makes the code view available as a node option, and already activates it for mail templates. To activate the code view in an html field: ```xml <field type="html" options="'codeview': True"/> ``` Task #2561300   -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#71860
When confirming a RfQ, even if a follower is subscribed to "RFQ Confirmed", he will not receive any email. To reproduce the error: (Need a mail catcher) 1. Create a PO 2. Add a follower and edit his subscriptions: - Check 'RFQ Confirmed' 3. Confirm the PO Error: No mail has been sent. The user should have been subscribed to "RFQ Approved" to receive an email. OPW-2447234 Forward-Port-Of: odoo/odoo#71846 Forward-Port-Of: odoo/odoo#71594
Original PR description
When confirming a RfQ, even if a follower is subscribed to "RFQ
Confirmed", he will not receive any email.
To reproduce the error:
(Need a mail catcher)
1. Create a PO
2. Add a follower and edit his subscriptions:
- Check 'RFQ Confirmed'
3. Confirm the PO
Error: No mail has been sent. The user should have been subscribed to
"RFQ Approved" to receive an email.
OPW-2447234
Forward-Port-Of: odoo/odoo#71846
Forward-Port-Of: odoo/odoo#71594Link to the original commit: https://github.com/odoo/odoo/pull/71596/commits/fc9d63f541340ebcd485cffcd6e9a3ee6cd57f49 opw-2547663 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#71861 Forward-Port-Of: odoo/odoo#71810
Original PR description
Link to the original commit: https://github.com/odoo/odoo/pull/71596/commits/fc9d63f541340ebcd485cffcd6e9a3ee6cd57f49 opw-2547663 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#71861 Forward-Port-Of: odoo/odoo#71810
…mail content It is currently escaped as it is not Markup-ed. Forward-Port-Of: odoo/odoo#71813
Original PR description
…mail content It is currently escaped as it is not Markup-ed. Forward-Port-Of: odoo/odoo#71813
Consider the value as FALSE by default, if it isn't set Having NULL values was the case for My Company (San Francisco) on runbot for instance, because the default value of the field was not applied correctly. Forward-Port-Of: odoo/enterprise#18879
Original PR description
Consider the value as FALSE by default, if it isn't set Having NULL values was the case for My Company (San Francisco) on runbot for instance, because the default value of the field was not applied correctly. Forward-Port-Of: odoo/enterprise#18879
Fixes a traceback in sign.request.item when calling send_signature_accesses with an empty recordset. Introduced with #17538 Forward-Port-Of: odoo/enterprise#18876
Original PR description
Fixes a traceback in sign.request.item when calling send_signature_accesses with an empty recordset. Introduced with #17538 Forward-Port-Of: odoo/enterprise#18876
Should last year (from 12 months ago to now), not last year (from 1/1 to 31/12 of last year) Forward-Port-Of: odoo/enterprise#18875 Forward-Port-Of: odoo/enterprise#18863
Original PR description
Should last year (from 12 months ago to now), not last year (from 1/1 to 31/12 of last year) Forward-Port-Of: odoo/enterprise#18875 Forward-Port-Of: odoo/enterprise#18863
An asset model created from an asset is not usable. To reproduce the error: 1. Create an asset 2. Confirm the asset 3. Save Model 4. Create a new asset: Error: the model is not available 5. Accounting > Configuration > Asset Models Error: the model is not present When consulting an asset, the key `default_asset_type` and `asset_type` are in the context. However, when clicking the action "Save Model", several keys are added: https://github.com/odoo/enterprise/blob/b802b4b8
Original PR description
An asset model created from an asset is not usable. To reproduce the error: 1. Create an asset 2. Confirm the asset 3. Save Model 4. Create a new asset: Error: the model is not available 5.…
An asset model created from an asset is not usable.
To reproduce the error:
1. Create an asset
2. Confirm the asset
3. Save Model
4. Create a new asset:
Error: the model is not available
5. Accounting > Configuration > Asset Models
Error: the model is not present
When consulting an asset, the key `default_asset_type` and `asset_type`
are in the context. However, when clicking the action "Save Model",
several keys are added:
https://github.com/odoo/enterprise/blob/b802b4b856a7ca74f390b78d9cd9fdf52e81b6a5/account_asset/models/account_asset.py#L482-L502
And the old context keys are filtered:
https://github.com/odoo/odoo/blob/44b59d10d0ab6440b0a908f518c157a3d670627b/addons/web/static/src/js/chrome/action_manager_act_window.js#L661-L670
Therefore `default_asset_type` is no more available.
Later, when saving the asset model, since the default value of
`asset_type` is not in the context, the field of the new record is not
defined. Then, the method `flush` triggers the methods `compute`, but
without all context keys mentioned above (`asset_type` is not
available). The field will thus stay undefined:
https://github.com/odoo/enterprise/blob/b802b4b856a7ca74f390b78d9cd9fdf52e81b6a5/account_asset/models/account_asset.py#L187-L195
This is the reason why the model won't be usable.
OPW-2467962
Forward-Port-Of: odoo/enterprise#18800…via the back end The return product and payment action from the back end should have been removed from the Point of Sale but it is not. This commit prevents the user from refunding and paying via the back end and should do it in the PoS UI (where the transaction calls to Fiskaly are executed) Forward-Port-Of: odoo/enterprise#18816
Original PR description
…via the back end The return product and payment action from the back end should have been removed from the Point of Sale but it is not. This commit prevents the user from refunding and paying via the back end and should do it in the PoS UI (where the transaction calls to Fiskaly are executed) Forward-Port-Of: odoo/enterprise#18816
Prior to this commit, the owl templates defined in project_enterprise and depending on web_enterprise templates caused a traceback when project_enterprise is installed before web_enterprise, when the installation scheduler installs web_enterprise after project_enterprise. This use case may happen when you directly install project_enterprise or industry_fsm. As the web_enterprise module will always be installed together with project_enterprise, this commit only enforces the dependency an
Original PR description
Prior to this commit, the owl templates defined in project_enterprise and depending on web_enterprise templates caused a traceback when project_enterprise is installed before web_enterprise, when the installation scheduler installs web_enterprise after project_enterprise. This use case may happen when you directly install project_enterprise or industry_fsm. As the web_enterprise module will always be installed together with project_enterprise, this commit only enforces the dependency and forces the web_enterprise module to be installed before project_enterprise. Co-authored-by: Xavier BOL (xbo) <xbo@odoo.com> Forward-Port-Of: odoo/enterprise#18865
Description of the issue/feature this PR addresses: 1: When for all products in an invoice the tax_type is set to 'Exento', there is a validation error for the generated CFDI (empty Traslados element instead of nothing) Desired behavior after PR is merged: The same behaviour as in v13, tax exemption is handled well and unnecessary elements are not included in the generated CFDI. OPW: 2508381 Forward-Port-Of: odoo/enterprise#18794 Forward-Port-Of: odoo/enterprise#18754
Original PR description
Description of the issue/feature this PR addresses: 1: When for all products in an invoice the tax_type is set to 'Exento', there is a validation error for the generated CFDI (empty Traslados element instead of nothing) Desired behavior after PR is merged: The same behaviour as in v13, tax exemption is handled well and unnecessary elements are not included in the generated CFDI. OPW: 2508381 Forward-Port-Of: odoo/enterprise#18794 Forward-Port-Of: odoo/enterprise#18754