Friday, August 7, 2020
22 changes · master
New functionality added to Odoo
Website editors can now add decorative SVG background shapes to snippets, including overlays on existing background images and customizable colors. The update also improves background controls so colors, images, and videos can be managed more independently, giving users more creative flexibility without overwriting existing choices.
Original PR description
This commit adds a new snippet option allowing the user to choose one of a series of SVG shapes as their background, or to be overlaid over the background image of a snippet. this commit also introduces some utility functions to deal with multiple css backgrounds. task-2210790
Enhancements to existing features
Website editors can now choose whether individual columns should appear on mobile screens. This gives businesses more control over mobile page layouts, helping them simplify content for smaller devices without affecting desktop views.
Original PR description
This PR attempts to add an editor snippet option to allow to toggle visibility on mobile viewport (when a column targeted in editor). Task ID 2308828
Resolved issues and error corrections
This fix prevents the search panel from accidentally changing its saved state while preparing it for export. It helps avoid incorrect search panel behavior when views are restored, making navigation and filtering more reliable for users.
Original PR description
Having maps in its state, the search panel has to serialise its state before sending it via exportState. Before this commit, this was done on the state object in place, causing issues if the model was restored without an imported state (no re-serialisation hence having a wrong state). Now, the exported object is deep-copied from the original state. Task 2312131
Miscellaneous changes
When trying to generate translation for a model that is not present in the registry (leftover of migration?), the code used to return `self.browse()`, expecting an empty recordset. self was however a `TranslationModuleReader` that has no browse method Return None as the first line after `_get_translatable_records` is ```py if not records: continue ``` Forward-Port-Of: odoo/odoo#55554
Original PR description
When trying to generate translation for a model that is not present in
the registry (leftover of migration?), the code used to return
`self.browse()`, expecting an empty recordset.
self was however a `TranslationModuleReader` that has no browse method
Return None as the first line after `_get_translatable_records` is
```py
if not records:
continue
```
Forward-Port-Of: odoo/odoo#55554Accounting localization modules are now grouped into clearer categories such as chart of accounts, EDI, point of sale, purchases, reporting, and sales. This makes it easier for users to find and install the right fiscal localization packages from accounting settings.
Original PR description
Task [2309613](https://www.odoo.com/web#id=2309613&action=333&active_id=967&model=project.task&view_type=form&cids=1&menu_id=4720)
We have a new hierarchy:
* Accounting
* [Generic, not changed]
* Localization
* Account Chart
* Check
* EDI
* Point of Sale
* Purchase
* Reporting
* Sale
This helps in displaying only the chart of accounts when clicking on
"Install more Packages" from the accounting settings in the Fiscal
Localization section.
We can also refine the search in the _auto_install_l10n post init hook
of account.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis change removes outdated code from the Time Off reporting area that no longer has any effect. Privacy protection for leave descriptions remains in place through newer safeguards, so users should not see a functional change.
Original PR description
_read_from_database was removed in the ormpocalypse of 13.0 . It was used in hr leaves report to make leave name (holding description) anonymous for people not belonging to HR groups. That way people havign access to hr.leave model but not member of hr groups could not read leave description as it is considered as private information. Since 13.0 _read_from_database has been removed. A security has been added in read_group itself, preventing to try to read name through read_group. In this commit we therefore simply remove dead code as the feature itself is still alive. Task ID-2285881
Updates the website editor panel with refined colors, typography, dropdowns, controls, and snippet previews to make page editing feel clearer and more consistent. It also removes outdated snippet thumbnail handling and reuses shared button and link styling for easier maintenance.
This update reorganizes many country-specific accounting and localization add-ons into clearer module categories. It helps businesses and administrators find the right localization features more easily without changing core accounting behavior.
Original PR description
Task [2309613](https://www.odoo.com/web#id=2309613&action=333&active_id=967&model=project.task&view_type=form&cids=1&menu_id=4720) Community PR: https://github.com/odoo/odoo/pull/55384
The website editor now updates option controls more directly and avoids unnecessary preview notifications. This makes editing snippets feel smoother by preventing flicker when users hover or preview different design choices.
This update corrects how default values are prepared in the delivery package selection wizard. It helps ensure the delivery workflow opens with the expected information and avoids errors caused by the previous setup.
Original PR description
Finetuning of addffca4235b0f751f3ad43943ca837544b307b6 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes a small issue in the employee contract signing flow where default values for the document wizard could be loaded incorrectly. It helps ensure contract documents open with the expected preset information, reducing user confusion during HR contract signing.
Original PR description
Finetuning of a8c2bceb178d2d2f0b365cd126744459dbd1626c Community PR (same problem): https://github.com/odoo/odoo/pull/55639
- Create an invoice using a tax exigible on_payment. - Refund the invoice with 'Full refund'. => Traceback: The lines are already reconciled. Explanation: Odoo tried to reconcile all lines having a reconcile account, including the one set on taxes. - The first reconciliation is made on the receivable account triggering the cash basis entries that will be reconcile with the tax account. - The second reconciliation fails because the account has been reconciled to the cash basis entries.
Original PR description
- Create an invoice using a tax exigible on_payment. - Refund the invoice with 'Full refund'. => Traceback: The lines are already reconciled. Explanation: Odoo tried to reconcile all lines having a reconcile account, including the one set on taxes. - The first reconciliation is made on the receivable account triggering the cash basis entries that will be reconcile with the tax account. - The second reconciliation fails because the account has been reconciled to the cash basis entries. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#55584
Forward-Port-Of: odoo/odoo#55567
Original PR description
Forward-Port-Of: odoo/odoo#55567
- Install Contacts and Belgium - Accounting (l10n_be) - Go to Contacts and create a new Contact: * Select Switzerland as Country * Enter "CHE-123.456.788 TVA" ad VAT The VAT is auto-updated to "CHE123456788TVA", removing all special characters. The entered VAT is converted to its minimal representation, stripping whitespaces and seperators, before the check. And it is this compacted value that is stored. As defined here (https://www.estv.admin.ch/estv/fr/home/mehrwertsteuer/fachin
Original PR description
- Install Contacts and Belgium - Accounting (l10n_be) - Go to Contacts and create a new Contact: * Select Switzerland as Country * Enter "CHE-123.456.788 TVA" ad VAT The VAT is auto-updated to…
- Install Contacts and Belgium - Accounting (l10n_be) - Go to Contacts and create a new Contact: * Select Switzerland as Country * Enter "CHE-123.456.788 TVA" ad VAT The VAT is auto-updated to "CHE123456788TVA", removing all special characters. The entered VAT is converted to its minimal representation, stripping whitespaces and seperators, before the check. And it is this compacted value that is stored. As defined here (https://www.estv.admin.ch/estv/fr/home/mehrwertsteuer/fachinformationen/steuerpflicht/unternehmens-identifikationsnummer--uid-.html), the Swiss VAT format should be CHE-XXX.XXX.XXX TVA. Therefore, the VAT will be automatically formated to the official format after the check. opw-2291581 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#55550 Forward-Port-Of: odoo/odoo#55234
fine tuning of https://github.com/odoo/odoo/commit/8444b476f64d022a51358c8fb374b4107256f27b Timeout should be an integer, get_param return a string. Forward-Port-Of: odoo/odoo#55369 Forward-Port-Of: odoo/odoo#55103
Original PR description
fine tuning of https://github.com/odoo/odoo/commit/8444b476f64d022a51358c8fb374b4107256f27b Timeout should be an integer, get_param return a string. Forward-Port-Of: odoo/odoo#55369 Forward-Port-Of: odoo/odoo#55103
According to what has been discussed in https://github.com/OCA/l10n-spain/issues/1434, there's a problem with this account, that can be put in 2 places in the balance sheet, depending on its nature. Unfolding it in 2 using same prefix, we can guide users in which account they should book their balances according the nature, and define reports according these accounts without the need of modifying them each time. Closes OCA/l10n-spain#1434 Forward-Port-Of: odoo/odoo#55545 Forward-Port-
Original PR description
According to what has been discussed in https://github.com/OCA/l10n-spain/issues/1434, there's a problem with this account, that can be put in 2 places in the balance sheet, depending on its nature. Unfolding it in 2 using same prefix, we can guide users in which account they should book their balances according the nature, and define reports according these accounts without the need of modifying them each time. Closes OCA/l10n-spain#1434 Forward-Port-Of: odoo/odoo#55545 Forward-Port-Of: odoo/odoo#55522
A POS payment method should be translatable. opw-2314353 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#55608
Original PR description
A POS payment method should be translatable. opw-2314353 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#55608
Before this commit, In a Mass mailing module, while creating new mailing list website popup content (html field) remains empty which is rendering wysiwyg iframe content. This bug arries from this commit[1] in which public methods are converted into the private methods. So that this template is considered as a private and server throw access error while loading template. After this commit, website popup content template is considered as a public and loading properly that allow users to
Original PR description
Before this commit, In a Mass mailing module, while creating new mailing list website popup content (html field) remains empty which is rendering wysiwyg iframe content. This bug arries from this commit[1] in which public methods are converted into the private methods. So that this template is considered as a private and server throw access error while loading template. After this commit, website popup content template is considered as a public and loading properly that allow users to customize their popup. [1] - https://github.com/odoo/odoo/commit/d9287caf9408bb4ff85ad734cbca08e44321e205 Task Id : 2292026 Forward-Port-Of: odoo/odoo#54798
With company country and localization set to Peru Go to invoice dashboard Click on 'Send sample' User will receive the warning 'If you want to use "Off-Balance Sheet" accounts, all the accounts of the journal entry must be of this type' and the action will abort because the first account fetched for the operation is an 'Off Balance' account opw-2300813 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#55036 Forwa
Original PR description
With company country and localization set to Peru Go to invoice dashboard Click on 'Send sample' User will receive the warning 'If you want to use "Off-Balance Sheet" accounts, all the accounts of the journal entry must be of this type' and the action will abort because the first account fetched for the operation is an 'Off Balance' account opw-2300813 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#55036 Forward-Port-Of: odoo/odoo#54991
**Current behavior before PR:** Traceback appearing while going to close subtypes dialog from followers or closing the attachment viewer dialog. This is happening because the dialog manager doesn't have a close function after [commit](https://github.com/odoo/odoo/commit/9216bdcb6f0bbb20900a33bbf7283e6e4fda1b2c) **Desired behavior after PR is merged:** Able to close the dialog without any traceback as fix it by calling the delete function. **LINKS** PR https://github.com/odo
Original PR description
**Current behavior before PR:** Traceback appearing while going to close subtypes dialog from followers or closing the attachment viewer dialog. This is happening because the dialog manager doesn't have a close function after [commit](https://github.com/odoo/odoo/commit/9216bdcb6f0bbb20900a33bbf7283e6e4fda1b2c) **Desired behavior after PR is merged:** Able to close the dialog without any traceback as fix it by calling the delete function. **LINKS** PR https://github.com/odoo/odoo/pull/55629 Task-2314898 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#55629
Issue - Install "Accounting" module - Go to "Accounting->Accounting->Miscellaneous->Journal Entries" - Create a new journal entries with journal items. - Go to "Accounting->Customers->Invoices" - Toggle Studio - Open "Reports" view and choose any template All account.move are retrieved (journal entries included). Cause Since 13.0, journal entries are also considered as 'account.move', therefore must filter results to remove them; otherwise not possible to print invoi
Original PR description
Issue - Install "Accounting" module - Go to "Accounting->Accounting->Miscellaneous->Journal Entries" - Create a new journal entries with journal items. - Go to "Accounting->Customers->Invoices" - Toggle Studio - Open "Reports" view and choose any template All account.move are retrieved (journal entries included). Cause Since 13.0, journal entries are also considered as 'account.move', therefore must filter results to remove them; otherwise not possible to print invoices and hard to lookup for them if lot of journal entries. Solution If report.model is 'account.move', exclude moves with type as 'entry'. opw-2301559 Forward-Port-Of: odoo/enterprise#12259
Following https://github.com/odoo/odoo/pull/55522 https://github.com/OCA/l10n-spain/issues/1434 Forward-Port-Of: odoo/enterprise#12258 Forward-Port-Of: odoo/enterprise#12248
Original PR description
Following https://github.com/odoo/odoo/pull/55522 https://github.com/OCA/l10n-spain/issues/1434 Forward-Port-Of: odoo/enterprise#12258 Forward-Port-Of: odoo/enterprise#12248