Daily updates from Odoo
Monday, August 20, 2018
11 changes · master
Enhancements to existing features
This update replaces a direct database operation with Odoo's standard data access approach in the conversion tooling. It helps keep the code easier to maintain and better aligned with platform practices, with no expected change for end users.
Original PR description
Hi @odony, don't need SQL execute here, use ORM instead :-) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo now uses the open-source Chromium browser by default instead of relying on Google Chrome. Organizations can still choose Google Chrome through configuration if they prefer, improving licensing flexibility and deployment control.
Original PR description
Current behavior before PR: https://github.com/odoo/odoo/pull/25991 introduced for the 1st time a closed source hardcoded dependency in Odoo. I'm not sure it's even legal for a LGPL project, but in any case, it makes not much sense to introduce that problem when there is the almost-completely binary compatible Chromium project, which is fully open source. Desired behavior after PR is merged: * Use by default the open source version Chromium. * Allow to configure it through CLI and conf file, for those that still want to test with Google Chrome. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @Tecnativa
This update adjusts mobile dropdown menu styling so status-related options display correctly and consistently. It also updates automated tests to help prevent the issue from returning in future releases.
Original PR description
BS4: statusbar dropdown issue https://drive.google.com/file/d/12smrfCMGo4iH2FqPaGCxphu5ltEax7XX/view?usp=sharing https://drive.google.com/file/d/1NqBMNOKOOKk8vl6dMbFduBCuWew94VEw/view?usp=drivesdk
Resolved issues and error corrections
Fleet reference data has been moved from demo-only content into standard module data. This ensures the fleet module has the needed baseline information even when a database is created without demo data, improving consistency for real use cases.
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 fixes a visual alignment issue in the web interface where menu entries without sub-items did not line up properly with other entries. The change makes navigation menus look more consistent and easier to scan for users.
Original PR description
fix alignment of menu entries without children: https://drive.google.com/a/odoo.com/file/d/10_j3cFgOJ5tpUWNpN1vYJDyKbuGvxefK/view?usp=drivesdk 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 the color picker used for tags on forms so it appears where users expect when changing a tag color. The change improves usability and reduces confusion when editing tagged records.
Original PR description
BS4 Issue: The color change box is not appearing at the desired location when u try to set the color of a tag ( https://youtu.be/H5lUiKIVrsU ) 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 checkout payment page has been cleaned up to make payment methods, billing and shipping details, and delivery options easier to read and compare. This improves the shopping experience by fixing alignment issues, reducing visual clutter, and making labels such as free delivery clearer.
Original PR description
- align payment method(Ex.Stripe) form attributes in row. - fix align between radio button and payment method name. - removed header div from 'billing & shipping'. - set badges(Ex.free) and align between badges and delivery method name in choose delivery method. - border subtraction from delivery methods div as already card class has border. Description of the issue/feature this PR addresses: 1) https://drive.google.com/file/d/1fZje7_eSA9H3E4wJ35jYTkQohU5NkVg1/view 2) https://www.awesomescreenshot.com/image/3517534/d56b76dbef078ad172f73d976bcbca82 Current behavior before PR: UI issues in shop/payment page in website. Desired behavior after PR is merged: Improved ui of shop/payment page. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes a visual issue where statusbar dropdowns could appear or behave incorrectly in forms. The change improves usability for users working with records that rely on status changes, making navigation and updates more reliable.
Original PR description
BS4: statusbar dropdown issue https://drive.google.com/file/d/12smrfCMGo4iH2FqPaGCxphu5ltEax7XX/view?usp=sharing https://drive.google.com/file/d/1NqBMNOKOOKk8vl6dMbFduBCuWew94VEw/view?usp=drivesdk -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes a layout problem affecting customer portal pages on tablet-sized screens. Helpdesk and subscription portal content should now appear as intended, improving readability and usability for customers using those pages.
Original PR description
BS4 issue in pad: https://drive.google.com/file/d/11nTNXy5IWSLghD_jIteNRiOOqcWF0oDb/view?usp=drivesdk expected https://drive.google.com/file/d/1TTF4fyrBFriI_N0qyFWoRASnPGaW-3Jr/view?usp=drivesdk
The signing process no longer assumes an SMS number is always provided when creating a signature request. This prevents errors in flows such as salary contract handling and avoids unnecessary updates to contact records.
Original PR description
The sms_number is a related, not mandatory field on a sign.request In hr_contract_salary for instance, the sms_number is not given (KeyError). In the wizard it was given but just the value of related. This was making an unecessary write on the partner when the key was given.
Documentation and clarification updates
The corporate Contributor License Agreement record for Dynapps N.V. has been updated. This keeps Odoo's contributor legal documentation current and helps ensure contributions are properly covered.
Original PR description
Update of DynApps N.V. corporate CLA agreement. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr