Monday, July 15, 2024
9 changes · 17.0
Resolved issues and error corrections
Employee resume reports now leave missing descriptions blank instead of displaying sample company text. This prevents confusing or unprofessional demo content from appearing in printed employee documents.
Original PR description
Steps to reproduce ================== - Install hr_skills,web_studio - Go to Employees - Open any record - Add a new resume entry without description - Save - Click on the actions gear - Print > Print Resume => `Odoo India pvt. Ltd` is displayed in the report in place of the missing description Solution ======== Use the new data-oe-demo attribute made for demo data inside studio opw-4033434
Spreadsheet list views now request only the field information they actually need. This reduces unnecessary data transfer, helping list-based spreadsheets load more efficiently without changing user-facing functionality.
Original PR description
Since 8777973edd25314df6ed0327d3f27edcf62f274b, the list data are retrieved with `web_search_read`. However, the payload was not minimal as it contains all attributes of the fields (name, store, sortable, etc.). This commit reduces the payload by only requesting what is needed. Task: 4052706 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 prevents module installation from failing when a database lacks an optional phone search extension. It adds a safety check before creating a specialized phone index, improving reliability for deployments with different database setups.
Original PR description
## Description Following https://github.com/odoo/odoo/commit/19d97aeb262e99f8f31d66d7411793e9807e4522, installing modules that inherit from `mail.thread.phone` mixin on a db that doesn't have the `pg_trgm` extension will fail at module installation when trying to create the trigram index. ## Fix Add a check with `has_trigram` before the creation of the trigram index. ## References opw-4052670 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The product page media viewer now adapts better to narrow screens, so video play and pause controls remain clickable. This improves the shopping experience for customers browsing product videos on smaller browser widths or mobile devices.
Original PR description
To reproduce the bug: 1. Add a video to a product media. 2. In the eCommerce app, go to the product page and switch to the added video. 3. Decrease the browser page width and try to click the play/pause button. The play/pause button is located under the arrow HTML element, making it unclickable. This is because the page is not responsive, and the size of the container element is fixed at 400px. To fix this, I propose making the element responsive and decreasing the height of the arrow elements. opw-3986105
Fixes payment term date calculations when an end-of-month rule uses zero days into the next month. This helps invoices receive the intended due date instead of carrying over the original calendar day, improving payment schedule accuracy.
Original PR description
This commit https://github.com/odoo/odoo/pull/166560/commits/fc2ee9e003f317e34dcc1d01e8e1a34acdb3b8dd fixed the due date which was wrong in some case, but one case was not dealt with. When using the days end of month payment term with a days_next_month to 0, the calculation was wrong. Ex: With the current implementation, If we do a case with 30 end of month 1 with a start date the 22/04, we will add 30 days and end up the 22/05 then we add 1 month (22/06) and fix the day at 1, so we will end up the 01/06. With a days_next_month to 0, the problem is that the relative delta will keep the 22/06 which is not what we wanted. task: 4045689 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The sales order report template was adjusted so users can edit previously inaccessible payment terms and fiscal position sections in the Studio report editor. This makes customizing sales documents easier without technical workarounds.
Original PR description
similar to https://github.com/odoo/odoo/pull/129310 Currently, users cannot edit the bottom part of `payment_terms` and `fiscal_position`, as these are conditional blocks. This commit adds empty divs that will be interpreted by odoo-editor as editable. opw-3558001
The web interface layout was adjusted so the search panel remains fully visible on large screens when the comparison feature is active. This helps users access filters and search options without parts of the panel being hidden.
Original PR description
Before this commit -The searchpanel wasn't fully visible on large screens when the Comparison feature is enabled. Changes: -Increased and fixed the minimum width of o_control_panel_actions so the searchpanel appears more to the right. -Decreased minimum width of o_comparison_menu for the title to go to multiline Task-3866695 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Calendar meetings now save the generated access token when the meeting is first created. This keeps the Odoo Meeting link unchanged when users later edit the event, avoiding confusion from mismatched links.
Original PR description
Steps to reproduce: - Install Calendar and Appointment - Go to Calendar - Create a meeting with a name and click on "+ Odoo Meeting" - Copy this link and keep it on the side - Create the event and edit it - Copy the link Issues: The link doesn't match, this is because we are not sending the access token upon the creation of the meeting to the backend. This causes a new access token to be created which ends up in a new link. opw-3910706
This update fixes visual alignment issues in the sign module where text and icons were inconsistently positioned in both the customer portal and backend interfaces. The fix ensures a polished, professional appearance with consistent alignment across all sign-related screens, improving the overall user experience.
Original PR description
Before this PR: In the sign module, there are inconsistencies with the alignment of texts and icons, in both the portal and backend interfaces. After this PR: This fix addresses alignment issues and ensures consistency between the portal and backend interfaces. Now, texts and icons in the sign appear aligned and consistent across both interfaces.