Saturday, April 1, 2023
6 changes · master
Miscellaneous changes
Steps to reproduce ================== - Go to the product page - Open studio - Click on the picture and set the size to large - Save and quit studio - -> The size doesn't change Port of https://github.com/odoo/odoo/pull/87087 opw-3217741 Forward-Port-Of: odoo/odoo#116651
Original PR description
Steps to reproduce ================== - Go to the product page - Open studio - Click on the picture and set the size to large - Save and quit studio - -> The size doesn't change Port of https://github.com/odoo/odoo/pull/87087 opw-3217741 Forward-Port-Of: odoo/odoo#116651
Install `l10n_au_keypay` on a fresh database, run the tests: two tests in `spreadsheet_account` fail. They wrongly assumed the last fiscal day of the main company is always 31th December. This is not true with the module mentioned above installed since https://github.com/odoo/odoo/commit/65dacfc17bec5feba1216354c71ca542c1b762b2 (look at `chart_template.py`) Runbot build errors: 19796, 19797 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-
Original PR description
Install `l10n_au_keypay` on a fresh database, run the tests: two tests in `spreadsheet_account` fail. They wrongly assumed the last fiscal day of the main company is always 31th December. This is not true with the module mentioned above installed since https://github.com/odoo/odoo/commit/65dacfc17bec5feba1216354c71ca542c1b762b2 (look at `chart_template.py`) Runbot build errors: 19796, 19797 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#117218
…h payments Joining from amls to SO is too much costly. Instead, retrieve the SO directly. If the SO is already invoiced, the matching rules will retrieve the amls since the matching rules are now taking into account the invoice_origin field populated with reference of the originator SO. Also, use directly the tokens to deduce or not if the query will be meaningful or not. For example, we want to execute the query matching the sale orders only if at least one token is prefixed correctly
Original PR description
…h payments Joining from amls to SO is too much costly. Instead, retrieve the SO directly. If the SO is already invoiced, the matching rules will retrieve the amls since the matching rules are now taking into account the invoice_origin field populated with reference of the originator SO. Also, use directly the tokens to deduce or not if the query will be meaningful or not. For example, we want to execute the query matching the sale orders only if at least one token is prefixed correctly by 'SO'. Forward-Port-Of: odoo/enterprise#39140 Forward-Port-Of: odoo/enterprise#38964
Steps to reproduce ================== - Create an app with studio - Switch to the search editor - Drag a field to the empty group by column -> Cannot read properties of undefined (reading 'Symbol(nodeStudioXpath)') Cause of the issue ================== node.attrs is missing opw-3240928 Forward-Port-Of: odoo/enterprise#39154 Forward-Port-Of: odoo/enterprise#38989
Original PR description
Steps to reproduce ================== - Create an app with studio - Switch to the search editor - Drag a field to the empty group by column -> Cannot read properties of undefined (reading 'Symbol(nodeStudioXpath)') Cause of the issue ================== node.attrs is missing opw-3240928 Forward-Port-Of: odoo/enterprise#39154 Forward-Port-Of: odoo/enterprise#38989
Steps to reproduce ================== - Go to project - Open studio - Click on a field - Add the bold attribute It isn't applied opw-3231363 Forward-Port-Of: odoo/enterprise#38785
Original PR description
Steps to reproduce ================== - Go to project - Open studio - Click on a field - Add the bold attribute It isn't applied opw-3231363 Forward-Port-Of: odoo/enterprise#38785
If applied, this commit will solve the issue of creating a letter in snailmail. Error: 'cannot adapt type res.company' while evaluating _cron_execute_followup(). This error comes when we create the letter in snailmail, the 'company_id' is passed as an object like 'to_send_partner.company_id' but it will take the 'id' of the record. so it should be 'to_send_partner.company_id.id'. sentry - 3833502258 Forward-Port-Of: odoo/enterprise#37047
Original PR description
If applied, this commit will solve the issue of creating a letter in snailmail. Error: 'cannot adapt type res.company' while evaluating _cron_execute_followup(). This error comes when we create the letter in snailmail, the 'company_id' is passed as an object like 'to_send_partner.company_id' but it will take the 'id' of the record. so it should be 'to_send_partner.company_id.id'. sentry - 3833502258 Forward-Port-Of: odoo/enterprise#37047