Tuesday, January 26, 2021
4 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
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