Tuesday, May 5, 2020
23 changes · master
Enhancements to existing features
This update improves list views by showing clearer icon buttons, status badges, remaining-day indicators, and user or employee avatars directly in records. It makes key information easier to scan across accounting, CRM, HR, events, expenses, fleet, leave, recruitment, timesheets, lunch, links, and mail workflows.
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
Odoo can now send emails to recipients with non-English characters in their email addresses. This improves communication for customers and users in markets where internationalized domain names or Unicode email headers are common.
Original PR description
It has been a recurrent request from customers to be able to send email messages to email addresses containing non-ascii characters. [IDNA] is a domain extension to allow unicode characters in domain names. [SMTPUTF8] is a SMTP extension to allow unicode in any header. IDNA defines the [punycode] encoding which translates unicode to an ascii representation. This encoding MUST be used to encode domains. SMTPUTF8 is an SMTP extension that allow utf-8 in all headers on the envelope. [IDNA] https://tools.ietf.org/html/rfc5890 [SMTPUTF8] https://tools.ietf.org/html/rfc6531 [punycode] https://tools.ietf.org/html/rfc3492 Task: 2116928
Search panel folder entries can now display the number of matching records, making it easier for users to understand where relevant records are before opening a folder. The update also improves how counts are calculated and lets modules such as Accounting keep slimmer panels by disabling these counters where needed.
Original PR description
Display the records count as text-muted on the far right of 'folder' item of the searchpanel. TASK-ID: 2166814 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website editor’s autocomplete menu now adjusts its height based on where it appears on the page, making suggestions easier to view and use. This improves editing usability by reducing awkward overflow and visual spacing issues around the suggestion list.
Original PR description
To imp: auto size height based on position of the autocomplete based on backend override and remove crappy border 1px, margin: -1px from standard library 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
The suggestion dialog shown after leaving an unfinished many-to-one field has been simplified. Users now see clearer wording and no longer need to re-enter the same value, reducing confusion and extra steps.
Original PR description
PURPOSE: The current m2x suggestion dialog displayed to the user when he clicks out of an 'un-committed' m2x should be much simpler with removing the input edition in the dialog. it is not necessary to ask for the input again in dialog. SPEC: With this commit, we have removed the input box from the suggestion dialog and straightforward take the value of the direct input from where we have generated the suggestion dialog. Task : 2234212 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The search panel now shows the number of records next to folder items, making it easier for users to understand how much content each folder contains before opening it. The Documents app was updated to support this behavior consistently across desktop and mobile views.
Original PR description
Display the records count as text-muted on the far right of 'folder' item of the searchpanel. TASK-ID : 2166814
Several business screens have been refreshed to align with newer Odoo interface patterns, including clearer field highlighting and updated button styling. This should make data cleaning and rental-related lists easier to scan and more consistent for users.
Original PR description
Part of task 2195254
Resolved issues and error corrections
This update relaxes a blog performance test so it does not fail due to small, random differences in request counts. It helps keep automated checks reliable without changing the customer-facing blog experience.
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
Miscellaneous changes
…kout Configure your POS with bank payment method only Make a sale with rounding necessary (i.e. 1,29€) The amount will be rounded. Go through the payment screen. Error message will appear because no payment methods available is capable of handling the change, but this is not necessary since we are rounding. Splitting the code to add a more specific condition in pos_cash_rounding fix the issue opw-2239946 -- I confirm I have signed the CLA and read the PR guidelines at www.o
Original PR description
…kout Configure your POS with bank payment method only Make a sale with rounding necessary (i.e. 1,29€) The amount will be rounded. Go through the payment screen. Error message will appear because no payment methods available is capable of handling the change, but this is not necessary since we are rounding. Splitting the code to add a more specific condition in pos_cash_rounding fix the issue opw-2239946 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#50056 Forward-Port-Of: odoo/odoo#50030
Austria now has all 9 states available when entering contact addresses. This makes address data more complete and easier to standardize for Austrian customers and partners.
Original PR description
Impacted versions: - 11.0 12.0 13.0 14.0/master Steps to reproduce: 1. add a new contact 2. select 'Austria' in Address/Country 3. choose State Current behavior before PR: - no predefined states appear Desired behavior after PR is merged: - list all 9 Austrian states Description of the issue/feature this PR addresses: States are missing for country Austria. This PR adds the 9 states to odoo/addons/base/data/res.country.state.csv. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The accounting year-end lock now checks for unprocessed bank statement lines before allowing the fiscal year to be closed. This helps prevent incomplete financial records from being finalized, reducing the risk of accounting errors and later corrections.
Original PR description
-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Validation messages in the online shop are now shown correctly when customers encounter input errors. This helps shoppers understand what needs fixing, reducing confusion during purchasing.
Original PR description
Before this commit, This validation message was not displayed properly. (See https://nimb.ws/OwfLsH ) Now we are displaying Validation error Properly. (See https://nimb.ws/ji3N2h ) 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
Bank statements now post directly after import, and General Ledger account filters opened from the journal dashboard behave correctly. Bank reconciliation reports also show clearer labels and more consistent warnings, helping finance teams spot balance issues more reliably.
Original PR description
task: 2244809
This update fixes several issues in the employee salary package and contract signing flow, including car benefit calculations, unclear errors, missing vehicle data, and duplicate records when employees go back and revalidate. It improves reliability for HR teams and employees completing salary simulations and signatures.
Original PR description
Before this commit: 1. The amount on the right for car company, was always set to 0 when we open the link (it's updated when we change the selected car) 2. When we fold an item (on front end), the…
Before this commit: 1. The amount on the right for car company, was always set to 0 when we open the link (it's updated when we change the selected car) 2. When we fold an item (on front end), the amount of this item (on the right) was not set to 0 3. If we set a contract template for new signature, but no contract template signature for existing contract, we have an error. 4. If we have no hr responsible on contract, the error message was not clear. 5. When we have no available vehicle (empty list), we can have error in python, because we made operation on False. 6. The new vehicle to add in waiting list was never created. 7. vehicle in waitinglist have no future driver and no company. 8. When an employee validate his contract, he arrive on signature page, then he decide to use back button, selected item are always selected but stay folded. 9. Default car on contract has mismatch between partner_id and employee_id After this commit: No more bug from the list above task ID 2214356
Step to reproduce : Import from Excel a list of Opportunities. The problem is that in _compute_day_open, the abs of the extraction date_open - create_date is set as the lead's day_open. As the date_open has no milliseconds, all those records which create date is the same second have a date_open that is before their create_date. Fixed it by comparing the date_create and date_open without microsecond. Task ID 2222251 Forward-Port-Of: odoo/odoo#50574 Forward-Port-Of: odoo/odoo#50431
Original PR description
Step to reproduce : Import from Excel a list of Opportunities. The problem is that in _compute_day_open, the abs of the extraction date_open - create_date is set as the lead's day_open. As the date_open has no milliseconds, all those records which create date is the same second have a date_open that is before their create_date. Fixed it by comparing the date_create and date_open without microsecond. Task ID 2222251 Forward-Port-Of: odoo/odoo#50574 Forward-Port-Of: odoo/odoo#50431
Steps to reproduce: - install sales, ecommerce and payment_authorize - setup authorize.net (test mode) - go to sales and select the quotation S00007 (demo data) or create a quotation with multiple items that add up to a float - select action > generate a payment link > go to the link > select pay with authorize - you are redirected to authorize.net use 4111 1111 1111 1111 as card number and 1223 as expiration date > pay - you are redirected to the odoo payment process page - wait for th
Original PR description
Steps to reproduce: - install sales, ecommerce and payment_authorize - setup authorize.net (test mode) - go to sales and select the quotation S00007 (demo data) or create a quotation with multiple…
Steps to reproduce: - install sales, ecommerce and payment_authorize - setup authorize.net (test mode) - go to sales and select the quotation S00007 (demo data) or create a quotation with multiple items that add up to a float - select action > generate a payment link > go to the link > select pay with authorize - you are redirected to authorize.net use 4111 1111 1111 1111 as card number and 1223 as expiration date > pay - you are redirected to the odoo payment process page - wait for the result Previous behavior: the user is returned to a 404 error page but the payment went trough Current behavior: access_token generation is consistent and will not fail because of float representation the user is returned to the "payment confirmed" page WARNINGS: - watching the values in vscode prevents bug reproduction - when setting up authorize.net, do not forget to add your test url to the account's allowed return urls - use https for authorize.net connection opw-2223135 Forward-Port-Of: odoo/odoo#50577
Before this commit, and in 13.0, you had access to gray colors in bootstrap_overridden.scss files through the `palette-gray` function but only if the gray was explicitely defined in the theme palette. This was fine as only those were used at that time. Now, some themes want to use the default BS gray values in those files to customize other variables. The solution is to "force" all grays in the selected gray palette, using the BS values by default. Forward-Port-Of: odoo/odoo#50634
Original PR description
Before this commit, and in 13.0, you had access to gray colors in bootstrap_overridden.scss files through the `palette-gray` function but only if the gray was explicitely defined in the theme palette. This was fine as only those were used at that time. Now, some themes want to use the default BS gray values in those files to customize other variables. The solution is to "force" all grays in the selected gray palette, using the BS values by default. Forward-Port-Of: odoo/odoo#50634
Forward-Port-Of: odoo/odoo#50541 Forward-Port-Of: odoo/odoo#50524
Original PR description
Forward-Port-Of: odoo/odoo#50541 Forward-Port-Of: odoo/odoo#50524
La moneda oficial del Ecuador cambió de sucre a dolar en el año 2000. 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#50518
Original PR description
La moneda oficial del Ecuador cambió de sucre a dolar en el año 2000. 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#50518
Forward-Port-Of: odoo/odoo#50628 Forward-Port-Of: odoo/odoo#50489
Original PR description
Forward-Port-Of: odoo/odoo#50628 Forward-Port-Of: odoo/odoo#50489
In 29f02a37f042 we bumped the verion of libsass that we use. One breaking change introduced by the new version is that if a css variable is interpolated to the empty string, it is still emited in the compiled css [1] This commit fixes that by explicitly omitting null values from the map before looping over it. [1]: https://sass-lang.com/documentation/breaking-changes/css-vars task-2248360 Forward-Port-Of: odoo/odoo#50545
Original PR description
In 29f02a37f042 we bumped the verion of libsass that we use. One breaking change introduced by the new version is that if a css variable is interpolated to the empty string, it is still emited in the compiled css [1] This commit fixes that by explicitly omitting null values from the map before looping over it. [1]: https://sass-lang.com/documentation/breaking-changes/css-vars task-2248360 Forward-Port-Of: odoo/odoo#50545
Description of the issue/feature this PR addresses: When a product has multiple variants the weight and packages are missing in the product form view. Current behavior before PR: When you go to the menu for product variants and open a product that has no variants the weight and packages are displayed. When you open a product that has variants the weight and packages are missing. Desired behavior after PR is merged: Display weight and packages always in product variants. -- I
Original PR description
Description of the issue/feature this PR addresses: When a product has multiple variants the weight and packages are missing in the product form view. Current behavior before PR: When you go to the menu for product variants and open a product that has no variants the weight and packages are displayed. When you open a product that has variants the weight and packages are missing. Desired behavior after PR is merged: Display weight and packages always in product variants. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#50479
Task [2214246](https://www.odoo.com/web#action=333&active_id=967&cids=1&id=2214246&menu_id=4720&model=project.task&view_type=form) The unreconciled move lines considered didn't look at the type of the move, that could lead to negative amounts overdue. Those lines were unreconciled and therefore the system said there was an action to perform in the followup reports. Forward-Port-Of: odoo/enterprise#9197
Original PR description
Task [2214246](https://www.odoo.com/web#action=333&active_id=967&cids=1&id=2214246&menu_id=4720&model=project.task&view_type=form) The unreconciled move lines considered didn't look at the type of the move, that could lead to negative amounts overdue. Those lines were unreconciled and therefore the system said there was an action to perform in the followup reports. Forward-Port-Of: odoo/enterprise#9197