Daily updates from Odoo
Navigate
Branch
Tuesday, April 16, 2019
20 changes
Security fixes and vulnerability patches
The Gengo private key password field now stays masked when users edit company settings. This prevents sensitive credentials from being shown in plain text and helps protect account security.
Original PR description
Task:https://www.odoo.com/web#id=1892058&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad:https://pad.odoo.com/p/r.66df6a740488a010c60a4c43028c71ac -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
New functionality added to Odoo
Online shoppers can now view product videos directly on e-commerce product pages, alongside existing product images. This helps businesses present products more clearly and can improve customer confidence before purchase.
Original PR description
Task - https://www.odoo.com/web#id=1945483&model=project.task&view_type=form&menu_id=5195 Pad - https://pad.odoo.com/p/r.d8a742a1ff985775a0dae53959b0dd9e 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 adds Indonesia-specific accounting setup in Odoo, including a local chart of accounts and tax definitions. It helps Indonesian businesses start using Odoo Accounting with country-appropriate defaults and reduces manual setup.
Original PR description
Description of the issue/feature this PR addresses: - Task : https://www.odoo.com/web#id=42243&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 - Pad : https://pad.odoo.com/p/r.0cc60a058652f804d7198ca71209f126 Current behavior before PR: - Create a l10n_id localization Desired behavior after PR is merged: 1. Create a CoA 2. Taxes -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
This update makes it easier for developers and partners to customize how product pricelist items are searched. It reduces the need to duplicate or bypass existing pricing logic when extending pricelist behavior, supporting safer and more maintainable customizations.
Original PR description
Description of the issue/feature this PR addresses: If you want extend the pricelist system by adding `applied_on` or any other idea, you need to by pass all the code. With this PR you can just inherit the search of items. @nim-odoo -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Employee profiles will automatically add resume entries when an employee completes a course or earns a certification. This makes employee development records easier to maintain and gives managers a clearer view of skills, training, and achievements.
Original PR description
Description of the issue/feature this PR addresses: on the employee profile see the certifications and lessons an employee followed Desired behavior after PR is merged: When a employee succeed a course or a certification, a new line will be added in resumé of employee profile. id=1946215 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adds a new Buy Now option to the eCommerce product flow, allowing customers to move directly toward checkout instead of first adding items to the cart. It can reduce purchase friction and help improve conversion for shoppers who are ready to buy immediately.
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
The website SEO dialog now handles empty titles and descriptions more clearly by falling back to default page values in the preview and on the page. It also removes a duplicate preview, adds helpful placeholders, and renames the social preview for better clarity.
Original PR description
**Improvements in behaviour of Optimize SEO dialog** After this PR is merged, when you keep title and description fields empty, then the page will use default title and description. We have added default_title and default_description to render the preview with default values when title and description fields are empty in SEO dialog. A fix has been done on rendering of the 'Preview' in SEO dialog. Earlier 2 previews were being shown, now we've removed the extra one. Some minor amendments like adding placeholders to title and description and renaming of second preview of SEO dialog to "Social Preview". Task Link: https://www.odoo.com/web?debug#id=1949636&action=327&model=project.task&view_type=form&menu_id=4720 Pad Link: https://pad.odoo.com/p/r.6991f9e0448188a816cbbc85672ada39 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website shop setup tour now points to a snippet that appears near the top of the list, making the drag-and-drop instruction easier to notice. This helps users follow the onboarding flow more smoothly when building or editing an online shop page.
Original PR description
related to task: 1942742 Description of the issue/feature this PR addresses: step to drag snippet is not enough visible. Current behavior before PR: step to drag snippet is not enough visible Desired behavior after PR is merged: step to drag snippet is now visible Task: https://www.odoo.com/web?#id=1942742&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.931c7ff1b3a5a3ce63f0a716ee633aac -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Project Overview profitability button now directs users to the Project Costs and Revenues report for the selected project. This gives managers a fuller view of both costs and revenue when assessing project profitability, and also corrects a small label typo.
Original PR description
In the Project Overview, the Profitability report takes into account Timesheet costs, but doesn't include information on Revenue. Because of that, the user is missing crucial information to determine the profitability of a given project. This PR aims at fixing this issue by sending the user to the 'Project Costs and Revenues' report of the concerned project when clicking the 'Profitability' button within the Project Overview page. It also fixes a tiny labelling typo. Task-1963932 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website editors now have a simpler way to change logo and font sizes. The manual confirmation box was removed, and entered values are validated automatically when users click away, reducing friction while editing pages.
Original PR description
Description of the issue/feature this PR addresses: Task ID: https://www.odoo.com/web?#id=1952964&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 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
Demo barcode data for stock locations was moved out of the demo file and into regular data setup. This makes barcode-related examples and tests more consistent without changing day-to-day business workflows.
Original PR description
**Description of the issue/feature this PR addresses**:
- Task: https://www.odoo.com/web#id=1947320&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720
- Pad: https://pad.odoo.com/p/r.78fd07890eda2e9557392580503602dc
**Description:**
-Removed demo data of stock.location from demo file and added it into data file.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis change introduces a reusable way to test Belgian payroll calculations against specific payslip scenarios. It helps the payroll team validate more cases consistently, reducing the risk of incorrect salary computations over time.
Original PR description
In order to ensure that we compute correctly all the payslips, we need to test specific cases. This commit aims at facilitating the writing of such tests
Payroll now supports configuring which absences or work entry types are unpaid for each salary structure, so payslips can deduct unpaid time more accurately. Belgian payroll data and 13th month rules are also improved, and payslip reports now show worked-day amounts for clearer employee compensation details.
Original PR description
[IMP] hr_payroll*: Add work entry data ===================== This commit adds benefit types and leave types data. In particular, add Belgian data. [IMP] hr_payroll: Clean unnecessary `@api.model`…
[IMP] hr_payroll*: Add work entry data ===================== This commit adds benefit types and leave types data. In particular, add Belgian data. [IMP] hr_payroll: Clean unnecessary `@api.model` ==================== Clean `@api.model` of `hr.payslip`. Method `get_worked_day_lines` does not need to be `@api.model`. Method `_get_payslip_lines` was wrongly an `@api.model` because it was using self. [IMP] hr_payroll: Allow to get days data for multiple work entry types ================== Currently the method `get_work_days_data` only accept one work entry type as parameter. After this commit, the method accept multiple benefit types. The data returned is the sum of attendance/leaves data for all benefit types in the parameter. [FIX] hr_payroll: Allow recreate cancelled work entry ===================== If a work entry have been cancelled (active: True -> False), an other work entry cannot be created with the same employee, type and date because it violates the unique constraint. The unique constraint should not take into account inactive records. Also the SQL query detecting conflicts between work entries should only take into account active entries. This commit fixes both issues. [IMP] hr_payroll: Add unpaid work engine ================= Purpose --------- Currently, all work entries are considered paid when payslips are computed. However, some work entry types may not be paid (e.g. unpaid leave, long sick leave). Some work entries are paid for some salary structures but not in others. e.g. In Belgium, "Breastfeeding Break" is not paid in the monthly payslip, but counts for "13th month" and "double holiday". There should be a way to choose which work entries (based on the type) are paid/unpaid based on the payslip structure. Specification --------------- Add a m2m field `unpaid_work_entry_type_ids` on payslip structures. When a payslip is computed, the amount corresponding to unpaid work entries is deducted. The deducted amount equals the number of unpaid days multiplied by the average daily salary. The average daily salary is computed as the average wage over 3 months (the number of days in three months is always constant = 13 weeks) [IMP] hr_payroll: Display worked days amount on payslip ================== Purpose ----------- Currently, the number of days and hours for each worked days are displayed on the payslip report based on the work entry type. However the corresponding amount is not. Specification ------------- For each work days line, display the corresponding amount on the report. Amounts should be computed as follows: Worked days lines of unpaid work entries: 0 For other worked days lines: Distribute the paid amount (=basic) among paid worked days types. amount of the line = basic * (number of days of the line)/(total number of paid days) [IMP] l10n_be_hr_payroll: Improve 13th month salary structure ================= Purpose ----- Currently the 13th month salary structure does not take into account many rules in CP200. Specification ------- The following rules should be applied: 1. The 13th month amount equals the December wage 2. An employee isn't allowed a 13th month if he has less than 6 months seniority. 3. If the employee did not worked the full year (but more than 6 months), the amount is prorated according to months fully worked. 4. Some work entries can be deducted (absences). Deducted work entry types: Unpaid, Unpredicatable reason, Long Term Sick, Part Time Sick, Notice
Resolved issues and error corrections
This update fixes small issues in the online shop experience, including incorrect labeling and iframe closing behavior. These corrections help make product pages and website sales interactions clearer and more reliable for shoppers and staff.
Original PR description
…20f9d9e21141baf6 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 change adjusts when certain online shop price list checks run so they happen after installation instead of during setup. This helps avoid unrelated test failures and keeps automated validation more reliable without changing customer-facing behavior.
Original PR description
Before this commit, theme runbot-theme was red somehow for the geoip pricelist test. Adding post_install seems to fix the issue, anyway it is better to flag the tests as such as it make no sense to test pricelists during module install.
This fixes an issue where timesheet unit fields could use the wrong display format in normal loading mode. Users should now see timesheet values shown with the correct unit format consistently, matching the intended company/session settings.
Original PR description
When the assets are loaded, the `hr_timesheet.timesheet_uom` scope is loaded in order to bind the `timesheet_uom` to the correct already existing widget (defined in the session, like `float_time` or `float_factor`, ...). The problem is that in normal mode (not debug assets), when the binding is done, the field_registry is empty, so the correct base widget is not applied. The fix is to add the scope filling the registry in the requirements of the `timesheet_uom` scope. Strangely, it was working in debug assets mode. 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
Odoo Studio users can edit search views again after a recent change accidentally made them unavailable. This restores expected customization options for filtering and searching records in Studio.
Original PR description
Since rev. odoo/enterprise@520c017 it wasn't possible to edit the search view anymore.
Gantt schedule items now appear in the correct time slots on days affected by daylight saving time changes. This prevents confusing placement errors when a day has a missing or repeated hour, improving reliability for teams using planning views.
Original PR description
When we switch to DST, two unusual things happen: - One day is missing one hour (1pm then 3pm) - One day has the same hour twice (2pm then 2pm) Before this commit, pills were placed in wrong slots on those days because of the missing/duplicated slots. To fix this, I changed the way we insert pills into slots, which is now the same way we match pills into intervals for aggregation. Because the variable was named "pillsInThisSlot", I thought I could merge the two and only compute it once. However, one of them put pills into slots (the new one), while the other actually put pills into intervals (the existing one), so I changed the name of the existing variable to make the difference more obvious.
Code cleanup and technical improvements
Several internal fields named "type" were renamed to more specific names across Odoo modules. This reduces conflicts with standard Python behavior, making the platform easier to maintain and less prone to technical issues without changing day-to-day user workflows.
Original PR description
**Description of the issue/feature this PR addresses:** Follow-up of https://github.com/odoo/odoo/pull/27262. **Current behavior before PR:** Many models have the selection field `type`, which overwrites the python method [type](https://docs.python.org/3/library/functions.html#type). **Desired behavior after PR is merged:** Some `type` fields of several models have been renamed to _something_type_. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update standardizes several internal field names across accounting, product, CRM, document sharing, attachments, and partner records. It mainly improves maintainability and consistency for future development, with little expected direct impact on day-to-day users.
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/27599. I have not tested it, so maybe I left few cases to adapt, but once the community PR is merged, then it will be fast and easy to detect the remaining cases and adapt them.