Daily updates from Odoo
Navigate
Branch
Wednesday, January 8, 2020
37 changes
New functionality added to Odoo
Website editors can now set sections to half-screen or full-screen height, making pages easier to design with strong visual layouts. Full-height sections can also include a scroll-down button, helping visitors move smoothly to the next part of the page.
Original PR description
This commit adds a "Height" option to sections, allowing them to have a minimum height of the user's choosing (either full screen height or half screen height, similar to blog covers). Enabling the full screen option also allows the user to add a "scroll down button" that will scroll down to the next section, also similar to blog covers. task-2152184 also see odoo/design-themes#197
Enhancements to existing features
This update refreshes the PDF viewing component used in Odoo to a newer PDF.js version. It helps keep document preview functionality current and adapts related website slides behavior so PDFs continue to display correctly.
Original PR description
Task:https://www.odoo.com/web#id=2124443&action=333&active_id=1251&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.a33eaa2cc360a778a439603f92f4c5bf -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website page snippets such as banners, covers, pictures, text blocks, and columns were streamlined to make them easier to edit. The changes remove unnecessary editing controls, improve image presentation, and make styling options more consistent, helping users build pages faster with fewer distractions.
Original PR description
This commit reviews a bunch structure snippets to streamline their use and edition, namely: Banner, Cover, Picture and Text-block snippets: - Remove extraneous levels of edition (buttons, heading/text only columns) Picture snippet: - make picture bigger Three columns and comparison snippets: - Make regular column options available on the cards - Remove unwanted UI elements (card footer, button) Cover snippet: - Make title bold It also consolidates the main colorpicker and the column colorpicker into a single option as they did the same thing and allows inner content to be dropped next to images in the Image - Text and Text - Image snippets. linked to odoo/design-themes#192 task-2152184
Adds quick search and grouping options for model constraints, making it easier to find specific constraints by key fields such as name. This helps functional users navigate constraint records more efficiently when reviewing or managing system configuration.
Original PR description
Description of the issue/feature this PR addresses: No quick search options Current behavior before PR: There are no easy search options on the model `ir.model.constraint` Desired behavior after PR is merged: Quick search options for the most important fields and a quick search by name. This speeds up searching through constraints:  -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Rental users can now check whether products are available directly from the rental configurator, helping them confirm stock before finalizing a rental. The update also prevents duplicate action buttons from appearing when Gantt views open in pop-up windows, improving the user experience.
Original PR description
Task: https://www.odoo.com/web?#id=2063955&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.f61c03f2828a54889e87b3ad333157da
Signed documents in the Sign app now display a ribbon once fully completed. This gives users a clear visual confirmation that the signing process is finished and the document has reached its completed state.
Original PR description
Task: https://www.odoo.com/web#id=2153927&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.1bb07f6a0ed78e2606eb79a3054252d1
Event management now supports more flexible planning flows by replacing fixed event states with customizable stages. Event teams also get improved timeline views for events and tracks, making it easier to schedule, review, and manage activities over time.
Original PR description
PURPOSE Improve event management by replacing static states by dynamic global stages. It gives more flexibility and allows event users to customize their flow according to their business requirements. SPECIFICATION 1. Remove the color picker widget from planning (moved to web) 2. Add a gantt view for Event and improve the Tracks gantt view LINKS Task #2088538 Com PR odoo/odoo#39486 Enterprise PR odoo/enterprise#6460
Resolved issues and error corrections
The inventory transfer screen no longer shows the Validate button when a transfer has no item lines. This prevents users from trying to validate an empty operation and makes the workflow clearer.
Original PR description
Description of the issue/feature this PR addresses: Go to inventory Create a picking Save --> you see the validate button --> it doesn't make sens because there no `move_lines`. Note : apply the same behavior than the `mark_as_todo` button. @nim-odoo -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents an error when users delete several manufacturing orders at the same time. It helps keep manufacturing cleanup actions reliable and avoids interruptions during routine order management.
Original PR description
Task : https://www.odoo.com/web#id=2168386&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.afebc8aabb3bfe5c81365f3d76016812 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 the sales order stat button so timesheet quantities are shown correctly when the timesheet unit of measure is days. This helps users see accurate delivered or logged time figures on sales orders and avoid misleading totals.
Original PR description
When UOM of timesheet is in days, the amount is not correct in the stat button of sale. taskID: 2160680 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Existing service products now keep the expected “Ordered quantities” invoicing behavior when the Timesheets app is installed after Sales. This prevents products from ending up with an empty invoicing policy, reducing confusion and helping invoices remain consistent.
Original PR description
Pad: https://pad.odoo.com/p/r.10459eb72aca3437c398bd64aa2c5490 Task: https://www.odoo.com/web?#id=2146778&action=327&model=project.task&view_type=form&menu_id=4720
Website editors can now see and use the delete option when editing inner content snippets. This makes it easier to remove unwanted nested content without extra workarounds, improving the page editing experience.
Original PR description
Description of the issue/feature this PR addresses: TaskID: https://www.odoo.com/web?#id=2153115&action=327&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
This fix updates the manufacturing screen wording when a production item has no related work order. It helps users better understand the situation and avoid confusion during manufacturing operations.
Original PR description
task-2128553 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 fix restores the document signing experience after an update to the PDF viewer changed how pages are identified. Users can continue opening and signing PDFs without issues caused by the viewer upgrade.
Original PR description
Task:https://www.odoo.com/web#id=2124443&action=333&active_id=1251&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.a33eaa2cc360a778a439603f92f4c5bf
This update adds internal names to page sections across multiple Odoo Enterprise apps. It makes those screens easier and safer for developers to customize, with no expected change to day-to-day user workflows.
Original PR description
Page is an element that is often used for xpath expressions so having a name on it makes it much easier as a developer. This is a followup of the community PR at https://github.com/odoo/odoo/pull/41718
Features or functions removed from Odoo
This change removes unused stock movement logic that is no longer needed in the inventory app. It simplifies maintenance without changing day-to-day stock operations for users.
Original PR description
- Remove the unused field call string_availability_info on the stock.move model. It was used in version 11.0 in a form view, this form views has been merge and this fields is now unused. - Remove onchange_quantity function, because the product_qty can't be change (_set_product_qty doesn't allow that) and the product_id is required.
Code cleanup and technical improvements
This update reorganizes how event-related settings are automatically kept in sync across the event, event sales, website event, event questions, and event track areas. It should reduce inconsistencies in event configuration without changing the day-to-day user experience.
Original PR description
task-2089156 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
Miscellaneous changes
### Description of the issue/feature this PR addresses: Now use directly the posted state from account move. This was changed in a constraint in l10n_latam_invoice_document module and and also in view domain in l10n_ar module. ### Current behavior before PR: 1. the constraint that check the proper invoice number and document type was not been properly applied when the invoice has been posted. 2. the responsibility field in account.move form was not properly hide when the invoice has be
Original PR description
### Description of the issue/feature this PR addresses: Now use directly the posted state from account move. This was changed in a constraint in l10n_latam_invoice_document module and and also in view domain in l10n_ar module. ### Current behavior before PR: 1. the constraint that check the proper invoice number and document type was not been properly applied when the invoice has been posted. 2. the responsibility field in account.move form was not properly hide when the invoice has been posted ### Desired behavior after PR is merged: 1. the constraint that check the proper invoice number and document type now applies when the invoice has been posted. 2. the responsibility field in account.move form was not properly set to invisible when the invoice has been posted -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42140
### Description of the issue/feature this PR addresses: The purpose of this partner is that we do not need to report to AFIP the identification number. ### Current behavior before PR: Since this partner identification was configured as DNI it was throwing an error when validate an invoice for that partner in AFIP, AFIP was requesting us to sent the DNI number. ### Desired behavior after PR is merged: Now we activate the Sigd "Sin identificar/venta global diaria" identification typ
Original PR description
### Description of the issue/feature this PR addresses: The purpose of this partner is that we do not need to report to AFIP the identification number. ### Current behavior before PR: Since this partner identification was configured as DNI it was throwing an error when validate an invoice for that partner in AFIP, AFIP was requesting us to sent the DNI number. ### Desired behavior after PR is merged: Now we activate the Sigd "Sin identificar/venta global diaria" identification type (code 99), and proper configure the Anonymous Final Consumer partner: AFIP validate the invoice directly and does not request us the identification number. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#41676
Fix an error which occurs during an attempt to access the string attribute of a non existing measure 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 Forward-Port-Of: odoo/odoo#42941 Forward-Port-Of: odoo/odoo#42844
Original PR description
Fix an error which occurs during an attempt to access the string attribute of a non existing measure 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 Forward-Port-Of: odoo/odoo#42941 Forward-Port-Of: odoo/odoo#42844
### Issue - Install Blog - Create a post - Remember the last update date - Visit the post - Check the last update date After visiting the post, the last update date changed. ### Cause In the web_blog main.py controller, we increase the visit count with a write, so the write_date is updated. ### Solution Keep the old write_date by forcing it. **OPW-2166289** -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.
Original PR description
### Issue
- Install Blog
- Create a post
- Remember the last update date
- Visit the post
- Check the last update date
After visiting the post, the last update date changed.
### Cause
In the web_blog main.py controller, we increase the visit
count with a write, so the write_date is updated.
### Solution
Keep the old write_date by forcing it.
**OPW-2166289**
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#42922
Forward-Port-Of: odoo/odoo#42897Reversal of ef46378cd38d6cb361f1b867a3009f3bbe3bd7c1 The bug we tried to fix with the reverted commit was fixed by 3023cd24af35bf63f1c962ec51183a20f9ca80e0 but it was causing other issues, like the text field translate button badly positionned -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42902
Original PR description
Reversal of ef46378cd38d6cb361f1b867a3009f3bbe3bd7c1 The bug we tried to fix with the reverted commit was fixed by 3023cd24af35bf63f1c962ec51183a20f9ca80e0 but it was causing other issues, like the text field translate button badly positionned -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42902
### Issue - Take a v13 runbot - Open survey's app - Open one of the surveys - Click on edit - Click on a question - Open 'option tab' - Make sur the field 'mandatory answer' is true - Try to translate field 'error message' -> Error ### Cause this occur because because we try to update the model survey.question from the list coming from survey.survey which mean that the record.viewType is list and not form. Since the fiel
Original PR description
### Issue
- Take a v13 runbot
- Open survey's app
- Open one of the surveys
- Click on edit
- Click on a question
- Open 'option tab'
- Make sur the field 'mandatory answer' is true
- Try to translate field 'error message'
-> Error
### Cause
this occur because because we try to update the model survey.question
from the list coming from survey.survey which mean that the
record.viewType is list and not form.
Since the field 'error message' is not in the list view, it's not
present in the dedicated dictionary from record.fieldsInfo.
### Solution
Add the field constr_error_msg into the embedded list view
**OPW-2157631**
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#42866Since dae065d, model defaults are retrieved based on the env company instead of the user's company. However, for a request with auth='none', the company might not be set on the environnement (if `allowed_company_ids` is not in the context). This makes the sql query crash, trying to compare an integer to `false`. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42838
Original PR description
Since dae065d, model defaults are retrieved based on the env company instead of the user's company. However, for a request with auth='none', the company might not be set on the environnement (if `allowed_company_ids` is not in the context). This makes the sql query crash, trying to compare an integer to `false`. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42838
some fields may depend on invoice_ids, which lead to a perf issue when field is not searchable. Forward-Port-Of: odoo/odoo#41117
Original PR description
some fields may depend on invoice_ids, which lead to a perf issue when field is not searchable. Forward-Port-Of: odoo/odoo#41117
Purpose ======= Since https://github.com/odoo/odoo/commit/ee8106bd7aff56aa1897b18e1a967466c6937045 the resume lines generated from the eLearning/Certfication courses are not rendered properly. TaskID: 2149477 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 Forward-Port-Of: odoo/odoo#42478
Original PR description
Purpose ======= Since https://github.com/odoo/odoo/commit/ee8106bd7aff56aa1897b18e1a967466c6937045 the resume lines generated from the eLearning/Certfication courses are not rendered properly. TaskID: 2149477 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 Forward-Port-Of: odoo/odoo#42478
Before this commit, opening the messaging menu might be slow. This was caused by the parsing of messages' bodies with lots of HTML nodes. Indeed, messages' bodies are linkified and inlined, and both processes were quite slow due to their implementation: each node in the HTML were recursively parsed and re-assigning `innerHTML`. As a result, each node was triggering an HTML parse, which is very slow on complex nodes. This commit fixes this performance issue by speeding up inlining and
Original PR description
Before this commit, opening the messaging menu might be slow. This was caused by the parsing of messages' bodies with lots of HTML nodes. Indeed, messages' bodies are linkified and inlined, and both processes were quite slow due to their implementation: each node in the HTML were recursively parsed and re-assigning `innerHTML`. As a result, each node was triggering an HTML parse, which is very slow on complex nodes. This commit fixes this performance issue by speeding up inlining and linkifying of html strings. In the case of linkify, it now triggers an HTML parse only when necessary, while inlining now relies on its textContent value. These changes should drastically improve the speed of opening and rendering messaging menu, almost ten times faster. Task-Id 2076299 Forward-Port-Of: odoo/odoo#37387
TaskID: 2153158 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 Forward-Port-Of: odoo/odoo#41547
Original PR description
TaskID: 2153158 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 Forward-Port-Of: odoo/odoo#41547
Pad: https://pad.odoo.com/p/r.4e9bb99308c8666083658127b6d21c69 Task:https://www.odoo.com/web#id=2157055&action=327&model=project.task&view_type=form&menu_id=4720 Forward-Port-Of: odoo/odoo#42163
Original PR description
Pad: https://pad.odoo.com/p/r.4e9bb99308c8666083658127b6d21c69 Task:https://www.odoo.com/web#id=2157055&action=327&model=project.task&view_type=form&menu_id=4720 Forward-Port-Of: odoo/odoo#42163
- Create a journal. - Create a vendor bill on this journal. => Odoo allows you to set a starting sequence number for your invoice. This number must always use the sequence used when posting the invoice. However, the invoice date was taken instead of the accounting date. Before this commit, when setting an invoice date at Y and an accounting date at Y - 1, the edited sequence was the one in Y - 1 but at the one in Y was used at the validation. Manual forward-port of https://github.co
Original PR description
- Create a journal. - Create a vendor bill on this journal. => Odoo allows you to set a starting sequence number for your invoice. This number must always use the sequence used when posting the invoice. However, the invoice date was taken instead of the accounting date. Before this commit, when setting an invoice date at Y and an accounting date at Y - 1, the edited sequence was the one in Y - 1 but at the one in Y was used at the validation. Manual forward-port of https://github.com/odoo/odoo/pull/42579 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42596
This commit corrects erroneous instructions in the documentation page for the installation of Odoo. Additionally, the following changes are made: - Added new instructions where the steps were not clear or complete enough. - Replaced installation some flows for an easier onboarding. - Reworked some parts of the page structure and display. task-2072822 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40319
Original PR description
This commit corrects erroneous instructions in the documentation page for the installation of Odoo. Additionally, the following changes are made: - Added new instructions where the steps were not clear or complete enough. - Replaced installation some flows for an easier onboarding. - Reworked some parts of the page structure and display. task-2072822 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40319
To add my signature in the c2c's CLA I try to confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42872 Forward-Port-Of: odoo/odoo#42729
Original PR description
To add my signature in the c2c's CLA I try to confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#42872 Forward-Port-Of: odoo/odoo#42729
Steps to reproduce: - install sales, website, ecommerce - go into debug mode and open your browser's console - debug menu > start tour > shop Previous behavior: tour does not find trigger for the first step Current behavior: tour starts properly opw-2126704 Forward-Port-Of: odoo/odoo#42850
Original PR description
Steps to reproduce: - install sales, website, ecommerce - go into debug mode and open your browser's console - debug menu > start tour > shop Previous behavior: tour does not find trigger for the first step Current behavior: tour starts properly opw-2126704 Forward-Port-Of: odoo/odoo#42850
"Groups" button on consolidation chart view used to display all groups when clicked, instead of only showing the groups linked to the current chart. Task : https://www.odoo.com/web#id=2089775&action=327&model=project.task&view_type=form&menu_id=4720 Forward-Port-Of: odoo/enterprise#7360
Original PR description
"Groups" button on consolidation chart view used to display all groups when clicked, instead of only showing the groups linked to the current chart. Task : https://www.odoo.com/web#id=2089775&action=327&model=project.task&view_type=form&menu_id=4720 Forward-Port-Of: odoo/enterprise#7360
Steps to reproduce the bug: - Export an asset A as xls from account.asset with Aquisition Date and First Depreciation Date - Import the xls file Bug: The Aquisition Date and First Depreciation Date were not kept in the imported file. opw:2154843 Forward-Port-Of: odoo/enterprise#7579
Original PR description
Steps to reproduce the bug: - Export an asset A as xls from account.asset with Aquisition Date and First Depreciation Date - Import the xls file Bug: The Aquisition Date and First Depreciation Date were not kept in the imported file. opw:2154843 Forward-Port-Of: odoo/enterprise#7579
Forward-Port-Of: odoo/enterprise#7369 Forward-Port-Of: odoo/enterprise#7204
Original PR description
Forward-Port-Of: odoo/enterprise#7369 Forward-Port-Of: odoo/enterprise#7204
Custom fw-port of https://github.com/odoo/enterprise/pull/7035 to include https://github.com/odoo/enterprise/pull/7531 The batches were sized according to the number of activities, and not dependent on the number of traces to handle. If 1 activity has a lot of traces (too many to perform in 1 cron execution time), it would never commit its progress, and perform the execution of the first traces every time the cron is called, executing their action multiple times. We instead split i
Original PR description
Custom fw-port of https://github.com/odoo/enterprise/pull/7035 to include https://github.com/odoo/enterprise/pull/7531 The batches were sized according to the number of activities, and not dependent on the number of traces to handle. If 1 activity has a lot of traces (too many to perform in 1 cron execution time), it would never commit its progress, and perform the execution of the first traces every time the cron is called, executing their action multiple times. We instead split in batches of 500 traces. There's no guarantee this is small enough as it can execute any server action, but it's to be aligned with the MailComposer's batch limit. We also patch the test that call this method to ensure it doesn't actually commit the test-data in the database. Forward-Port-Of: odoo/enterprise#7548