Wednesday, July 7, 2021
28 changes · master
New functionality added to Odoo
Users can now create direct message conversations with multiple people instead of only one-on-one chats. This makes team coordination easier by allowing small group discussions directly within Odoo Mail/Discuss.
Original PR description
This commit adds feature to create grouped direct messages task-id: 2360934 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
Enhancements to existing features
Internal event managers can now more easily identify and manage unpublished event rooms, exhibitors, sponsors, agendas, and events. Unpublished items are consistently shown after published items with clear visual indicators, while remaining hidden from regular portal visitors where appropriate.
Original PR description
PURPOSE
Improve the management of non-published event subrecords for internal users.
SPECIFICATIONS
In this task we did 3 changes
1) In Community section of any event non-publish room is not available. Here
we add unpublished rooms with tag, just like shop with opacity.
2) Before this commit unpublished exhibitors are mixed with the published ones
with random position. After our merge all unpublished exhibitors are shown at
the end of list and not mixed with published ones. Moreover display of exhibitors
is improved to better find unpublished one.
3) In agenda section only unpublished tags have blurry effect and except that
whole section is same as published ones. We add blurry effect for whole
unpublished agenda. Moreover this we added this blurry effect for main event
section, which looks more systematic..
LINKS
Task ID-2346612Resolved issues and error corrections
The Live Chat support page was failing to load because it still pointed to an outdated file location. This fix updates the Live Chat setup so customers and staff can access the support route without a browser error.
Original PR description
Before this commit, when arriving on the route /im_livechat/support/1, there was a crash in the console becauase boot.js was not found. This was because the file has been moved, and im_livechat has not been adapted After this commit, the route /support correctly works 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
This commit changes the warning log for Selection fields that states that the hook could not go through the ORM for the deletion at uninstall (because of some business error) and that it had to bypass the ORM (aka pure sql delete) and turns it into a runbot-level log, meaning that it's technically a warning but the runbot won't fail because of it. This is done because for the install/uninstall tests it shows up as an actual failure but it is not as it is non-blocking, and 99.9% of devs
Original PR description
This commit changes the warning log for Selection fields that states that the hook could not go through the ORM for the deletion at uninstall (because of some business error) and that it had to bypass the ORM (aka pure sql delete) and turns it into a runbot-level log, meaning that it's technically a warning but the runbot won't fail because of it. This is done because for the install/uninstall tests it shows up as an actual failure but it is not as it is non-blocking, and 99.9% of devs won't ever see this warning on runbot since it triggers on module uninstall anyway. Forward-Port-Of: odoo/odoo#73291
Event-related website menus are now consistently linked to event menu records, making them easier to manage from the backend and when edited on the website. The update also cleans up related menu code and reorganizes tests without changing the intended user experience.
Original PR description
In website_event some event-specific frontend menus are not linked to ``website.event.menu`` like track or exhibitor sub-modules menus. This comes from initial implementation of ``website.event.menu`` that was available only for ``website_event_track``. Using ``website.event.menu`` eases menu management as it allows to have an object making a link between the event and the website menu. Notably when checking / unchecking in backend submenus it eases management. It also eases management when people manually edit menus from frontend as otherwise we have to manually manage ``ir.ui.view`` based on some naming manipulation. Task ID-2577079
Odoo now shows a more user-friendly default message when an incoming email cannot be delivered. The update also improves how empty email content is detected, reducing confusing or unwanted formatting in mail-related workflows.
Original PR description
Followup of 7ae1b4622c6743e28deca12476d6e70375c9417e
City searches can now use zip codes as well as city names, making it easier to pick the correct city when multiple places have similar names. City results also show the zip code in parentheses for clearer identification.
Original PR description
When having cities with similar name it may quickly be difficult to find the right one. Adding zip code to name search helps finding it more easily. IN order to match this new _name_search we update name_get accordingly and display the zip code between parenthesis. Task ID-2525738
Event pages now use space more efficiently by reducing extra padding, centering menu items, and allowing them to wrap below the header area when needed. This helps prevent menu items from overlapping the registration button and improves the page layout for visitors.
Original PR description
Remove padding from event name, and center menu items, purpose is to reduce lost space Make menu items wrap and move to the bottom to avoid having them overlap with the register button. Shorten the name of the "OpenWood Collection Online Reveal" event to "OpenWood Collection Reveal", because otherwise it would usually take two lines and would not look good. Task-2524708 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Timesheets app is easier to analyze and navigate with new graph and pivot reporting options, clearer menu naming, and a simplified settings path. The app icon is also aligned with the Enterprise version for a more consistent experience.
Original PR description
The timesheet_grid icon changes when enterprise is present. This changes the icon from base to the one from enterprise. Generic improvements of the timesheet app: - Adds pivot and graph view to 'My Timesheets' - Adds a graph view to 'All Timesheets' - Rename 'Timesheet' menu to 'Timesheets' - Remove unused submenu for configuration, directly leads to settings now. Task ID: 2531317 Relates to odoo/enterprise#19101
Helpdesk screens, menus, and help text were cleaned up to make ticket management clearer and less repetitive. SLA partner ordering was aligned with ticket behavior, and time entry was simplified into a single field to reduce confusion for support teams.
Original PR description
In General: - Remove redundant 'Ticket' from menuitems and field names - Improve form and tree views - Improve help messages Ticket SLA: - Match res.partner order with the one on the helpdesk tickets Task ID: 2513006
The Timesheet experience is streamlined by removing an app preview menu and improving validation screens. Managers can create and validate entries more easily, use graph and pivot views, and rely on corrected Last Week/Last Month shortcuts and clearer reminder messages.
Original PR description
Remove Timesheet App menu Generic improvements to timesheet app: - Allow creating lines from 'Validate' views - Add graph and pivot view to 'Validate' views - Fix some texts in timesheet reminder templates - Change 'Last Week' and 'Last Month' menus not really taking you to the timesheets from last week/last month - Add server action to be able to validate timesheets from any timesheet view Task ID: 2531317 Relates to odoo/odoo#72336
The Event Twitter Wall feature now aligns with updated event website menu management. This helps keep event-related website menus more consistent and easier to manage for users working with event pages.
Original PR description
See community PR for more details.
The Planning app settings and templates were updated to make setup and day-to-day use clearer for users. This helps teams onboard more easily and configure planning workflows with less confusion.
Original PR description
The purpose of the commit is to improve the usability and onboarding of the planning app. TaskID: 2531438
This fixes a timing issue that could load the wrong page when users quickly navigate or when the browser address changes during an action. Users should now land on the intended screen more consistently, reducing confusing navigation behavior.
Original PR description
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 change removes unstable checks from two web client tests so they no longer fail unpredictably during automated testing. It helps keep development and release validation more dependable without changing user-facing behavior.
Original PR description
Before this commit, two tests had undeterministic outcomes: they wanted to assert something in DOM was present at the same tiome as an owl rendering After this commit, the problematic asserts are removed and the tests behave deterministically. 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
PURPOSE When hover mouse on tour droplet, it shows tip info, but when click on app name(ex- expenses) and hover on tour droplet, it does not show text. SPEC Show tip info even after clicking over App name. TASK 2376278 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#66819
Original PR description
PURPOSE When hover mouse on tour droplet, it shows tip info, but when click on app name(ex- expenses) and hover on tour droplet, it does not show text. SPEC Show tip info even after clicking over App name. TASK 2376278 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#66819
PURPOSE When editable listview has sequence field with handle widget and user edits row it is displayed with white background, while user can not change it in edit mode so it should be displayed with grey background SPEC The sequence field should be displayed with grey background in editable listview in edit mode. TASK 2507971 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#69371
Original PR description
PURPOSE When editable listview has sequence field with handle widget and user edits row it is displayed with white background, while user can not change it in edit mode so it should be displayed with grey background SPEC The sequence field should be displayed with grey background in editable listview in edit mode. TASK 2507971 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#69371
Step to reproduce: 1. On mobile devices, open the pos app and lunch a bar/restaurant session; 2. You can't navigate on floor screen => bug To fix that we allow scroll on mobile devices. Task ID: 2453679 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#72774
Original PR description
Step to reproduce: 1. On mobile devices, open the pos app and lunch a bar/restaurant session; 2. You can't navigate on floor screen => bug To fix that we allow scroll on mobile devices. Task ID: 2453679 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#72774
See odoo/odoo#71047 Forward-Port-Of: odoo/odoo#73328 Forward-Port-Of: odoo/odoo#72221
Original PR description
See odoo/odoo#71047 Forward-Port-Of: odoo/odoo#73328 Forward-Port-Of: odoo/odoo#72221
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#73132
Original PR description
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#73132
PURPOSE Curretnly, the link responsible for sharing the page on whatsapp (from social share snippet) is not working correctly. There are two main problems: - it works only for the mobile devices where WhatsApp is alreay installed - only the page title is being shared, not the page URL SPECIFICATION This PR fixes both the issues by changing the sharing URL for WhatsApp. The URL is now changed to 'https://wa.me/....' instead of using 'whatsapp://' protocol (see the official li
Original PR description
PURPOSE Curretnly, the link responsible for sharing the page on whatsapp (from social share snippet) is not working correctly. There are two main problems: - it works only for the mobile devices…
PURPOSE Curretnly, the link responsible for sharing the page on whatsapp (from social share snippet) is not working correctly. There are two main problems: - it works only for the mobile devices where WhatsApp is alreay installed - only the page title is being shared, not the page URL SPECIFICATION This PR fixes both the issues by changing the sharing URL for WhatsApp. The URL is now changed to 'https://wa.me/....' instead of using 'whatsapp://' protocol (see the official link[1] for more information). With this URL, if the WhatsApp is not installed on the device, it will provide user with the options to either download it or use WhatsApp Web, and if WhatsApp is installed, it will open the app. Also with the URL, we pass both page title and page URL within 'text' URL parameter, and the secure link will be automatically parsed and converted to hyperlink by the platform. [1] - https://faq.whatsapp.com/general/chats/how-to-use-click-to-chat/ TaskID-2557077 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#72838 Forward-Port-Of: odoo/odoo#72284
Currently, the hover property inconsistent with some content of the stat button. It happens because the content of the stat button contains the 'o_quick_editable' class in read-only mode which has the property cursor: default. so, this commit fixes the issue by overriding the CSS of the stat button in the read-only mode. TaskID-2479807 Forward-Port-Of: odoo/odoo#68775
Original PR description
Currently, the hover property inconsistent with some content of the stat button. It happens because the content of the stat button contains the 'o_quick_editable' class in read-only mode which has the property cursor: default. so, this commit fixes the issue by overriding the CSS of the stat button in the read-only mode. TaskID-2479807 Forward-Port-Of: odoo/odoo#68775
PURPOSE Entering random value in daterange widget manually and click outside should not throw traceback. SPEC If value entered manually is wrong then show warning toaster. TASK 2410523 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#73238 Forward-Port-Of: odoo/odoo#62716
Original PR description
PURPOSE Entering random value in daterange widget manually and click outside should not throw traceback. SPEC If value entered manually is wrong then show warning toaster. TASK 2410523 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#73238 Forward-Port-Of: odoo/odoo#62716
_prepare_transaction_request() introduced in 35a6c1867d8edc9b58c002a6ff6a63c35a0fc708 is only used for 'authOnlyTransaction' and 'authCaptureTransaction' transaction types. capture(), void() and refund() still build their own request parameters. Make this clearer by renaming _prepare_transaction_request() to _prepare_authorization_transaction_request(). Forward-Port-Of: odoo/odoo#73334
Original PR description
_prepare_transaction_request() introduced in 35a6c1867d8edc9b58c002a6ff6a63c35a0fc708 is only used for 'authOnlyTransaction' and 'authCaptureTransaction' transaction types. capture(), void() and refund() still build their own request parameters. Make this clearer by renaming _prepare_transaction_request() to _prepare_authorization_transaction_request(). Forward-Port-Of: odoo/odoo#73334
Due to odoo/odoo#51075 it's an error to assign the `_date_name` field on an empty recordset. ``` Traceback (most recent call last): File "/home/odoo/src/odoo/14.0/odoo/models.py", line 1582, in _fields_view_get arch_etree = getattr(self, '_get_default_%s_view' % view_type)() File "/home/odoo/src/odoo/14.0/odoo/models.py", line 1495, in _get_default_calendar_view self._date_name = dt AttributeError: 'project.phase' object attribute '_date_name' is read-only ``` Issue
Original PR description
Due to odoo/odoo#51075 it's an error to assign the `_date_name` field on
an empty recordset.
```
Traceback (most recent call last):
File "/home/odoo/src/odoo/14.0/odoo/models.py", line 1582, in _fields_view_get
arch_etree = getattr(self, '_get_default_%s_view' % view_type)()
File "/home/odoo/src/odoo/14.0/odoo/models.py", line 1495, in _get_default_calendar_view
self._date_name = dt
AttributeError: 'project.phase' object attribute '_date_name' is read-only
```
Issue observed on upgrade requests 2615 and 3121.
Co-authored-by: Christophe Simonis <chs@odoo.com>
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#73380…rent from MXN and don't generate cfdi. Mexican companies should always have their accounting in MXN. Community PR : odoo/odoo#73079 See odoo/enterprise#19245 See odoo/enterprise#19353 Forward-Port-Of: odoo/enterprise#19475 Forward-Port-Of: odoo/enterprise#19401
Original PR description
…rent from MXN and don't generate cfdi. Mexican companies should always have their accounting in MXN. Community PR : odoo/odoo#73079 See odoo/enterprise#19245 See odoo/enterprise#19353 Forward-Port-Of: odoo/enterprise#19475 Forward-Port-Of: odoo/enterprise#19401
Fix an issue making a button appear in the debug popup, when there is nothing to redirect to. Forward-Port-Of: odoo/enterprise#19473
Original PR description
Fix an issue making a button appear in the debug popup, when there is nothing to redirect to. Forward-Port-Of: odoo/enterprise#19473
Improvements made for the carryover in #3d7374 made a new popup template for it. But using the same name for the data key has caused a conflict with the debug popup for financial reports making it show twice in their views. Forward-Port-Of: odoo/enterprise#19472
Original PR description
Improvements made for the carryover in #3d7374 made a new popup template for it. But using the same name for the data key has caused a conflict with the debug popup for financial reports making it show twice in their views. Forward-Port-Of: odoo/enterprise#19472