Daily updates from Odoo
Navigate
Branch
Tuesday, September 24, 2019
4 changes
Enhancements to existing features
This update simplifies navigation labels in the website learning area. User profile breadcrumbs no longer show an unnecessary Home entry, and course pages now label the main course link as Courses, making navigation clearer for learners.
Original PR description
- Remove the /home from the breadcrumb in user profile - And rename the Home (on a specific course) into "Courses" -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The map view documentation was updated to reflect a simpler way to define marker popup fields. It also documents new options to hide names and addresses, giving implementers clearer control over what users see in map markers.
Original PR description
Description of the issue/feature this PR addresses: * Task: https://www.odoo.com/web#id=2009017&action=327&model=project.task&view_type=form&menu_id=4720 * Pad: https://pad.odoo.com/p/r.998aaa524bca44f3f543deb4c3272719 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
Map views now show cleaner, more useful location popups, including better formatting and grouped markers when multiple records share the same location. Users can also activate and edit map views in Studio, making it easier to configure location-based workflows without developer help.
Original PR description
* Task: https://www.odoo.com/web#id=2009017&action=327&model=project.task&view_type=form&menu_id=4720 * Pad: https://pad.odoo.com/p/r.998aaa524bca44f3f543deb4c3272719
Resolved issues and error corrections
This fixes a crash that could occur on tablets when the top menu and systray contain many items, especially in apps with fewer main menu entries such as Contacts. Users can now load these apps and resize or rotate the screen without hitting an error caused by missing menu items.
Original PR description
When having a long systray (icons from different apps, mode debug, multi-company...) the resize of the window can trigger a crash for apps that have not too much top-level menus (e.g. Contacts). This…
When having a long systray (icons from different apps, mode debug,
multi-company...) the resize of the window can trigger a crash for apps
that have not too much top-level menus (e.g. Contacts).
This also happens when loading those apps.
Steps to reproduce (on an iPad, portrait):
* use a Runbot with all modules installed (12.0+)
* activate "debug mode"
* ensure that the menu/systray bar is quite full
* open the "Contacts" app
=> traceback with a "cannot call getBoundingClientRect of undefined"
error
The reason is that the resize's callback iterate over the systray/menu
items to find which one should be folded behind a "more" ("+") menu
item.
Sadly in some cases (combination of screen width, systray size, app's
number of menus) it can lead to a traceback.
This commit ensures that when looping for menu items, we don't try to
reach an non-existing item.
X-original-commit: odoo/odoo@d7bae0329990171710acf2d9c0d4d9579cba2c0e
Co-authored-by: Romeo Fragomeli <rfr@odoo.com>