Thursday, July 8, 2021
29 changes · master
Enhancements to existing features
The website editor now shows the scroll-down button option only when a section is set to full height. This keeps editing choices clearer and avoids offering a button setting when it would not apply.
Original PR description
- Show "scroll down button" only when height is 100%. - Make the "scroll down button" a child of "height" option. task-2471323 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Accounting settings screen now gives the chart template field more room to display longer values. This makes configuration easier to read and reduces wasted space in the settings layout.
Original PR description
Lots of unused space and the values can be long sometimes [task-2526878](https://www.odoo.com/web#cids=1&id=2526878&model=project.task) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update renames an internal website setup field to better reflect how website feature suggestions are chosen. It clarifies that preselected options now consider both the type of website and its intended purpose, helping keep configuration logic aligned with the business flow.
Original PR description
Rename field website_type_preselection to website_config_preselection since feature preselection is not only based on website type anymore but also on website purpose. task-2518565 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 revert button in grouped accounting move lines now uses an undo icon instead of a refresh icon. This makes the action easier to recognize and aligns it with similar banking screens, reducing confusion for users.
Original PR description
The current icon used by the revert button on account.move.lines group by view is a refresh icon. Change it by an undo icon like on the bank statement lines. Task id #2585445 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website setup configuration now uses a broader field name that better reflects how options are preselected. This keeps the system aligned with the current setup flow, where choices depend on both website type and purpose.
Original PR description
Rename field website_type_preselection to website_config_preselection since feature preselection is not only based on website type anymore but also on website purpose. task-2518565
The asset management screens now provide clearer tooltip guidance for the proration setting. This helps users better understand how asset depreciation timing is calculated, reducing confusion during asset setup.
Original PR description
[task-2534565](https://www.odoo.com/web#id=2534565&model=project.task)
Helpdesk-related accounting reversals now automatically use the same journal type as the original accounting entry. This prevents errors when creating reversals and keeps financial records consistent with the source transaction.
Original PR description
"journal_id" is now required on move reversals. Add move ids to context to set default journal in view Task: 2497529 community PR: https://github.com/odoo/odoo/pull/72431
The Belgian payroll CP category field is now hidden on job forms for companies outside Belgium, keeping HR screens cleaner and more relevant. Referral-related job listings continue to respect the intended sequence order when the referral app is installed.
Original PR description
Hide cp category in the hr.job form view outside of belgian companies Task ID: 2581595
Resolved issues and error corrections
This fixes a display problem in the email template preview where a referenced field could collapse to zero width and become hard to read. Users reviewing mail templates will now see the related field properly, making template previews clearer and more reliable.
Original PR description
The field resource_ref in the template preview was of `width: 0!important` because of a the class `o_row` added when the options `model_field` was not provided. This fix provides the name of the field (`model_id`) to the option. 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
This release brings same small fixes/improvements. Github release: https://github.com/odoo/owl/releases/tag/v1.3.2 Release notes: config: change debug mode warning to info fix: add support for callable expression in event handler (for example, t-on-click="some.function") fix: allow specific props to override generic props (in t-props) fix: add support for short object description in inline expressions: { hey } fix: add support for t-att-value on <textarea/> and <select/> fix: slots
Original PR description
This release brings same small fixes/improvements. Github release: https://github.com/odoo/owl/releases/tag/v1.3.2 Release notes: config: change debug mode warning to info fix: add support for…
This release brings same small fixes/improvements.
Github release: https://github.com/odoo/owl/releases/tag/v1.3.2
Release notes:
config: change debug mode warning to info
fix: add support for callable expression in event handler (for example, t-on-click="some.function")
fix: allow specific props to override generic props (in t-props)
fix: add support for short object description in inline expressions: { hey }
fix: add support for t-att-value on <textarea/> and <select/>
fix: slots: issue with scoping in nested loops
fix: slots: default slot is not lost in some cases
fix: do not shadow an error in case the finalizing code fails
imp: qweb: allow multiple class in class attribute object notation: t-att-class="{'a b': value}"
imp: better detection for dynamic component change (less need for t-key)
fix: router: allow querystrings in path
fix: qweb: add support for template strings
fix: qweb: make sure nodes with t-transition are removed in all cases
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#73277This fixes an issue where users could not open or use status selection dropdowns directly from list views. The dropdown now displays properly, and choosing an option no longer accidentally opens or edits the full record.
Original PR description
currently, when clicking on an editable state_selection widget in listview, the dropdown is not displayed. this is happening because overflow of cell was hidden. after this commit, now when clicking on an editable state_selection widget in listview, the dropdown is displayed. change overflow to visible. also have to stop event to propagate when select option from drop down is not so formview will for record will open. Task - 2485883 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 fix prevents employees and managers from choosing time off types that are no longer valid or have expired when creating leave or allocation requests. It helps avoid incorrect requests and reduces follow-up corrections by keeping unavailable options out of the selection list.
Original PR description
Previously the domain in the view for the leave request didn't check for the time off type validity, this fix aims to remove that possibility. Also prevents from selecting expired time off types in allocation requests. Task ID: 2578150
The accounting reports test setup was adjusted to follow the newer rule that journals must be posted before they are archived. This keeps automated checks aligned with current accounting behavior and helps prevent false test failures.
Original PR description
It is not allowed to post in an archived journal anymore. [task-2516060](https://www.odoo.com/web#id=2516060&model=project.task) Related: https://github.com/odoo/odoo/pull/71851
…tive quantity ticket: 2585188 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#73290 Forward-Port-Of: odoo/odoo#72924
Original PR description
…tive quantity ticket: 2585188 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#73290 Forward-Port-Of: odoo/odoo#72924
Before this commit, you can provide arbitrary url for redirect. Now, we always return a relative url, since this method should be only called from a page on your current website, their are no reason to let redirect to another domain. 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#73356 Forwa
Original PR description
Before this commit, you can provide arbitrary url for redirect. Now, we always return a relative url, since this method should be only called from a page on your current website, their are no reason to let redirect to another domain. 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#73356 Forward-Port-Of: odoo/odoo#72848
This pull request contains early work on how web client actions are controlled and served. It appears to be a proof of concept, so the business impact is likely limited until the implementation is completed and clarified.
Original PR description
POC
When viewing an order in the order management screen that has customer with fiscal position, the calculation of prices is based on the fiscal position of the currently active order. This commit fixes the issue by properly specifying the order in the calculation of taxes based on the order's customer and/or fiscal position. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#71904
Original PR description
When viewing an order in the order management screen that has customer with fiscal position, the calculation of prices is based on the fiscal position of the currently active order. This commit fixes the issue by properly specifying the order in the calculation of taxes based on the order's customer and/or fiscal position. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#71904
before this commit, the optional field's dropdown displays outside of the form view when columns are expanded. after this commit, the optional field's dropdown should always be positioned on the right side of the list, just below the dropdown icon. TaskID-2510187 Forward-Port-Of: odoo/odoo#69727
Original PR description
before this commit, the optional field's dropdown displays outside of the form view when columns are expanded. after this commit, the optional field's dropdown should always be positioned on the right side of the list, just below the dropdown icon. TaskID-2510187 Forward-Port-Of: odoo/odoo#69727
l10n_eu_service has been modified in order to follow the new OSS regulation. We now auto-generate the mapping instead of relying on a wizard. Databases that were already using the module will still see the button to open this wizard, unless they upgrade the module. Wit this, we add an error message in case they try to do so, asking them to update the module, so that they can use the new OSS mapping. Forward-Port-Of: odoo/odoo#73126
Original PR description
l10n_eu_service has been modified in order to follow the new OSS regulation. We now auto-generate the mapping instead of relying on a wizard. Databases that were already using the module will still see the button to open this wizard, unless they upgrade the module. Wit this, we add an error message in case they try to do so, asking them to update the module, so that they can use the new OSS mapping. Forward-Port-Of: odoo/odoo#73126
Github release: https://github.com/odoo/owl/releases/tag/v1.4.3 Release notes: - fix: another scoping issue with t-slots 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#73410
Original PR description
Github release: https://github.com/odoo/owl/releases/tag/v1.4.3 Release notes: - fix: another scoping issue with t-slots 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#73410
When starting a drag and drop of a snippet, a loading effect on the editor panel was performed for the whole duration of the drag. Worse: even if the drop was done immediately, the loading effect still occurred for 400ms as it was only marked as finished after the scroll to the dropped snippet. The loading effect addition was in fact a side-effect of first disabling all editor overlays at the start of the drag... but that action was in fact entirely unnecessary because this is not possi
Original PR description
When starting a drag and drop of a snippet, a loading effect on the editor panel was performed for the whole duration of the drag. Worse: even if the drop was done immediately, the loading effect still occurred for 400ms as it was only marked as finished after the scroll to the dropped snippet. The loading effect addition was in fact a side-effect of first disabling all editor overlays at the start of the drag... but that action was in fact entirely unnecessary because this is not possible to have any overlay enabled when the snippet panel is opened (because opening it already disables all editor overlays and enabling an overlay forces the editor to switch out of the blocks panel). Forward-Port-Of: odoo/odoo#73409
### [FIX] core: in onchange, assign inherited fields that have changed This allows `onchange` to recompute fields that depend on the inherited field that has changed. The use-case we have is a model that inherits from 'account.move'. On its form view, setting the (inherited) journal field does not recompute the (inherited) company field. When the field `journal_id` is modified, the `onchange` should: - assign the new value to `move_id.journal_id` (*) - recompute `move_id.company_id`
Original PR description
### [FIX] core: in onchange, assign inherited fields that have changed This allows `onchange` to recompute fields that depend on the inherited field that has changed. The use-case we have is a model…
### [FIX] core: in onchange, assign inherited fields that have changed This allows `onchange` to recompute fields that depend on the inherited field that has changed. The use-case we have is a model that inherits from 'account.move'. On its form view, setting the (inherited) journal field does not recompute the (inherited) company field. When the field `journal_id` is modified, the `onchange` should: - assign the new value to `move_id.journal_id` (*) - recompute `move_id.company_id` (`related='journal_id.company_id'`) - recompute `company_id` This adds the missing part (*). ### [FIX] core: in onchange, do not force delegate fields to False The use-case is when a "parent" field is put on the form view, as a readonly field, and we create a new record. Before the fix, the fields that depend on the parent record are always False, until the record is actually created. Those commits actually fix up https://github.com/odoo/odoo/pull/64359, and re-introduce behaviors that were lost. Forward-Port-Of: odoo/odoo#73364 Forward-Port-Of: odoo/odoo#72855
Before this commit 308 redirections could be configured with a malformed route which made the routing fail. After this commit 308 redirections validation makes sure all parameters of URL from appear in URL to and no other parameter appears. Rebased to ~14.0~ 13.0 from https://github.com/odoo/odoo/pull/68030 task-2451780 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the
Original PR description
Before this commit 308 redirections could be configured with a malformed route which made the routing fail. After this commit 308 redirections validation makes sure all parameters of URL from appear in URL to and no other parameter appears. Rebased to ~14.0~ 13.0 from https://github.com/odoo/odoo/pull/68030 task-2451780 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#73202
This filter was not working anymore since 146e972d65d182 Indeed, NULL values shouldn't be tested using an equality operator like `!=`. It doesn't work, `IS NOT NULL` should be used instead. opw-2507449 Forward-Port-Of: odoo/enterprise#19525
Original PR description
This filter was not working anymore since 146e972d65d182 Indeed, NULL values shouldn't be tested using an equality operator like `!=`. It doesn't work, `IS NOT NULL` should be used instead. opw-2507449 Forward-Port-Of: odoo/enterprise#19525
Before this commit, when we only install project_enterprise module, the `employee_id` field is not defined in the `res.users` model. So, we have a traceback since we check if the user has an employee_id to take his resource calendar in `write` and `_calculate_planned_dates` methods in `project.project` model. This commit removes this check and gives the calendar of user if it is set otherwise we take the default calendar set in the current company. Related task: 2387984 Related PR: #
Original PR description
Before this commit, when we only install project_enterprise module, the `employee_id` field is not defined in the `res.users` model. So, we have a traceback since we check if the user has an employee_id to take his resource calendar in `write` and `_calculate_planned_dates` methods in `project.project` model. This commit removes this check and gives the calendar of user if it is set otherwise we take the default calendar set in the current company. Related task: 2387984 Related PR: #16627 X-original-commit: 52536bf8bb Forward-Port-Of: odoo/enterprise#19424
The /published_posts endpoint offers the same features and capabilities as the /feed endpoint except that it does not contain posts made by other people on your page. Which is exactly what we want, since we can't get information about other people's posts. Fetching posts from other people can apparently also cause issues with Facebook security detection. In addition, we only fetch posts metrics if the posts are of our own page (and avoid doing it for the '/tagged' endpoint), as this
Original PR description
The /published_posts endpoint offers the same features and capabilities as the /feed endpoint except that it does not contain posts made by other people on your page. Which is exactly what we want, since we can't get information about other people's posts. Fetching posts from other people can apparently also cause issues with Facebook security detection. In addition, we only fetch posts metrics if the posts are of our own page (and avoid doing it for the '/tagged' endpoint), as this may also cause issues with Facebook security detection (trying to access post metrics that you don't own). LINKS Task-2587257 Support Ticket-2541898 Forward-Port-Of: odoo/enterprise#19513 Forward-Port-Of: odoo/enterprise#19486
Before this commit, the label of unmapped records is displayed below the prefix, because of the 'div' class used in the XML. This commit replaces the 'div' tag with the 'span' tag. so, the label of the unmapped records is displayed aligned with their count prefix. TaskID-2452694 Forward-Port-Of: odoo/enterprise#16110
Original PR description
Before this commit, the label of unmapped records is displayed below the prefix, because of the 'div' class used in the XML. This commit replaces the 'div' tag with the 'span' tag. so, the label of the unmapped records is displayed aligned with their count prefix. TaskID-2452694 Forward-Port-Of: odoo/enterprise#16110
When viewing an order in the order management screen that has customer with fiscal position, the calculation of prices is based on the fiscal position of the currently active order. This commit fixes the issue by properly specifying the order in the calculation of taxes based on the order's customer and/or fiscal position. Related to: https://github.com/odoo/odoo/pull/71904 Forward-Port-Of: odoo/enterprise#18872
Original PR description
When viewing an order in the order management screen that has customer with fiscal position, the calculation of prices is based on the fiscal position of the currently active order. This commit fixes the issue by properly specifying the order in the calculation of taxes based on the order's customer and/or fiscal position. Related to: https://github.com/odoo/odoo/pull/71904 Forward-Port-Of: odoo/enterprise#18872
Steps to reproduce (in the mobile app): - Open Contacts - Create a new partner - Before saving it, click on "Add to Mobile" => traceback opw-2467428 Forward-Port-Of: odoo/enterprise#19488
Original PR description
Steps to reproduce (in the mobile app): - Open Contacts - Create a new partner - Before saving it, click on "Add to Mobile" => traceback opw-2467428 Forward-Port-Of: odoo/enterprise#19488