Monday, November 15, 2021
4 changes · master
Enhancements to existing features
Website background images now default to a centered position, making wide or tall images look better when replaced. Editors also get a rule-of-thirds grid while adjusting background position, helping them place key visual elements more accurately.
Original PR description
**PURPOSE:** When you use an image as a background, it is positionned at ~0% ~100%. 83% of pictures have the main element at the center of image and/or apply the rule of 1/3 but in both case, the…
**PURPOSE:**
When you use an image as a background, it is positionned at ~0% ~100%.
83% of pictures have the main element at the center of image
and/or apply the rule of 1/3 but in both case, the user will want to center
the background image.
We also want to help the user to place properly his image.
Other example, for the carousel snippet:
actual default position: https://cdn.discordapp.com/attachments/687642880793378830/748500811017093220/unknown.png
expected position: https://cdn.discordapp.com/attachments/687642880793378830/748500949454291034/unknown.png
**SPECIFICATION:**
Part 1:
By default the image should be vertically and horizontally centered.
Two pictures, one extra wide and one extra tall are in attachment.
Part 2:
Also to help the user to position the image with the ⅓ rule,
we should display a grid that divides a rectangle into nine equal parts
once the user start to position the background https://tinyurl.com/y3gdwaas
the same way we do it for the crop: https://tinyurl.com/yyts6obd
Note that the grid divide the image in 9 parts and not the visible area.
**LINKS:**
TaskID: 2319593
Closes: https://github.com/odoo/odoo/pull/58175Project customer rating reports and dashboards were refined to make satisfaction trends easier to understand, with clearer views, filters, badges, and menu placement. Project rating indicators now focus on the last 30 days, helping teams monitor recent customer satisfaction more accurately.
Original PR description
The purpose of the commit is to improve the customer rating report of the project app. So in this commit, done the below changes: - remove the project and task measures - switch the rating value and…
The purpose of the commit is to improve the customer rating report of the project app. So in this commit, done the below changes: - remove the project and task measures - switch the rating value and the count from a place in pivot view - remove the default group by the rated operator, keep it for graph view - reorder some fields on form and list view - use the badge widget for the rating field and the color code is applied to the form view - add an optional list view - the following fields should be optional: rated_partner_id, parent_ref, resource_ref, partner_id, feedback - all of these fields are displayed by default, except the feedback one that is hidden by default - add some demo data for the feedback field - center the information vertically in kanban view - move the 'customer ratings' menu item below the 'project costs and revenues' one - add the following filters: My Projects, My Team - reorder the group bys and rename 'Resource' into 'Task' - reorder the search fields - project kanban card:[Done] - the rating % represents the average satisfaction rate of the ratings submitted in the last 30 days (including today) - change the tooltip to the Average satisfaction rate for the last 30 days - the 'customer satisfaction' stat button display the last 30 days' rating on the project.project and this stat button should open the kanban view by default instead of the list view TaskId: 2531428
Website editors can now set minimum and maximum values for chart axes in line and bar charts. This helps charts better reflect data ranges that do not start near zero, making visual reporting clearer and less misleading.
Original PR description
PURPOSE: If your data aren't close to zero, your chart could not represent reality. SPECIFICATION Add two inputs: min and max for the values of the chart axis configuration. task-2250766 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
The eCommerce search bar now handles products assigned to more than one public category without crashing. Category labels are shown correctly as separate links and are no longer incorrectly treated as searchable product text, improving the shopping search experience.
Original PR description
This commit fixes an issue when there are several public categories on a single product. Categories are shown side-by-side under product name in the search bar. This commit also fixes the issue where…
This commit fixes an issue when there are several public categories on
a single product. Categories are shown side-by-side under product name
in the search bar.
This commit also fixes the issue where the `Category:X` text is matched
and highlighted whereas the search test is not used to match the product
categories.
Steps to reproduce :
- Install eCommerce
- Add several eCommerce Categories to a product
- Go to shop
- Search for the product in the searchbar
- Traceback
Current Behavior :
- Traceback when generating the results in the quick search bar.
It's not expected to have several categories in the current
implementation.
- If all products have a unique category, then the text in
`Category:X` is matched and highlighted.
Desired Behavior :
- No traceback
- When there are multiple categories, an extra link should be
present on each category rather than a unique link on all
categories.
- The product categories don't have to be matched.
Related PR: #79258
task-2680726
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr