Thursday, January 30, 2025
2 changes · saas-17.2
Resolved issues and error corrections
This fix prevents Odoo from totaling the same numeric field that users choose for grouping records. It avoids confusing or incorrect grouped results, making views such as Kanban more reliable for everyday analysis.
Original PR description
This commit fixes an issue where if the user applies a group by on an aggregatable field (an integer like color_index for example), this field is also registered as an aggregator in the webReadGroup call and this leads to nonsensical results by the orm. After this commit, the group by field is automatically excluded from aggregators so the issue cannot happen. task-4491839
The website partner map now continues to zoom correctly even when some partner records do not have saved latitude and longitude details. This prevents one incomplete or unresolvable address from blocking the map display for visitors.
Original PR description
The World Map view when you are on the "/partners" page doesn't zoom. This happens when any of the partners that are getting rendered doesn't have a location (longitude and latitude). Geocoder is then used to locate those addresses on the map. We use Promises, and when there is an error, we're not catching it where we are calling it from. The failed Geocode triggers the reject, which is not caught, and we're stuck in the await Promise. The zoom-in line never gets called. Steps to Reproduce on Runbot: Integrate the Google Place Map key via Settings -> Geolocation -> Google Place Map. Go to "/partners." Toggle on the world map view for the page via the editor. Ensure one partner on the page lacks a location. Go to the "map" view, and the map will not zoom in. opw-4319619