Daily updates from Odoo
Thursday, February 7, 2019
11 changes · master
Enhancements to existing features
This change prevents Odoo from recalculating related values when a one-to-many field is updated without any real change. It improves performance and avoids unnecessary background work, with an added stock dependency fix to keep stock picking data accurate.
Bank statement forms now include the chatter area, so users can follow discussions, messages, and activity history directly on each statement. This improves collaboration and traceability for accounting teams when reviewing or reconciling bank statements.
Original PR description
Task : https://www.odoo.com/web#id=1871356&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.f49e91398f39199dfb345f173491de87 Current behavior before PR: http://www.awesomescreenshot.com/image/3525952/70e9544a265839c19bcbbaddbda6945e Desired behavior after PR is merged: http://www.awesomescreenshot.com/image/3525954/4e04f8ef5c2134914b34ffe57fe6f415 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This prepares Odoo’s gamification features so they can be reused beyond forums, especially in eLearning and user profiles. It adds karma-based ranks, profile support, and shared badge tools, laying the foundation for upcoming learning and community experience improvements.
Original PR description
Purpose of this merge is to prepare addition of gamification in slides / eLearning platform. In order to be able to use karma and the badges in other modules we move those models in gamification. A website_profile module is added to hold code, data and all necessary stuff to display a user profile, including its gamification-related details. It is a bridge between gamification and website. It will soon hold a revamped user profile, used in both forum and slides. More generally this merge is linked to ongoing tasks * task ID 1902304 (main eLearning task) PR #29876; * task ID 1922159 (new user profile and gamification) PR #30514; * task ID 1936153 (new homepage for slides) PR #30770; * task ID 1937160 (payment flow and integration with ecommerce) PR #30914; This merge is therefore not functionally complete itself and serves as a preparation for other incoming commits. See sub commits for more details on what has been done here.
Default terms and conditions are now managed from Accounting instead of Sales, so businesses can set them even when the Sales app is not installed. This also makes customer invoices created directly use the same default terms as sales-related invoices, improving consistency.
Original PR description
Task:https://www.odoo.com/web#id=1917663&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad:https://pad.odoo.com/p/r.38975219f77f459272a33ea1282e5ccb -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Product screens are updated to hide sales price and tax information where it is not needed. This reduces pricing visibility for users who should focus on product details rather than commercial or tax settings.
Original PR description
Task: https://www.odoo.com/web#id=1936865&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.fc5c0297881d02ad8c331d1e7e24356b 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 reporting can now be analyzed by the customer’s industry, giving teams another way to understand revenue patterns. This helps sales and management users compare performance across market segments and make more informed business decisions.
Original PR description
**Added a reading level in the sales reporting -> the industry of the customer.** Task Link: https://www.odoo.com/web?#id=1922025&action=327&model=project.task&view_type=form&menu_id=4720 Pad Link: https://pad.odoo.com/p/r.a14c093291f07d61ea9ac9942e5e89ef -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Product forms now include quick access to related quality control points and quality checks. This helps quality control users review existing controls and create new ones directly from the product page, reducing navigation time.
Original PR description
Task link : https://www.odoo.com/web?debug=#id=1913359&action=327&model=project.task&view_type=form&menu_id=4720 Pad link :https://pad.odoo.com/p/r.d5d489a0102a89bd1df36ddc5411ffa2 …lity checks on product form view. Purpose : quality control user directly see and create quality control points and quality checks from the product form view. This commit is related to task id : 1913359
Accounting reports now use a multi-selection control for analytic filters, making it easier for users to choose and manage multiple analytic items. This improves report setup and helps users refine financial reporting with less manual effort.
Resolved issues and error corrections
This fixes an issue that prevented visitors from opening the website menu on mobile devices, especially iOS. It helps ensure mobile users can navigate the website reliably, improving access to pages and content.
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
Fixed an issue that prevented users on iPhones and iPads from opening the website menu properly. This improves mobile navigation for visitors and staff using the website from iOS devices.
Original PR description
PR https://github.com/odoo/odoo/pull/30507 fixed the problem in stable versions, this commit makes the proper fix for master. task-1923151
This fixes an issue where users with signed portal links could be blocked from posting comments because the system compared the same identifier in two different formats. The change ensures the identifier is handled consistently, so valid signed links work as intended.
Original PR description
To post a comment with a signed token, we compare tokens with the pid. The token is signed with the pid, which is an integer. When checking access, we compare the token with a pid as char. Obviously, the comparison failed, and posting the message is refused, as the 2 'pid' does not share the same type. This commit cast the recieved 'pid' into an integer before checking special access.