Thursday, September 10, 2020
25 changes · master
Enhancements to existing features
The payment settings now show a clearer tooltip to help users better understand the related option. This small wording improvement reduces confusion during payment configuration.
Resolved issues and error corrections
This update tidies the marketing automation mailing view so the correct queue action buttons can be managed reliably. It also removes an obsolete adjustment for a scheduling button that no longer exists, reducing maintenance risk without changing business workflows.
Original PR description
- The action button 'action_put_in_queue' was replaced by two buttons (one with confirmation, the other not) but with same action name. Since `position="replace"` does not replace both, we must add ids to buttons so we can target them. - The action button 'action_schedule' was removed from 'mass_mailing' module, no need to replace it anymore. Task ID 2202759 Related: odoo/odoo#48358
Because we are using self[0], we need to ensure the order to have something deterministic. We want the first entry of the period to have a sample name. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#56866
Original PR description
Because we are using self[0], we need to ensure the order to have something deterministic. We want the first entry of the period to have a sample name. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#56866
Two account.account M2O where authorizing off-balance accounts while they should not be selectable. This change aim to fix that. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#57317
Original PR description
Two account.account M2O where authorizing off-balance accounts while they should not be selectable. This change aim to fix that. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#57317
The recent changes in misc improvements broke the loading of the exchange accounts in the chart template. This change aim to fix that by moving the setup of those accounts back where it was originally done. Taks id #2319601 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#57321 Forward-Port-Of: odoo/odoo#55849
Original PR description
The recent changes in misc improvements broke the loading of the exchange accounts in the chart template. This change aim to fix that by moving the setup of those accounts back where it was originally done. Taks id #2319601 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#57321 Forward-Port-Of: odoo/odoo#55849
Recent changes to make post all entries works from the dashboard broke it when used from the move list. This commit will fix that and make sure it works in both situation Problematic PR : https://github.com/odoo/odoo/pull/56371 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#57327 Forward-Port-Of: odoo/odoo#57229
Original PR description
Recent changes to make post all entries works from the dashboard broke it when used from the move list. This commit will fix that and make sure it works in both situation Problematic PR : https://github.com/odoo/odoo/pull/56371 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#57327 Forward-Port-Of: odoo/odoo#57229
1af543a399dccf837f7305df2b5e3e1eb0e90da9 removed the default time limit for CSRF tokens, because of the usability issues and the limited security benefit. However the timestamp that was used to implement the limit also served as a salt, making the CSRF token variable for each request. This is a desirable property that can help mitigate some attacks, such as BREACH. This patch re-introduces the variability by including a distant expiry (1 year) when no specific time limit is passed. The pur
Original PR description
1af543a399dccf837f7305df2b5e3e1eb0e90da9 removed the default time limit for CSRF tokens, because of the usability issues and the limited security benefit. However the timestamp that was used to implement the limit also served as a salt, making the CSRF token variable for each request. This is a desirable property that can help mitigate some attacks, such as BREACH. This patch re-introduces the variability by including a distant expiry (1 year) when no specific time limit is passed. The purpose isn't to expire the token, but simply to serve as a salt. Forward-Port-Of: odoo/odoo#57274
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#57136
Original PR description
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#57136
During the `test_01_tickets_questions` a tour is started as a portal user to reserve tickets for the newly created event. At the end of the tour, a modal is opened and once filled, the `continue` button is used. The problem is that the tour stops without waiting but the python tests continues. If the HttpCase session is cleared before the tickets are registered, the test fails with a `400 Bad Request: Session expired` warning and the next python assertion cannot be fullfilled. Descript
Original PR description
During the `test_01_tickets_questions` a tour is started as a portal user to reserve tickets for the newly created event. At the end of the tour, a modal is opened and once filled, the `continue` button is used. The problem is that the tour stops without waiting but the python tests continues. If the HttpCase session is cleared before the tickets are registered, the test fails with a `400 Bad Request: Session expired` warning and the next python assertion cannot be fullfilled. 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#57264
[FIX] account: Invoice in Documents not linked to the original invoice Steps to reproduce the bug: - Install Accounting and Documents - Go to Documents configuration - Enable Files Centralization > Accounting and save - Still in Documents configuration, into "-> Journals", create a new Journal to Synchronize with: - Journal: Customer Invoices (USD) - Go to Accounting > Customers > Invoices - Create a new invoice with any customer and product and save - "Post" then "Send & Print" -
Original PR description
[FIX] account: Invoice in Documents not linked to the original invoice Steps to reproduce the bug: - Install Accounting and Documents - Go to Documents configuration - Enable Files Centralization >…
[FIX] account: Invoice in Documents not linked to the original invoice Steps to reproduce the bug: - Install Accounting and Documents - Go to Documents configuration - Enable Files Centralization > Accounting and save - Still in Documents configuration, into "-> Journals", create a new Journal to Synchronize with: - Journal: Customer Invoices (USD) - Go to Accounting > Customers > Invoices - Create a new invoice with any customer and product and save - "Post" then "Send & Print" - On the dialog, "Send & Print" (confirm the report template if necessary) - Go to Documents Bug: The document is missing the "related resource" link shortcut Cause: The context key `default_res_id` is propagated up to: https://github.com/odoo/enterprise/blob/a6606f000e66e72b9f89d353552950652ab2045f/documents/models/document.py#L364 Consequently, the corresponding document is created with a `res_id`, but no `res_model` as `default_res_model` is not set. By adding the `default_res_model` context key, the document is created with the right `res_model`. Note that another solution would be to remove `default_res_id` from the context before creating the `documents.document` and leave the `_compute_res_record` do the job. However, this could have a larger impact since it would affect all document creations. opw:2332596 Forward-Port-Of: odoo/odoo#57341
Issue - Ensure that the provider of "The Poste" delivery method is "Based on Rules". - Create a quotation with "The Poste" as shipping method. - Confirm, then click on "Delivery" stat button. - Click on "Put in Pack" and create a "Delivery Packaging". - Save, go back to quotation and duplicate it. - Confirm, then click on "Delivery" stat button. - Click on "Put in Pack". The "Delivery Packaging" created previously is not available. Solution If 'current_package_carrier_
Original PR description
Issue - Ensure that the provider of "The Poste" delivery method is "Based on Rules". - Create a quotation with "The Poste" as shipping method. - Confirm, then click on "Delivery" stat button. - Click on "Put in Pack" and create a "Delivery Packaging". - Save, go back to quotation and duplicate it. - Confirm, then click on "Delivery" stat button. - Click on "Put in Pack". The "Delivery Packaging" created previously is not available. Solution If 'current_package_carrier_type' is equal to 'fixed' or 'base_on_rule', replace it by 'none' since there are the equivalents in 'package_carrier_type' for 'delivery_type'. Related fix : https://github.com/odoo/odoo/pull/37427 opw-2310258 Forward-Port-Of: odoo/odoo#57152
task-2333128 Forward-Port-Of: odoo/odoo#57192
Original PR description
task-2333128 Forward-Port-Of: odoo/odoo#57192
task-2310610 Forward-Port-Of: odoo/odoo#57425
Original PR description
task-2310610 Forward-Port-Of: odoo/odoo#57425
task-2333122 Forward-Port-Of: odoo/odoo#57362
Original PR description
task-2333122 Forward-Port-Of: odoo/odoo#57362
To quote the commit message: > If you define a report using `<report>` it will implicitly add that > action to a Print menu in the model's views. If you use ``<record>`` to > do the same, that won't happen unless you also set `binding_model_id`. > > In older versions that wasn't really an issue because people mainly used > `<report>`, but it was deprecated in 13.5, hence this update. And it > applies to versions older than 13.5 as well, I tested until 11.0. 12.0 was targeted because t
Original PR description
To quote the commit message: > If you define a report using `<report>` it will implicitly add that > action to a Print menu in the model's views. If you use ``<record>`` to > do the same, that won't happen unless you also set `binding_model_id`. > > In older versions that wasn't really an issue because people mainly used > `<report>`, but it was deprecated in 13.5, hence this update. And it > applies to versions older than 13.5 as well, I tested until 11.0. 12.0 was targeted because the documentation fix builds on some changes that Victor (vfe) made starting in 12.0 and 11.0 will be out of support soon. This PR also includes a fix for an unrelated typo in the Odoo Guidelines that was introduced in 12.0. Forward-Port-Of: odoo/odoo#57421
Forward-Port-Of: odoo/enterprise#13103
Original PR description
Forward-Port-Of: odoo/enterprise#13103
- updated list view to display the thumbnail as an optional field - update the thumbnail of predefined templates task-id: 2325315 Forward-Port-Of: odoo/enterprise#13118
Original PR description
- updated list view to display the thumbnail as an optional field - update the thumbnail of predefined templates task-id: 2325315 Forward-Port-Of: odoo/enterprise#13118
Link to the release: https://github.com/odoo/o-spreadsheet/releases/tag/0.7.0 Here is the list of changes: Breaking changes ============= * autofill: allow to use a custom component to render the tooltip * `getLastValue` is now replaced by `getTooltip` * The return of the function above is now a `Tooltip`, an object with two attributes: * `component` (optional, a custom owl `Component`) * If empty, it use a default component with simply render the content as a string
Original PR description
Link to the release: https://github.com/odoo/o-spreadsheet/releases/tag/0.7.0 Here is the list of changes: Breaking changes ============= * autofill: allow to use a custom component to render the…
Link to the release: https://github.com/odoo/o-spreadsheet/releases/tag/0.7.0
Here is the list of changes:
Breaking changes
=============
* autofill: allow to use a custom component to render the tooltip
* `getLastValue` is now replaced by `getTooltip`
* The return of the function above is now a `Tooltip`, an object with two attributes:
* `component` (optional, a custom owl `Component`)
* If empty, it use a default component with simply render the content as a string
* `content` props that are given to the `component`
Improvements
============
* grid, menu: small design/color changes
* helpers: Support sheet reference in toZone
* core: bottom_bar: add sheet context menu
* A new event can now be triggered by `Spreadsheet`: `edit-text`. This event should ask an input to the user and call a given callback with the input
* history: do not historize standalone ACTIVATE_SHEET command
* autofill: allow to use a custom component to render the tooltip
Fixes
=====
* composer: Don't process keyup events after edition is done
In addition to these changes, the Odoo codebase could be updated to support the new `edit-text` event.
Forward-Port-Of: odoo/enterprise#13110
Forward-Port-Of: odoo/enterprise#13095Steps to reproduce the bug: - Let's consider D1, D2, D3 three dates such as D1 > D2 > D3 and D1 = today - Create and configure an asset A with purchasing date and depreciation dates in the past D3 - Dispose A and set the accounting date on the disposal entry DE to D3 - View asset report filtered for the past period [D3, D2] containing the disposal date disposal D3 Bug: DE was not displayed on the asset report DE was diplayed when filtereing for period [D3, D1] because the disposal_d
Original PR description
Steps to reproduce the bug: - Let's consider D1, D2, D3 three dates such as D1 > D2 > D3 and D1 = today - Create and configure an asset A with purchasing date and depreciation dates in the past D3 - Dispose A and set the accounting date on the disposal entry DE to D3 - View asset report filtered for the past period [D3, D2] containing the disposal date disposal D3 Bug: DE was not displayed on the asset report DE was diplayed when filtereing for period [D3, D1] because the disposal_date of A was D1 instead of D3 opw:2320384 Forward-Port-Of: odoo/enterprise#12921 Forward-Port-Of: odoo/enterprise#12890
The creation of a Direct Debit Mandate is causing a traceback when there is no stored_mandate to compute. This fix will ensure that even without stored_mandate, no traceback is caused Task id #2327217 Forward-Port-Of: odoo/enterprise#12780
Original PR description
The creation of a Direct Debit Mandate is causing a traceback when there is no stored_mandate to compute. This fix will ensure that even without stored_mandate, no traceback is caused Task id #2327217 Forward-Port-Of: odoo/enterprise#12780
"Résultat de l'exercice" should be computed from "Bénéfice ou perte" (total_products.balance - total_charges.balance) and not from "1-Résultat d'exploitation (I-II)" (I.balance-II.balance) opw-2319643 Forward-Port-Of: odoo/enterprise#13094 Forward-Port-Of: odoo/enterprise#13075
Original PR description
"Résultat de l'exercice" should be computed from "Bénéfice ou perte" (total_products.balance - total_charges.balance) and not from "1-Résultat d'exploitation (I-II)" (I.balance-II.balance) opw-2319643 Forward-Port-Of: odoo/enterprise#13094 Forward-Port-Of: odoo/enterprise#13075
**Purpose** The problem arises when you edit any record and the state is in dirty mode, and then click on the menu switcher will display the discard message but the top navigation bar will hide. And also display the background image of the main menu in top navigation bar. **SPEC** The issue was, menu toggle mode and show & hide the background of the menu is changed before checking the uncommitted changes present in the record. we are now first to check uncommitted changes and then we w
Original PR description
**Purpose** The problem arises when you edit any record and the state is in dirty mode, and then click on the menu switcher will display the discard message but the top navigation bar will hide. And also display the background image of the main menu in top navigation bar. **SPEC** The issue was, menu toggle mode and show & hide the background of the menu is changed before checking the uncommitted changes present in the record. we are now first to check uncommitted changes and then we will toggle the menu and show the background of the menu. Task : 2312437 Forward-Port-Of: odoo/enterprise#12262
Forward-Port-Of: odoo/enterprise#12760
Original PR description
Forward-Port-Of: odoo/enterprise#12760
PURPOSE This merge commit completes demo data to be able to showcase more of the social features and also fixes a few edge cases. SPECS - Fix the compute method of clicks count when the social.post is not created yet (caused by recent ORM change) ; - Deleting the campaign created by the social_demo module could cause some issues ; - Allow posting social.posts on LinkedIn streams when using the demo_module ; - Complete the demo data of the social_demo module to showcase more fe
Original PR description
PURPOSE This merge commit completes demo data to be able to showcase more of the social features and also fixes a few edge cases. SPECS - Fix the compute method of clicks count when the social.post is not created yet (caused by recent ORM change) ; - Deleting the campaign created by the social_demo module could cause some issues ; - Allow posting social.posts on LinkedIn streams when using the demo_module ; - Complete the demo data of the social_demo module to showcase more features. See underlying commits for details. LINKS Task-2302570 Forward-Port-Of: odoo/enterprise#12548