Daily updates from Odoo
Navigate
Branch
Wednesday, January 9, 2019
13 changes
Enhancements to existing features
Website editors can now create and link directly to anchors on a page, including default top and bottom locations and existing anchors. This makes it easier for visitors to jump to relevant sections and improves navigation on longer pages.
Original PR description
* portal, web_editor
Anchor Link:
- Some visual improvements of the link dialog.
- New 'Page Anchor' field.
- System by default: top and bottom.
- Shows existing anchors.
Creation of the anchor:
- New option 'Anchor Name' to be able to create an anchor.
task-1913458The model field selector now shows a search box by default, making it easier for users to quickly find the fields they need. This also improves the domain field widget, reducing time spent scrolling through long field lists.
Original PR description
The option `showSearchInput`, which is used on the model field selector to display a search input that filters the displayed fields, is not set by default. This includes the model field selector instantiated in the `domain` field widget.
This update makes the gamification goal view clearer by correcting an oversized layout element that pushed content out of place. It also adds clearer internal labels to key parts of the view, making future customizations easier and less fragile.
Original PR description
Description of the issue/feature this PR addresses: Improve extendability of the view and improve the layout Current behavior before PR: The layout has an element with a colspan of `4` which pushes the whole group out of its size:  Desired behavior after PR is merged: The view is rendered more clear and while I was already in the view I added name elements around the most important attributes for easier and cleaner `xpath` expressions. New view:  -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Sales orders for kits now show availability based on the stock of their required components, so users get more realistic warnings before confirming orders. Delivered quantities are also calculated from the components already processed, improving accuracy for partial deliveries, backorders, returns, nested kits, and mixed units of measure.
Original PR description
**Before this PR:** - The quantities available when a kit was ordered was 0 even if enough components were available - The quantities delivered when a kit was ordered were correct only if all move…
**Before this PR:**
- The quantities available when a kit was ordered was 0 even if enough components were available
- The quantities delivered when a kit was ordered were correct only if all move from the picking of its sale order were done. So the quantities delivered were correct only if all components were fully delivered.
**After this PR:**
- The number of kits available is computed based on the quantities available of the components needed to make the kit.
- The number of kits delivered is computed based on how many kits it's possible to make with the components already processed.
- Some test case are added the check the flows when kits are ordered.
Those test case make sure that:
* Delivered quantities are accurate if :
- kits in kit
- backorders are made
- returns are made
- returns of returns are made
- Multiple differents UoMs are setted on the components of a kit
* Available quantities are accurate if:
- Kits in kit
- Multiple differents UoMs are setted on the components of a kit
TaskID : 1915370Forum users can now see how many people marked a question as a favourite on question pages and profile tabs. This improves transparency and makes forum engagement signals easier to understand, similar to other large Q&A communities.
Original PR description
Description of the issue/feature this PR addresses: Show the missing favourites counter Current behavior before PR: There is no way to see the amount of favorites set in the forum. Desired behavior…
Description of the issue/feature this PR addresses: Show the missing favourites counter Current behavior before PR: There is no way to see the amount of favorites set in the forum. Desired behavior after PR is merged: You can see the favourites counter on the forum question, just like most huge forums have. For example Stackoverflow:  Result on profile:  Result on question:  Right now you cannot see it while it has value. You can set/see your own favorites on your profile for example. There is even a forum badge for this, "Question set as favorite by 25 users" while there is no way for you to check the value. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Customers can now click anywhere inside a payment or delivery option panel to select it, instead of needing to click a specific control. This makes checkout interactions simpler and more intuitive, especially for users on touch devices or smaller screens.
Original PR description
Task link : https://www.odoo.com/web?#id=1918459&action=327&model=project.task&view_type=form&menu_id=4720 Pad link : https://pad.odoo.com/p/r.1fea18f655e99f79eeeb07abc8e9deb2 Purpose: user click anywhere from panel box of payment acquirer to select payment method. This commit is related to task id 1918459 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 update makes an internal configuration lookup stop as soon as it finds the single expected match. Because these configuration keys are already unique, the change keeps behavior the same while making the lookup slightly more efficient.
Original PR description
Description of the issue/feature this PR addresses: Improvement in `base` module `key` is already `unique` so it makes sense to use limit 1 in search Current behavior before PR: Desired behavior after PR is merged: Ps: Will it be acceptable in v12 ? -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Adds an automated test to confirm that only approved timesheets are invoiced when sales orders include multiple service products. This helps reduce the risk of incorrect invoicing for service work tied to project tasks.
Original PR description
task : https://www.odoo.com/web?debug#id=1885464&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720
Resolved issues and error corrections
Changing the assigned website on website-related records no longer accidentally unpublishes content that was already live. This protects published pages, products, events, jobs, and partner records from disappearing during routine back-office edits.
Original PR description
Before this commit, when changing the website field in a record form view, the is_published field would be force to false, ending unpublishing the record if it was published. That behavior was coming from the fact that is_published field is missing from the form view. Thus, onchange on website is triggering a recompute server side without is_published as the JS framework is not sending the field. The ORM is then fallbacking on default Boolean value (False) for is_published when sending back the onchange result. This would only appear on object with 'website.published.multi.mixin' and with website_id in the form view. Replacing website_published by is_published will fix the behavior and has more sense has website_published is the 'is_published' state in a website context. In the backend, we are not in a website context. task-1919689
This fix prevents an error that could appear when users enabled settings or refreshed a page without a record ID. It improves reliability in the web interface by handling missing page information correctly.
Original PR description
- at the time of making datapoint currentId passed is "" (blank string). this is because currentId is "" in params. but after '_extractParamsFromAction' this method it becomes undefined which is…
- at the time of making datapoint currentId passed is "" (blank string). this is because currentId is "" in params. but after '_extractParamsFromAction' this method it becomes undefined which is correct but _.defaults set default value "" as it is undefined. - So, set currentId undefined if it is "" Related commit: https://github.com/odoo/odoo/commit/40dd121938552d3f88289d2e5fcd1d57a0dd01bb#diff-e4abcc1db44a1bf2e663576a3b0975deR92 Issue: 1916837 Description of the issue/feature this PR addresses: got a traceback when try to enable any setting. Current behavior before PR: got a traceback when try to enable any setting. Desired behavior after PR is merged: traceback resolved when enable setting or when a refresh of a page without id. Issue: https://www.odoo.com/web#id=1916837&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.916b21ffbf1d0db10b8ad88d15a0559b -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where pressing Backspace in an empty search bar could trigger an error. Users can now clear or edit searches without being interrupted by a crash.
Original PR description
https://drive.google.com/file/d/1ahIw5m9WbEJkIqCMH_23mOe8c9rNc19P/view?usp=drivesdk This PR is related to Task ID: 1917541 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Changing the assigned website on certain website-related records no longer accidentally unpublishes content that was already live. This helps avoid unexpected visibility changes for appointments, helpdesk pages, and Twitter wall content when administrators update website settings.
Original PR description
Before this commit, when changing the website field in a record form view, the is_published field would be force to false, ending unpublishing the record if it was published. That behavior was coming from the fact that is_published field is missing from the form view. Thus, onchange on website is triggering a recompute server side without is_published as the JS framework is not sending the field. The ORM is then fallbacking on default Boolean value (False) for is_published when sending back the onchange result. This would only appear on object with 'website.published.multi.mixin' and with website_id in the form view. Replacing website_published by is_published will fix the behavior and has more sense has website_published is the 'is_published' state in a website context. In the backend, we are not in a website context. task-1919689
Code cleanup and technical improvements
This update removes an outdated configuration option in Web Studio because search fields are now shown by default. The change keeps the code simpler without changing how business users interact with Studio.
Original PR description
This option is now set to true as default (see PR odoo/odoo#29986).