Daily updates from Odoo
Navigate
Branch
Tuesday, March 3, 2020
26 changes
Enhancements to existing features
This update refines several website snippets so pages look cleaner and behave more consistently out of the box. It improves default layouts, spacing, button styling, image handling, and carousel indicators, making it easier for users to build polished website pages.
OAuth login provider settings now include the missing style field on the configuration form, making it easier to control how providers appear. Providers can also be ordered using their existing sequence setting, helping businesses choose the order shown on the login page.
Original PR description
Field `css_class` was not added on Views. In this commit, we add this field on form view. 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
Sales order lines for event tickets now keep their unit of measure locked so users cannot change it to an unsupported value. This prevents confusing or incorrect ticket sales processing and keeps event sales data consistent.
Original PR description
Specification: -Updating the uom of Sales Order Lines related to an event (selling event tickets) doesn't have any sense and wouldn't work correctly if changed. Task-2178371 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
Subscription templates now display their code field, with a helpful tooltip explaining its use. This makes it easier for users to identify or sequence subscriptions consistently when working with templates.
Original PR description
purpose of this commit is code field can be usefull for a sequence of subscription. task: 2184022
Resolved issues and error corrections
This fix ensures stock movements keep the same operation type consistently during processing. It helps prevent mismatched warehouse transfer behavior and reduces the risk of incorrect stock handling.
Original PR description
Description of the issue/feature this PR addresses: Normalise picking_type @sle-odoo -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix ensures systray items in the web interface are properly recognized as attached to the page. It prevents embedded interface components from missing their setup step, so their interactions and event handling work as expected.
Original PR description
Currently, the method `on_attach_callback` is never called on any Widget in the systray. Calling `on_attach_callback` is required if any systray widget uses an OWL component via the ComponentWrapper. Without the callback, the component is never considered mounted to the DOM and no event handler is triggered. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an issue where the timesheet timer option could be incorrectly enabled or disabled when creating a project. The timer setting now consistently follows whether timesheets are allowed, helping avoid confusing project setup behavior.
Original PR description
The 'allow_timesheet_timer' field should not have a default value as it is computed according to the 'allow_timesheets' field value. Some tests have been added to check the coherency between 'allow_timesheets' and 'allow_timesheet_timer' fields, at project creation and update. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes how timesheet timer availability is set when creating Field Service and Helpdesk-related projects. The timer setting now follows whether timesheets are allowed, helping teams avoid incorrect timer behavior and keeping project setup consistent.
Original PR description
The way to compute the 'allow_timesheet_timer' field was wrong. This field strongly depends on the 'allow_timesheets' field value and not directly on the 'is_fsm' field value. That's why, now: - 'allow_timesheets' is computed according to the 'is_fsm' field value. - 'allow_timesheet_timer' is computed according to the 'allow_timesheets' field value only. -- I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr](www.odoo.com/submit-pr)
Fixed an issue where some items in the top navigation systray could fail to fully activate after appearing on the page. This ensures interactive controls in that area respond properly, improving reliability for users without changing their workflow.
Original PR description
Currently, the method `on_attach_callback` is never called on any Widget in the systray. Calling `on_attach_callback` is required if any systray widget uses an OWL component via the ComponentWrapper. Without the callback, the component is never considered mounted to the DOM and no event handler is triggered.
Customers now see a Close Subscription button in the portal when their subscription template allows customer closure. This fixes a missing action so eligible customers can end subscriptions without needing staff assistance.
Original PR description
Purpose Even when the template is selected as Closable by customer, Close Subscription button should appear on front end. Task-2178367
Code cleanup and technical improvements
A helper for safely handling file types is being moved into Odoo's shared tools so it can be reused beyond the Documents app. This is an internal change that supports future improvements without changing day-to-day user workflows.
Original PR description
This method will be used later in other module(s) than Document Task : 1960733 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
A helper used to make file types safer has been moved from the Documents app into a shared Odoo toolkit. This prepares the functionality for reuse by other apps, including Community edition modules, without changing day-to-day user workflows.
Original PR description
This method will be used later in other module(s) than Document. Especially in Community version ones. Task : 1960733
Miscellaneous changes
Since 12.0, the links on the login forms are no longer next to the main button, but under it. This commit reflects this change in the reset password form, which has not been updated yet. Forward-Port-Of: odoo/odoo#46723
Original PR description
Since 12.0, the links on the login forms are no longer next to the main button, but under it. This commit reflects this change in the reset password form, which has not been updated yet. Forward-Port-Of: odoo/odoo#46723
/!\ This commit is a manual forward-port of two PR targetting originally 11.0: #40442 and its fix / partial revert #41042. /!\ Purpose of this commit is to check all recipients of incoming emails when trying to determine the route to apply. Notably * an incoming email should be considered as a write to catchall only if all recipients are catchall. Catchall + a valid alias should take the alias into account; * an incoming email sent to the bounce alias should be considered
Original PR description
/!\ This commit is a manual forward-port of two PR targetting originally 11.0: #40442 and its fix / partial revert #41042. /!\ Purpose of this commit is to check all recipients of incoming emails…
/!\ This commit is a manual forward-port of two PR targetting originally
11.0: #40442 and its fix / partial revert #41042. /!\
Purpose of this commit is to check all recipients of incoming emails when
trying to determine the route to apply. Notably
* an incoming email should be considered as a write to catchall only if all
recipients are catchall. Catchall + a valid alias should take the alias
into account;
* an incoming email sent to the bounce alias should be considered as a bounce
even if another valid alias is in recipients and whatever the order. Indeed
it indicates an issue and bounce is considered as more important;
* forward to an alias linked to another model should check all recipients
and not only the first one. Otherwise reply_alias, forward_alias is
considered as a reply whereas it should be considered as a forward when
considering all recipients;
Tests are added according to those specifications.
Please see original PRs for more details about the content, the comments
done on it and the various discussions.
PR #40821
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#46764Because of the event propagating to an option's parent, a snippet option requesting a uservalue widget would also get back the corresponding widgets on the parent snippetEditor, this has the potential to cause unforeseen problems. This commit fixes that by stopping the event's propagation. Forward-Port-Of: odoo/odoo#46707
Original PR description
Because of the event propagating to an option's parent, a snippet option requesting a uservalue widget would also get back the corresponding widgets on the parent snippetEditor, this has the potential to cause unforeseen problems. This commit fixes that by stopping the event's propagation. Forward-Port-Of: odoo/odoo#46707
The hidden fields containing form infos have options activated on them because of the class s_website_form_field. When a saved snippet is dropped the snippet editor tries to activate them. They should not have any options. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46513
Original PR description
The hidden fields containing form infos have options activated on them because of the class s_website_form_field. When a saved snippet is dropped the snippet editor tries to activate them. They should not have any options. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46513
Before this commit, the amount currency could be wrapped on a second line (on mobile). To fix this, we had to find a way to have more space: - Buttons are now displayed at the top (mobile only). - Amounts can grow (col-auto) and the other column will take the space left (col) and add "..." when there is not enough space. (mobile + desktop) We also had to remove a button from a div tag in order to display the buttons next to each other on mobile (buttons are "inline-block" but di
Original PR description
Before this commit, the amount currency could be wrapped on a second line (on mobile). To fix this, we had to find a way to have more space: - Buttons are now displayed at the top (mobile only). - Amounts can grow (col-auto) and the other column will take the space left (col) and add "..." when there is not enough space. (mobile + desktop) We also had to remove a button from a div tag in order to display the buttons next to each other on mobile (buttons are "inline-block" but div is a "block"). The main flow tour has been adapted accordingly and the typo has been fixed too... Task-ID: 2184243 Forward-Port-Of: odoo/odoo#46589 Forward-Port-Of: odoo/odoo#46463
… the tax Before this commit, when two lines belonging to a period that is already closed a cash basis entry is created at the present date. There are localizations that could not allow creating the cash basis entry in a date other than the maximum between the Journal Items being reconciled. Now, the localizations are able to override and chose the date without having to override the whole 'create_tax_cash_basis_entry' method. opw-2195016 Forward-Port-Of: odoo/odoo#46570 Forward-Po
Original PR description
… the tax Before this commit, when two lines belonging to a period that is already closed a cash basis entry is created at the present date. There are localizations that could not allow creating the cash basis entry in a date other than the maximum between the Journal Items being reconciled. Now, the localizations are able to override and chose the date without having to override the whole 'create_tax_cash_basis_entry' method. opw-2195016 Forward-Port-Of: odoo/odoo#46570 Forward-Port-Of: odoo/odoo#46434
Finetuning of https://github.com/odoo/enterprise/commit/b6e6347c3b06560f4f617b918dd816fdc645b38a, only the returned lots were shown on the invoice. Now, SN are shown after pickup (and not after return only). Forward-Port-Of: odoo/enterprise#8993
Original PR description
Finetuning of https://github.com/odoo/enterprise/commit/b6e6347c3b06560f4f617b918dd816fdc645b38a, only the returned lots were shown on the invoice. Now, SN are shown after pickup (and not after return only). Forward-Port-Of: odoo/enterprise#8993
Because rental stock moves don't happen through pickings, their content wasn't displayed on the invoice report, even when the feature "Display Lot/SN on invoices" was enabled. opw-2207885 Forward-Port-Of: odoo/enterprise#8971
Original PR description
Because rental stock moves don't happen through pickings, their content wasn't displayed on the invoice report, even when the feature "Display Lot/SN on invoices" was enabled. opw-2207885 Forward-Port-Of: odoo/enterprise#8971
Before this commit: For an incoming call, only the phone number was shown, even if the contact is registered as a contact. The contact wasn't found because the phone number is used instead of the sanitized one. For e.g : 0412345678 call and a contact using this phone number is searched instead of +32412345678 (which is the value stored in the db) Note that I am not sure that `inviteSession.remoteIdentity.uri.type` is the mobile prefix of the incoming call. But it seems to be. OPW-218777
Original PR description
Before this commit: For an incoming call, only the phone number was shown, even if the contact is registered as a contact. The contact wasn't found because the phone number is used instead of the sanitized one. For e.g : 0412345678 call and a contact using this phone number is searched instead of +32412345678 (which is the value stored in the db) Note that I am not sure that `inviteSession.remoteIdentity.uri.type` is the mobile prefix of the incoming call. But it seems to be. OPW-2187771 Forward-Port-Of: odoo/enterprise#8713
Task [2198748](https://www.odoo.com/web?#id=2198748&action=333&active_id=967&model=project.task&view_type=form&cids=1&menu_id=4720) The functionality was removed by https://github.com/odoo/enterprise/pull/4379 because the functionality was buggy, laggy, and since we didn't get a lot of tickets about it, we thought it wasn't used much. As it turns out, it was. This commit reintroduces the functionality while improving the performances and hopefully removing bugs. Forward-Port-Of: odoo/
Original PR description
Task [2198748](https://www.odoo.com/web?#id=2198748&action=333&active_id=967&model=project.task&view_type=form&cids=1&menu_id=4720) The functionality was removed by https://github.com/odoo/enterprise/pull/4379 because the functionality was buggy, laggy, and since we didn't get a lot of tickets about it, we thought it wasn't used much. As it turns out, it was. This commit reintroduces the functionality while improving the performances and hopefully removing bugs. Forward-Port-Of: odoo/enterprise#8839 Forward-Port-Of: odoo/enterprise#8496
Purpose ======= Most of our customers are SMEs with a handful employees. For these people, it is practical to have a list of all employees always available. However, this could cause significant performance issues for big databases with a lot of employees. In that case, the current group_expand we have would be perfect, as it only shows the essential information. Specification ============= If there are less than 20 employees (or any other number that suits you best), display
Original PR description
Purpose ======= Most of our customers are SMEs with a handful employees. For these people, it is practical to have a list of all employees always available. However, this could cause significant performance issues for big databases with a lot of employees. In that case, the current group_expand we have would be perfect, as it only shows the essential information. Specification ============= If there are less than 20 employees (or any other number that suits you best), display all employees in the Gantt view If there are more than 20 employees, only display the employees to whom a shift was assigned in the past 30 days (current group_expand we have in master) TaskID: 2184024 Forward-Port-Of: odoo/enterprise#8961 Forward-Port-Of: odoo/enterprise#8073
Addapt existing use of website_form hidden field to it's fix. Related to: https://github.com/odoo/odoo/pull/46513 Forward-Port-Of: odoo/enterprise#8873
Original PR description
Addapt existing use of website_form hidden field to it's fix. Related to: https://github.com/odoo/odoo/pull/46513 Forward-Port-Of: odoo/enterprise#8873
Before this commit, the amount currency could be wrapped on a second line (on mobile). To fix this, we had to find a way to have more space: - Buttons are now displayed at the top (mobile only). - Amounts can grow (col-auto) and the other column will take the space left (col) and add "..." when there is not enough space. (mobile + desktop) Task-ID: 2184243 Forward-Port-Of: odoo/enterprise#8895 Forward-Port-Of: odoo/enterprise#8858
Original PR description
Before this commit, the amount currency could be wrapped on a second line (on mobile). To fix this, we had to find a way to have more space: - Buttons are now displayed at the top (mobile only). - Amounts can grow (col-auto) and the other column will take the space left (col) and add "..." when there is not enough space. (mobile + desktop) Task-ID: 2184243 Forward-Port-Of: odoo/enterprise#8895 Forward-Port-Of: odoo/enterprise#8858
Before this commit: If we got to view Schedule by Role, and we show list view, there are a traceback. After this commit: No more traceback task ID 2206454 Forward-Port-Of: odoo/enterprise#8926
Original PR description
Before this commit: If we got to view Schedule by Role, and we show list view, there are a traceback. After this commit: No more traceback task ID 2206454 Forward-Port-Of: odoo/enterprise#8926