Search
Navigate
Branch
Monday, April 1, 2024
17 changes
5 changes
Miscellaneous changes
…search **Issue Description:** Due to changes in field access rights verification as seen here: https://github.com/odoo/odoo/blob/494231e796b562162d3bfb19fc8ce7550657cf07/odoo/models.py#L5334-L5345 And the removal of sudo rights for CrmLead: https://github.com/odoo/odoo/blob/494231e796b562162d3bfb19fc8ce7550657cf07/addons/website_crm_partner_assign/controllers/main.py#L98 Attempting to open a search by domain with the `activity_date_deadline` field triggers a 403 error: "You do not have eno
Original PR description
…search **Issue Description:** Due to changes in field access rights verification as seen here: https://github.com/odoo/odoo/blob/494231e796b562162d3bfb19fc8ce7550657cf07/odoo/models.py#L5334-L5345…
…search **Issue Description:** Due to changes in field access rights verification as seen here: https://github.com/odoo/odoo/blob/494231e796b562162d3bfb19fc8ce7550657cf07/odoo/models.py#L5334-L5345 And the removal of sudo rights for CrmLead: https://github.com/odoo/odoo/blob/494231e796b562162d3bfb19fc8ce7550657cf07/addons/website_crm_partner_assign/controllers/main.py#L98 Attempting to open a search by domain with the `activity_date_deadline` field triggers a 403 error: "You do not have enough rights to access the fields 'activity_date_deadline' on Lead/Opportunity (crm.lead). Please contact your system administrator." **Steps to Reproduce:** 1. Install the `website_crm_partner_assign` module. 2. Assign Joel Willis a partner level (via the partner assignment tab in the `Contact` app). 3. Navigate to CRM, select an opportunity, and assign it to Joel Willis (using the assigned partner tab in the lead form). 4. Log in to the portal as Joel Willis, navigate to Opportunities, and click any filter on the activities date `Overdue / today / this week activities`. This action results in a crash. **Proposed Solution:** Our approach focuses on secure and efficient access to data, especially for sensitive fields like `activity_date_deadline` and `activity_ids.date_deadline`. We selectively apply higher permissions during search operations to ensure users can access crucial information without compromising data security. By carefully using higher permissions and applying internal rules after searches, we strike a balance between making data available for legitimate needs and upholding our security measures. opw-3703583 Forward-Port-Of: odoo/odoo#154653
Current behavior before PR: The `<br>` tags copied from external editing software's were remained unchanged. Desired behavior after PR is merged: Implement breaking element at `<br>` during HTML paste to adress unwanted `<br>` elements introduced by external editing software's or the OS. This ensures consistent and correct behaviour for all commands. Note that this change does not break `<li>`, `<blockquote>`, and `<pre>` elements. task-2936891 Forward-Port-Of: odoo/odoo#136
Original PR description
Current behavior before PR: The `<br>` tags copied from external editing software's were remained unchanged. Desired behavior after PR is merged: Implement breaking element at `<br>` during HTML paste to adress unwanted `<br>` elements introduced by external editing software's or the OS. This ensures consistent and correct behaviour for all commands. Note that this change does not break `<li>`, `<blockquote>`, and `<pre>` elements. task-2936891 Forward-Port-Of: odoo/odoo#136743
- 17.0 Steps to reproduce: - Open Project app and click on overflow menu of a project - Select project updates option - Try and create a new update document Issue: - The budget details text is just coming under activities which should be in profitability section. Cause: - Unset priorities of the inherited XML to cause files load before on another changing the orientation of display order and same Xpath for two inherited files. Solution: - Changing Xpath of one inherite
Original PR description
- 17.0 Steps to reproduce: - Open Project app and click on overflow menu of a project - Select project updates option - Try and create a new update document Issue: - The budget details text is just coming under activities which should be in profitability section. Cause: - Unset priorities of the inherited XML to cause files load before on another changing the orientation of display order and same Xpath for two inherited files. Solution: - Changing Xpath of one inherited view to accommodate for the order of display Task-3678808 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#149564
**Current behavior before PR:** Opening OXP template in mass mailing without installing website there are some background colors that became transparent. This issue is introduced by [1] commit. This issue occurs because the $bg-gradient variable referenced in the commit cannot be included within a file of web_editor. Additionally, it cannot use the o-website-value to retrieve its value. **Desired behavior after PR is merged:** Now it will show the background color of block without websi
Original PR description
**Current behavior before PR:** Opening OXP template in mass mailing without installing website there are some background colors that became transparent. This issue is introduced by [1] commit. This issue occurs because the $bg-gradient variable referenced in the commit cannot be included within a file of web_editor. Additionally, it cannot use the o-website-value to retrieve its value. **Desired behavior after PR is merged:** Now it will show the background color of block without website installed. [1]: https://github.com/odoo/odoo/pull/75680/commits/5c4ad451787a1a52824a046c9ae81b0e86a05a3b task-3688383 Forward-Port-Of: odoo/odoo#151704
Some tests on dynamic variants mechanism didn't pass on test without demo data due to odoo/odoo#143543. Forward-Port-Of: odoo/odoo#159818 Forward-Port-Of: odoo/odoo#159709
Original PR description
Some tests on dynamic variants mechanism didn't pass on test without demo data due to odoo/odoo#143543. Forward-Port-Of: odoo/odoo#159818 Forward-Port-Of: odoo/odoo#159709
8 changes
Miscellaneous changes
In 2024, Luxembourg added two new fields: 769 and 770. In addition to adding it to our reports, it is also necessary to add these in the PDF export file. Part of: task-3814151 See also: https://github.com/odoo/odoo/pull/158016 Forward-Port-Of: odoo/enterprise#59842 Forward-Port-Of: odoo/enterprise#58837
Original PR description
In 2024, Luxembourg added two new fields: 769 and 770. In addition to adding it to our reports, it is also necessary to add these in the PDF export file. Part of: task-3814151 See also: https://github.com/odoo/odoo/pull/158016 Forward-Port-Of: odoo/enterprise#59842 Forward-Port-Of: odoo/enterprise#58837
4 changes
Resolved issues and error corrections
This fix resolves an issue where LinkedIn follower counts were not being updated in social media streams. The problem was caused by using an outdated API parameter format when retrieving follower information from LinkedIn. The fix updates the parameter to the correct format required by the latest LinkedIn API version, ensuring accurate follower counts are displayed.
Original PR description
**Steps to reproduce:** - Install `Social Marketing` module - Add a LinkedIn stream and ensure stream already have some followers **Issue:** Followers count is not updated in the stream. **Cause:** Changed to API version 202401 in this commit: https://github.com/odoo/enterprise/commit/a6680edb9e7d91f6038d276f36d86aef07946fd9 Using deprecated parameter key (`CompanyFollowedByMember` instead of `COMPANY_FOLLOWED_BY_MEMBER`) in the API request when retrieving company followers. More info: [LinkedIn API doc](https://learn.microsoft.com/en-us/linkedin/marketing/community-management/organizations/organization-lookup-api?view=li-lms-2024-03&tabs=http#retrieve-organization-follower-count) opw-3798739 Forward-Port-Of: odoo/enterprise#59160
### Steps to reproduce: - Install **field service** app. - Go to **field service**, and convert the view to **Calendar**. - Click on a task and try to drag it. You **_can't_** drag and drop a task. ### Investigation: - the `date_start` option is `planned_date_start` https://github.com/odoo/enterprise/blob/dab59cb6dea28f13b6b984b19d844fc9ad6f2006/industry_fsm/views/fsm_views.xml#L91 - which is a **computed -readonly-** field https://github.com/odoo/enterprise/blob/a29e55f7ac02a0c2b34c9714
Original PR description
### Steps to reproduce: - Install **field service** app. - Go to **field service**, and convert the view to **Calendar**. - Click on a task and try to drag it. You **_can't_** drag and drop a task.…
### Steps to reproduce: - Install **field service** app. - Go to **field service**, and convert the view to **Calendar**. - Click on a task and try to drag it. You **_can't_** drag and drop a task. ### Investigation: - the `date_start` option is `planned_date_start` https://github.com/odoo/enterprise/blob/dab59cb6dea28f13b6b984b19d844fc9ad6f2006/industry_fsm/views/fsm_views.xml#L91 - which is a **computed -readonly-** field https://github.com/odoo/enterprise/blob/a29e55f7ac02a0c2b34c9714397c5a1322785833/project_enterprise/models/project_task.py#L31 - That's why, we can't drag the task. - The `planned_date_start` field was added because the `start_date_begin` field was **optional** and so to be able to view tasks with only a deadline a no start date, the field `planned_date_start` was added with the compromise of not being able to drag the task - The `planned_date_begin ` field is now **required** tho. and so no need to make such compromise as an fsm task will always have a start date `start_date_begin` opw-3750403 Forward-Port-Of: odoo/enterprise#59256 Forward-Port-Of: odoo/enterprise#58316
Adding the current list context to the loadAction call in case some element are needed For exemple the active_id was needed in the project task list view Task-3815748 Forward-Port-Of: odoo/enterprise#58929
Original PR description
Adding the current list context to the loadAction call in case some element are needed For exemple the active_id was needed in the project task list view Task-3815748 Forward-Port-Of: odoo/enterprise#58929
Following odoo/odoo#142007 - Fix an issue introduced by this change; - Remove a button now useless. Forward-Port-Of: odoo/enterprise#59205
Original PR description
Following odoo/odoo#142007 - Fix an issue introduced by this change; - Remove a button now useless. Forward-Port-Of: odoo/enterprise#59205
**Bug 1:** - Select a document and add Marc Demo as a follower - Use the 'View Document' link in the notification email to access the document. - The form view still has a button named 'Archive' instead of 'Move to trash'. However, the 'Archive' button moves the document to trash. This PR changes the string of button from 'Archive' to 'Move to trash' and the title of web ribbon from 'Archived' to 'Moved to trash' respectively. **Bug 2:** - Open the documens module. - Go to Config
Original PR description
**Bug 1:** - Select a document and add Marc Demo as a follower - Use the 'View Document' link in the notification email to access the document. - The form view still has a button named 'Archive'…
**Bug 1:** - Select a document and add Marc Demo as a follower - Use the 'View Document' link in the notification email to access the document. - The form view still has a button named 'Archive' instead of 'Move to trash'. However, the 'Archive' button moves the document to trash. This PR changes the string of button from 'Archive' to 'Move to trash' and the title of web ribbon from 'Archived' to 'Moved to trash' respectively. **Bug 2:** - Open the documens module. - Go to Configuration -> Workspaces - Click on the search view dropdown - The filters section still has a filter named 'Archived Workspace' instead of 'Moved to trash' even though it displays trashed workspaces. This PR changes the string of filter from 'Archived Workspace' to 'Moved to trash'. Task: [3787404](https://www.odoo.com/web#id=3787404&cids=2&menu_id=4720&action=333&active_id=10888&model=project.task&view_type=form) Forward-Port-Of: odoo/enterprise#59768 Forward-Port-Of: odoo/enterprise#58248
Steps to reproduce: - Install `documents` module - Ensure you have access to 2 companies (Co. 1 and Co. 2) - Enable both companies - Create a Folder A in Co. 1 - Create a Folder B in Co. 2 with Folder A as parent - Create a Folder C in Co. 1 with Folder B as parent - Put a file in each folder - Enable only Co. 1 - On left panel, select Folder A and unfold until Folder C appears Issue: The folder B is visible. Cause: When retrieving the folders to disp
Original PR description
Steps to reproduce: - Install `documents` module - Ensure you have access to 2 companies (Co. 1 and Co. 2) - Enable both companies - Create a Folder A in Co. 1 - Create a Folder B in Co. 2 with Folder A as parent - Create a Folder C in Co. 1 with Folder B as parent - Put a file in each folder - Enable only Co. 1 - On left panel, select Folder A and unfold until Folder C appears Issue: The folder B is visible. Cause: When retrieving the folders to display in the search_panel, we retrieve all the ancestors of the available folders to display the complete folder tree for all available folders. Solution: Change the name of the unauthorized folders to "Restricted Folder". opw-3701633 Forward-Port-Of: odoo/enterprise#59681 Forward-Port-Of: odoo/enterprise#58422
**Before this PR:** When user tried to delete an archived document from the activity view, it led to a traceback. This same traceback was also encountered when a user changed the workspace of a document from activity view. This issue arose because the 'activity renderer' tried to display records of all resIds obtained from activity data, including the record of the document currently in preview, which would be deleted already. Thus, leading to the aforementioned traceback. **After this
Original PR description
**Before this PR:** When user tried to delete an archived document from the activity view, it led to a traceback. This same traceback was also encountered when a user changed the workspace of a…
**Before this PR:** When user tried to delete an archived document from the activity view, it led to a traceback. This same traceback was also encountered when a user changed the workspace of a document from activity view. This issue arose because the 'activity renderer' tried to display records of all resIds obtained from activity data, including the record of the document currently in preview, which would be deleted already. Thus, leading to the aforementioned traceback. **After this PR:** The issue has been addressed by updating the behavior of the 'ActivityRenderer' to retrieve and display the updated activity records in order to ensure accuracy. Apart from that, the progress bar was not updated after the docs were deleted. This PR solves that issue by calling the 'load' method of activity model along with the 'rootParams', and then calling the 'notify' method to update the data correctly. Task: [3714544](https://www.odoo.com/web#id=3714544&menu_id=4722&cids=2&action=333&active_id=10888&model=project.task&view_type=form) Forward-Port-Of: odoo/enterprise#59740 Forward-Port-Of: odoo/enterprise#56357
**Steps to reproduce:** - Install `Social Marketing` module - Add a LinkedIn stream and ensure stream already have some followers **Issue:** Followers count is not updated in the stream. **Cause:** Changed to API version 202401 in this commit: https://github.com/odoo/enterprise/commit/a6680edb9e7d91f6038d276f36d86aef07946fd9 Using deprecated parameter key (`CompanyFollowedByMember` instead of `COMPANY_FOLLOWED_BY_MEMBER`) in the API request when retrieving company followers.
Original PR description
**Steps to reproduce:** - Install `Social Marketing` module - Add a LinkedIn stream and ensure stream already have some followers **Issue:** Followers count is not updated in the stream. **Cause:** Changed to API version 202401 in this commit: https://github.com/odoo/enterprise/commit/a6680edb9e7d91f6038d276f36d86aef07946fd9 Using deprecated parameter key (`CompanyFollowedByMember` instead of `COMPANY_FOLLOWED_BY_MEMBER`) in the API request when retrieving company followers. More info: [LinkedIn API doc](https://learn.microsoft.com/en-us/linkedin/marketing/community-management/organizations/organization-lookup-api?view=li-lms-2024-03&tabs=http#retrieve-organization-follower-count) opw-3798739 Forward-Port-Of: odoo/enterprise#59160
This update fixes a display issue where the last letter of project and task names was being cut off when shown in italic text in the timesheet grid view. The fix ensures adequate spacing is allocated for italic text so all characters display properly without truncation.
Original PR description
- saas-16.3 ### Steps to reproduce: -install the project and timesheet app. -open the project app, create a project, and add a task to it. -add a timesheet a week before from current date in the created task. -now open the timesheet app in grid view. -the created project and task are in italic font. -the last letter of the project and task is slightly cut. ### Issue: The last letter of the string is slightly cut in grid view. ### Cause: The dedicated space allowed for normal text is not sufficient for the Italic so the last letter was slightly cut. ### Solution: Provide enough space for italic string. Task-3749072 Forward-Port-Of: odoo/enterprise#57000
This update fixes an issue where line break tags copied from external editing software were not being properly handled when pasting content into the web editor. The fix ensures that unwanted line breaks are converted to proper paragraph breaks, providing a cleaner and more consistent editing experience while preserving important formatting elements like lists, quotes, and code blocks.
Original PR description
Current behavior before PR: The `<br>` tags copied from external editing software's were remained unchanged. Desired behavior after PR is merged: Implement breaking element at `<br>` during HTML paste to adress unwanted `<br>` elements introduced by external editing software's or the OS. This ensures consistent and correct behaviour for all commands. Note that this change does not break `<li>`, `<blockquote>`, and `<pre>` elements. task-2936891 Forward-Port-Of: odoo/odoo#136743
This update resolves a critical synchronization issue with Google Calendar that was causing the system to crash when syncing calendar events. The fix addresses a missing data field error that prevented users from properly syncing their Google Calendar with Odoo, restoring the functionality that worked in the previous version.
Original PR description
Description of the issue/feature this PR addresses:
Fyx sync with google calendar like in v15 PR: https://github.com/odoo/odoo/pull/125788
Current behavior before PR:
```
Traceback (most recent call last):
File "/odoo/src/odoo/http.py", line 643, in _handle_exception
return super(JsonRequest, self)._handle_exception(exception)
File "/odoo/src/odoo/http.py", line 301, in _handle_exception
raise exception.with_traceback(None) from new_cause
KeyError: 'entryPointType'
```
Desired behavior after PR is merged:
No key Error
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr