Tuesday, January 26, 2021
14 changes · master
Enhancements to existing features
The Swedish OCR payment reference features are now included directly in the main Swedish localization module, reducing setup complexity for companies operating in Sweden. The update also improves translations, partner form integration, and data cleanup behavior when the module is removed.
Original PR description
merge module l10n_se_ocr into l10n_se Also set ondelete policy for field invoice_reference_model for invoice_reference_model field with selection add a property into account.journal set ondelete policy that implements the proper cleanup of the corresponding records upon module uninstallation -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now find contacts and leads by phone or mobile number even when the number is typed with different formatting. This improves search results in CRM, contacts, and SMS-related views while reusing the same phone search logic across modules.
Original PR description
Before this commit the user had to type in the exact same formatting to find contacts. After this commit the user will be able to get better search results and does not have to type the same formatting. To avoid code duplication, the existing search_mobile_phone method has been moved to the mail_thread_phone class, so that it could be used by both the crm and res_partner models. Task-2435233 Signed-off-by: Noureddine Bensebia <neb@odoo.com> -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Translation exports now default to the PO/POT format commonly used across Odoo and with Transifex. This reduces repetitive manual selection for contributors and helps keep translation update workflows consistent.
Original PR description
WHY: I'm tired to switch it every time I update pot file in my pull requests 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 website countdown snippet now keeps its content on one line on mobile screens, matching the desktop presentation. This improves readability and gives mobile visitors a more consistent, polished page experience.
Original PR description
PURPOSE The snippet countdown and quotes are cool but could be improved on mobile. SPECIFICATION Current: https://tinyurl.com/y472gmz3 Imp: everything on one line task-2349095 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now edit the subject lines of follow-up email templates, making customer payment reminders easier to tailor. This helps businesses communicate more clearly and consistently when following up on overdue invoices.
Original PR description
Make the subject of the followup email templates editable. Task:2095801
Resolved issues and error corrections
This fixes a shutdown delay that could occur when users had browser sessions waiting for live updates. Odoo now wakes those waiting requests during server shutdown, helping the system stop promptly instead of waiting up to 50 seconds.
Original PR description
Start odoo in threading mode with bus installed. Login in the browser using any internal user. Make sure the browser call the /longpolling/poll uri. While the browser is waiting for a response, stop…
Start odoo in threading mode with bus installed. Login in the browser using any internal user. Make sure the browser call the /longpolling/poll uri. While the browser is waiting for a response, stop the server. The server takes up to 50 seconds to stop. When started in threading mode, a request to /longpolling/poll is served by a casual http thread. It searches for messages enqueued in the bus and returns them. If there are no message for the user in the queue yet, it creates a `threading.Event`, attach it to the user in a shared dictionnary and `wait()` on it with a timeout of 50 secondes (hardcoded value). When the bus thread (the one responsible to listen on the database) receives new messages, it `set()` the events which resume any http thread that was waiting. Because when we stop the server, there is no way to server new requests, there are no way new messages arrive in the bus. All the threads that were waiting for a new message will just wait until the event timeouts which slow down the shutdown of the server. Now we actively `set()` all events in order to resume all those workers when we stop the server. The `ImDispatch.poll` signature has been changed too so it is possible to change (via code) the hardcoded default. The function was using the object referenced by `TIMEOUT` at the time the function was defined, using `timeout None` then `if None: timeout=TIMEOUT` ensure we lookup the variable. 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
The uom must be displayed to the customer in any case. Otherwise portal user couldn't sign their online quote if they couldn't read the uom (ex: a contract of one year or one day) Fine tuning of https://github.com/odoo/odoo/commit/342dd5ffb8281cb5c37fea4fb96db2b570c30122 opw:2411108 Forward-Port-Of: odoo/odoo#65010
Original PR description
The uom must be displayed to the customer in any case. Otherwise portal user couldn't sign their online quote if they couldn't read the uom (ex: a contract of one year or one day) Fine tuning of https://github.com/odoo/odoo/commit/342dd5ffb8281cb5c37fea4fb96db2b570c30122 opw:2411108 Forward-Port-Of: odoo/odoo#65010
This fix ensures that, on mobile, opening the full search view from a Pivot screen no longer leaves a row dropdown stuck open. It improves the reliability of mobile navigation and prevents confusing leftover menus in the interface.
Original PR description
In mobile the Pivot drop down remains open when the user clicks on the
full search view (form Control Panel)
This is due because there is a stop propagation on the full search icon.
Steps to reproduce:
* Open a App with a Pivot view
* Select the Pivot view
* Click on one row to open the drop down
* Click on the Full Search icon ('.o_toggle_searchview_full.fa-filter')
* Click back arrow, drop down is still open => BUG
Task ID: 2439742BEFORE: Odoo tries to unlink and then checks for exceptions AFTER: allow to filter products before starting recursion WHY: this speeds up updating attributes in product.template --- opw-2440417 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#64997
Original PR description
BEFORE: Odoo tries to unlink and then checks for exceptions AFTER: allow to filter products before starting recursion WHY: this speeds up updating attributes in product.template --- opw-2440417 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#64997
The uom must be displayed to the customer in any case. Otherwise a customer couldn't know the modalities of a contract (ex: a contract of one year or one day) Fine tuning of 342dd5f opw:2411108 Forward-Port-Of: odoo/odoo#65037
Original PR description
The uom must be displayed to the customer in any case. Otherwise a customer couldn't know the modalities of a contract (ex: a contract of one year or one day) Fine tuning of 342dd5f opw:2411108 Forward-Port-Of: odoo/odoo#65037
using markAsRead only mark message stored inside the frontend. By using markAllAsRead, we mark all the message regardless of the frontend. task-2426357 Forward-Port-Of: odoo/odoo#64009
Original PR description
using markAsRead only mark message stored inside the frontend. By using markAllAsRead, we mark all the message regardless of the frontend. task-2426357 Forward-Port-Of: odoo/odoo#64009
Before this commit saving a custom snippet inside an email template produced a "cross origin" error related to the combination of the save & reload mechanism with the fact that the email template editor is inside an iframe. After this commit saving a custom snippet inside an email template is not available anymore. Given that fixing the reload problem would be only temporary -while quite complex-, it has been decided to disable the feature until the editor allows for cleaning snippets
Original PR description
Before this commit saving a custom snippet inside an email template produced a "cross origin" error related to the combination of the save & reload mechanism with the fact that the email template editor is inside an iframe. After this commit saving a custom snippet inside an email template is not available anymore. Given that fixing the reload problem would be only temporary -while quite complex-, it has been decided to disable the feature until the editor allows for cleaning snippets without saving them. Decided during task-2374802 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#64922
PURPOSE Fix various tours. SPEC Remove steps from crm and sale tour and improve step selector in project tour. TASK 2444272 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#64835
Original PR description
PURPOSE Fix various tours. SPEC Remove steps from crm and sale tour and improve step selector in project tour. TASK 2444272 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#64835
New module to synchronize Australian payroll with odoo The settings are at the bottom of the accounting section, you need an Australian company to see them. You can setup one api key and the url of the provider as a globale config while activating the integration per company, you will need the business id to do so. Forward-Port-Of: odoo/enterprise#13625
Original PR description
New module to synchronize Australian payroll with odoo The settings are at the bottom of the accounting section, you need an Australian company to see them. You can setup one api key and the url of the provider as a globale config while activating the integration per company, you will need the business id to do so. Forward-Port-Of: odoo/enterprise#13625