Daily updates from Odoo
Thursday, July 25, 2019
25 changes · master
New functionality added to Odoo
Event organizers can now schedule SMS messages alongside emails for event communications, including registration confirmations and reminders. This helps reach attendees more reliably by using mobile or phone numbers and keeps sent-message logs for follow-up.
Original PR description
PURPOSE
Allow the user to schedule SMS communication on events
SPECIFICATION
In event.event form view:
* rename tab 'Email Schedule' to 'Communication'
* add a selection field at the beginning of event_mail_ids with label 'Send'
and values 'Email' and 'SMS Text Message' (required with default value
'Email');
* add support of SMS template and SMS sending in event communication;
Add SMS template data
* Name: Event: Registration (see data)
* Name: Event: Reminder (see data)
Improve registration model
* add a mobile field to the attendees form view: https://nimb.ws/p0VvyS
Technically this task uses the newly-introduced API methods allowing to
send and schedule SMS.
MIGRATION
Some notes on migration
* event.registration: new mobile field in addition to phone, may be void;
* event.type.mail and event.mail: new notification_type field. Existing
rows: set value to 'mail'.
LINKS
Task 1922187Enhancements to existing features
Module loading now avoids repeating the same dependency checks when modules share dependencies. This reduces unnecessary processing and helps prevent timeouts in complex module setups.
Original PR description
If you have a module with several dependencies or a complex dependency graph, the system repeats the number of checks of a module. For example: we have 4 modules A, B, C and D, where A depends on B and C, B depends on D and C depends on D. Before this patch, we check once if A is installed, once if B is installed, once if C is installed and twice id D is installed. With this patch, D is checked only once. On this example, the difference is minimal but on worse scenario as explained on the below issue, the processing time was provoking a timeout on test platform https://github.com/odoo/odoo/pull/29779#issuecomment-452821082 Cherry-pick to master of #29779
This improves how Odoo reports automated test failures, making the details appear immediately and closer to the relevant test output. It reduces duplicate or unhelpful log messages, helping developers diagnose issues faster without changing business features.
Original PR description
Righ now, the unittest log system is a little bit blurry. -> Using TextTestResult for almost nothing (implementation needs reduced to minimal in OdooTestRunner -> Using a testStream to transform write on stream in logs and filtering crap added by TextTestResult The proposed solution -> Simplified implementation of runner to keep only what we need -> Use a custom OdooTestResult to log errors Side effetcs (or improvements) ->Traceback are now printed in a single log when test fails, not at the end of the suite This is particularly convenient if a test logs some info when failing, traceback will be display next to it. -> Less 'useless' error logs like 'FAILED'
The manual replenishment source document label can now appear in the user's language, such as Chinese. This improves clarity for international users creating purchase requests from product replenishment.
Original PR description
Description of the issue/feature this PR addresses: Let "Manual Replenishment" translatable. Current behavior before PR: Use the button **Replenish** on product form view. A new Requests for Quotation is created with Source Document set to "Manual Replenishment". Desired behavior after PR is merged: Use the button **Replenish** on product form view. In China, A new Requests for Quotation is created with Source Document set to "手动补给". -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update lets core web templates included by modules be inherited and customized on the server before they are delivered. It makes it easier for Odoo apps and customizations to reuse shared interface pieces consistently, while leaving widget-specific template loading unchanged.
Original PR description
QWeb templates that show up in the 'qweb' key of a module's manifest now support server side inheritance and xpath evaluation QWeb templates that show up in the xmlDependencies of a JS widget are not…
QWeb templates that show up in the 'qweb' key of a module's manifest now support server side inheritance and xpath evaluation QWeb templates that show up in the xmlDependencies of a JS widget are not impacted at all by theses changes, as they are served through the Werkzeug sharedMiddleware A similar syntax than ir.ui.view has been implemented in the QWeb templates - each template must have a root node, whatever tag works - the root node of a template must have a t-name containing the name of the template The name -- without the module's name -- may contain dots pretty much anywhere Though what is recommended is only underscores in template names - if a template is to inherit from a parent, the root node has a t-inherit directive containing either the full name of the template it inherits from which is module_name.template_name or the name of the template, no module name necessary, if the parent template is in the same module - there are 2 modes of inheriting primary: copy the behavior of the parent into the template extension: modifies the parent in place Task: 1999528
The web interface now allows domain field dialogs to receive context from the surrounding screen. This helps dialogs show more relevant options and behave consistently with the user’s current workflow.
Original PR description
Description of the issue/feature this PR addresses: Extends the domain field widget. Current behavior before PR: No context can be passed to the dialog. Desired behavior after PR is merged: Context can be passed to the dialog. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Events app now uses the word “talks” instead of “tracks” across customer-facing screens and related event communications. This makes event terminology clearer and more consistent for attendees, organizers, and marketing users.
Original PR description
**Description of the issue/feature this PR addresses**: - Task: https://www.odoo.com/web#id=1952957&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 - Pad: https://pad.odoo.com/p/r.6e8fcc437c577d90cd352ed51da4cdd0 **Description:** -There will be no mention of "tracks" anywhere in the front end. instead, it'll be known as "tracks". -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Websites can now use their own logo independently from the company logo. This lets businesses tailor each website’s branding without changing the main company identity across Odoo.
Original PR description
Task: https://www.odoo.com/web#id=1968099&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720
Blog post SEO information can now be viewed and edited directly from the backend, including when managing multiple posts. This reduces the time needed to update search-related content because users no longer need to open each blog post on the website frontend or rely on CSV imports.
Original PR description
Description of the issue/feature this PR addresses: Allow to easily and quickly edit SEO values for blog posts. Current behavior before PR: Right now there is no quick way to edit the SEO of a blog post or multiple blog posts from the backend. You can only do it through the frontend by opening the blog(s) and then the SEO dialog or by importing through CSV. Desired behavior after PR is merged: You're able to quickly view and edit the SEO fields of blog posts through the backend. This will take a lot less time. Note: I've also fixed the typo in a group name and removed the `invisible` element as otherwise the group has no purpose at all. Example:  -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Ogone payment pages can now better match the website’s theme by using the site’s colors, fonts, sizing, and button styles. This gives customers a more consistent checkout experience and lets businesses enable the custom design from the payment provider settings.
Original PR description
Task: https://www.odoo.com/web?#id=1924721&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.179c817e5dab540cad3e9717013facd3 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
Resolved issues and error corrections
Scrapping products from completed receipts now starts from the received stock location and creates the related scrap move in draft first. This prevents duplicate inventory valuation entries when the scrap is processed, improving accuracy for warehouse and accounting operations.
Original PR description
In the receipts, you can only scrap after the reception. This implies that the source location of the scrap move is the destination location of the picking. Create the scrap move as draft, else in the receipt it used the state of the picking (done) and calling _action_done again resulted in double valuation layers task-2042399 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
This fixes how file size unit labels are prepared for translation in the web interface. It prevents punctuation used as an internal separator from being translated incorrectly, helping file sizes display consistently across languages.
Original PR description
Before this commit, the string containing all size units for binary fields was comma separated. The problem with this is that comma got also translated into the language's specific comma-like, whereas in this case it is obviously a technical separator which shouldn't be translated After this commit, we separate unit size with pipes (|), hoping that this character - is easy to find on any keyboard - has no language specific equivalent OPW 2041975 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
This fixes a problem that could appear when upgrading the core Base module, such as during migrations from older Odoo versions to master. The change helps make upgrades more reliable and reduces the risk of migration interruptions.
Original PR description
The bug triggers during an upgrade of base (tested while migrating from 12.0 to master). Introduced at 074074e5704601b5f74b81b9ca3eb870a4f23482
This fixes how Odoo sends actions to connected scales through the IoT hardware drivers. Scale actions can now receive structured parameters, making device commands more reliable and easier to extend.
Original PR description
Scale action took a string as argument. It now takes a dict so parameters can be passed to action methods. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixes wishlist and cart animations so they target the correct navigation bar when shoppers scroll and a floating menu appears. This prevents missing wishlist buttons and misdirected animations, creating a smoother shopping experience.
Original PR description
* = website_sale, website_sale_wishlist The wishlist animation was not handling the floating navbar and always refering to the fixed one. Now the animation will target the right navbar if we scroll down. When the navbar is duplicated, the ids of the tags were kept wich is wrong and was producoing bugs such as wishlist button not showing up on the floating navbar on the first product added to the wishlist and the first issue. Now the id is removed from the clone and never used in JS code. It's only purpose is for the xpath of the wishlist button. When a product is added to the cart from the wishlist and the floating navbar is displayed, the product is hidden before the animation is ompleted. This changes the height of the page and the animation goes to the middle of the page instead of the button. This is now fixed too. task-2002122
This fixes a small spelling mistake in the Slovenia localization module's setup information. The correction helps the system read the module version properly and avoids confusion during module management.
Original PR description
Description of the issue/feature this PR addresses: fixes typo in manifest key Current behavior before PR: Manifest key is `versiom` Desired behavior after PR is merged: Manifest key is `version` -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Invoices created outside the standard screen, such as through demo data or imports, now automatically receive the correct taxes and units of measure on their lines. This helps prevent incorrect invoice details and reduces manual corrections for accounting teams.
Original PR description
With this change the account invoice line taxes and uom will be properly computed when creating an invoice from demo data and import functionality. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix moves the scale device script back to the correct point-of-sale IoT asset area. It helps ensure connected weighing scales load properly in POS setups while keeping the change limited and internal.
Original PR description
The scale.js file was declared in the wrong template. It was moved back where other iot device assets are declared until a proper assets.xml file is created.
The point-of-sale IoT scale integration now sends information in a more flexible format when triggering scale actions. This fixes an issue that limited what data could be passed, helping scale-related workflows behave correctly as they evolve.
Original PR description
Scale action took a string as argument. It now takes a dict so parameters can be passed to action methods.
The Indian payroll demo data has been updated so it installs correctly after a required setup field was introduced. This helps keep demo and testing environments usable for payroll scenarios without manual fixes.
Original PR description
Demo data were not installing because type_id is now required
This update adjusts an internal automated test for rental sales so it no longer depends on items appearing in a specific order. It helps keep quality checks stable and reduces false test failures without changing customer-facing behavior.
Original PR description
In some case, order can change making the test indeterminist This fix ensures that order doesn't matter
This fix removes duplicate sidebar templates in Odoo Studio. It helps keep the Studio interface definitions clean and reduces the risk of inconsistent behavior or maintenance issues.
Original PR description
remove the duplicate template: * web_studio.Sidebar.Warning.Groups, * web_studio.Sidebar.Toolbox Task: 1999528
Incoming VoIP calls from saved contacts now display the partner's name instead of only their phone number. This makes it easier for users to recognize callers and handle calls more efficiently.
Original PR description
Set a phone number on a partner, make that partner call Odoo, his phone number is shown instead of his name. opw-2034004
Documentation and clarification updates
This pull request adds a corporate Contributor License Agreement form for BADEP to the repository documentation. It supports legal compliance for contributions and does not affect product functionality or end users.
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
This pull request updates the contributor license agreement record for an individual contributor by adding another email address. This helps keep legal contribution records accurate and ensures the contributor can be properly associated with their work.
Original PR description
Description of the issue/feature this PR addresses: Update my email -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr