Daily updates from Odoo
Thursday, July 25, 2019
9 changes · master
Enhancements 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 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 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
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
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