Search
Navigate
Branch
Sunday, March 31, 2024
30 changes
5 changes
Miscellaneous changes
In 2024, Luxembourg has added two new fields in the monthly, quarterly, and annual reports: 769 and 770 (rate of 17%). These fields should be added in our reports too. Part of: task-3814151 See also: https://github.com/odoo/enterprise/pull/58837 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#160027 Forward-Port-Of: odoo/odoo#158016
Original PR description
In 2024, Luxembourg has added two new fields in the monthly, quarterly, and annual reports: 769 and 770 (rate of 17%). These fields should be added in our reports too. Part of: task-3814151 See also: https://github.com/odoo/enterprise/pull/58837 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#160027 Forward-Port-Of: odoo/odoo#158016
This reverts commit ed651c93ca23c25f7cc3431b62be8f131b3ac9b6. With that commit, the users will have to empty eas/endpoint fields in order to see the checkbox and then they'll see a usererror when trying to download the ubl file. We will fix it differently, showing the checkbox at all times (if edi format is set) and allowing to download the UBL file regardless of the eas/endpoint fields. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-
Original PR description
This reverts commit ed651c93ca23c25f7cc3431b62be8f131b3ac9b6. With that commit, the users will have to empty eas/endpoint fields in order to see the checkbox and then they'll see a usererror when trying to download the ubl file. We will fix it differently, showing the checkbox at all times (if edi format is set) and allowing to download the UBL file regardless of the eas/endpoint fields. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#160035 Forward-Port-Of: odoo/odoo#159553
Steps to reproduce: - Setup sendcloud shipping (shipping product 10-30KG) - Enable demo payment - On the website proceed to checkout (customizable desk) - Select sendcloud (Pay button is disabled) - Edit website and add terms and conditions - Now if you uncheck and recheck terms and conditions - Pay button is enabled although carrier is in error Fix: when reenabling the pay button we check that the carrier is ready but we only check if there's pickup point ensure that the shipping me
Original PR description
Steps to reproduce: - Setup sendcloud shipping (shipping product 10-30KG) - Enable demo payment - On the website proceed to checkout (customizable desk) - Select sendcloud (Pay button is disabled) - Edit website and add terms and conditions - Now if you uncheck and recheck terms and conditions - Pay button is enabled although carrier is in error Fix: when reenabling the pay button we check that the carrier is ready but we only check if there's pickup point ensure that the shipping method is avialable before enabling the pay button opw-3698804 Forward-Port-Of: odoo/odoo#159133
This error occurs when the user adds a new ``Working Schedule`` to the resource, switches to the two-week calendar view, removes all the existing ``Working Hours`` lines, and then attempts to add a new line under ``Working Hours.`` Steps to reproduce: - Install ``resource`` module - Settings -> Technical -> Resource -> Working Schedules - New -> Switch to 2 week calendar -> Remove all ``Working Hours`` lines - Click on Add a line Traceback: ```ZeroDivisionError: float division by zer
Original PR description
This error occurs when the user adds a new ``Working Schedule`` to the resource, switches to the two-week calendar view, removes all the existing ``Working Hours`` lines, and then attempts to add a…
This error occurs when the user adds a new ``Working Schedule`` to the resource, switches to the two-week calendar view, removes all the existing ``Working Hours`` lines, and then attempts to add a new line under ``Working Hours.``
Steps to reproduce:
- Install ``resource`` module
- Settings -> Technical -> Resource -> Working Schedules
- New -> Switch to 2 week calendar -> Remove all ``Working Hours`` lines
- Click on Add a line
Traceback:
```ZeroDivisionError: float division by zero
File "odoo/http.py", line 2252, in __call__
response = request._serve_db()
File "odoo/http.py", line 1828, in _serve_db
return self._transactioning(_serve_ir_http, readonly=ro)
File "odoo/http.py", line 1848, in _transactioning
return service_model.retrying(func, env=self.env)
File "odoo/service/model.py", line 134, in retrying
result = func()
File "odoo/http.py", line 1826, in _serve_ir_http
return self._serve_ir_http(rule, args)
File "odoo/http.py", line 1833, in _serve_ir_http
response = self.dispatcher.dispatch(rule.endpoint, args)
File "odoo/http.py", line 2058, in dispatch
result = self.request.registry['ir.http']._dispatch(endpoint)
File "odoo/addons/base/models/ir_http.py", line 222, in _dispatch
result = endpoint(**request.params)
File "odoo/http.py", line 740, in route_wrapper
result = endpoint(self, *args, **params_ok)
File "addons/web/controllers/dataset.py", line 38, in call_kw
return self._call_kw(model, method, args, kwargs)
File "addons/web/controllers/dataset.py", line 34, in _call_kw
return call_kw(request.env[model], method, args, kwargs)
File "odoo/api.py", line 458, in call_kw
result = getattr(recs, name)(*args, **kwargs)
File "addons/web/models/models.py", line 1081, in onchange
snapshot1 = RecordSnapshot(record, fields_spec)
File "addons/web/models/models.py", line 1168, in __init__
self.fetch(name)
File "addons/web/models/models.py", line 1183, in fetch
self[field_name] = self.record[field_name]
File "odoo/models.py", line 6671, in __getitem__
return self._fields[key].__get__(self, self.env.registry[self._name])
File "odoo/fields.py", line 1138, in __get__
self.recompute(record)
File "odoo/fields.py", line 1353, in recompute
apply_except_missing(self.compute_value, recs)
File "odoo/fields.py", line 1326, in apply_except_missing
func(records)
File "odoo/fields.py", line 1375, in compute_value
records._compute_field_value(self)
File "odoo/models.py", line 4984, in _compute_field_value
fields.determine(field.compute, self)
File "odoo/fields.py", line 102, in determine
return needle(*args)
File "addons/resource/models/resource_calendar_attendance.py", line 83, in _compute_duration_days
attendance.duration_days = 0.5 if attendance.duration_hours <= attendance.calendar_id.hours_per_day * 3 / 4 else 1
File "odoo/fields.py", line 1138, in __get__
self.recompute(record)
File "odoo/fields.py", line 1353, in recompute
apply_except_missing(self.compute_value, recs)
File "odoo/fields.py", line 1326, in apply_except_missing
func(records)
File "odoo/fields.py", line 1375, in compute_value
records._compute_field_value(self)
File "odoo/models.py", line 4984, in _compute_field_value
fields.determine(field.compute, self)
File "odoo/fields.py", line 102, in determine
return needle(*args)
File "addons/resource/models/resource_calendar.py", line 109, in _compute_hours_per_day
calendar.hours_per_day = calendar._get_hours_per_day(attendances)
File "addons/resource/models/resource_calendar.py", line 185, in _get_hours_per_day
return float_round(hour_count / float(number_of_days), precision_digits=2)
```
This commit implements a check for the variable ``number_of_days``. If the value of ``number_of_days`` is zero or not found, the function will return zero. This ensures that the function behaves appropriately in cases where the number of days is zero.
https://github.com/odoo/odoo/blob/5177e21aea68959eedc73e0034ed984992392dd7/addons/resource/models/resource_calendar.py#L185
sentry - 5108250957
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#159844When installing the module `account_check_printing`, it is possible that a MemoryError is raised during the computation of `_compute_check_number`. To avoid that, the `_auto_init` function is overridden to create the field through SQL. opw-3790729 Forward-Port-Of: odoo/odoo#159499
Original PR description
When installing the module `account_check_printing`, it is possible that a MemoryError is raised during the computation of `_compute_check_number`. To avoid that, the `_auto_init` function is overridden to create the field through SQL. opw-3790729 Forward-Port-Of: odoo/odoo#159499
21 changes
Enhancements to existing features
The Gantt view now makes task planning clearer by highlighting the current month when viewing schedules by month. This helps teams orient themselves faster and manage task dependencies with less confusion.
Original PR description
This PR brings some UX improvements in the gantt view in the context of task dependencies. task-2647326
4 changes
Resolved issues and error corrections
Luxembourg tax regulations changed in 2024, requiring two new fields (769 and 770) to be added to the tax reporting system. This update ensures the tax reports and PDF exports include these mandatory new fields, keeping the system compliant with current Luxembourg tax requirements.
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#59774 Forward-Port-Of: odoo/enterprise#58837
Code cleanup and technical improvements
This update streamlines how Odoo Enterprise manages light and dark color themes. It removes an older workaround that is no longer needed now that Studio fully supports dark mode, reducing complexity and improving maintainability without changing expected user behavior.
Original PR description
*: website_enterprise This commit removes unnecessary complexity to the color_scheme service. Most of those changes were introduced in commit (1) to improve the experience when navigating to Studio, since dark mode was not supported. After commit (2), Studio module supports dark mode fully, and the patch of the service was no longer necessary. This commit removes the need for the extra cookie 'configured_color_scheme', and simplifies the service once again. 1) https://github.com/odoo/enterprise/commit/fda6f9cc47b9f9849155032fc0c53983a561e15d 2) https://github.com/odoo/enterprise/commit/f71d2a04fdada581c2e23776883c6fda6a21b8da
Miscellaneous changes
With no demo data, the current user does not have a timezone set. As the default value of appointment_tz is based on that, it leads to an error. We now set manually the appointment_tz for the appointment type created. runbot-55570 runbot-55571 runbot-55572 runbot-55573 runbot-55574 Forward-Port-Of: odoo/enterprise#59737
Original PR description
With no demo data, the current user does not have a timezone set. As the default value of appointment_tz is based on that, it leads to an error. We now set manually the appointment_tz for the appointment type created. runbot-55570 runbot-55571 runbot-55572 runbot-55573 runbot-55574 Forward-Port-Of: odoo/enterprise#59737
Before this commit, if the end of a table appointment was ending the day after the start day, the appointment wouldn't be displayed. Fixing this, a new issue arises, if an appointment start the day before, showing it next day will create confusion since it will display the starting time of the previous day. To fix this we simply set the starting time to the start of the day. Forward-Port-Of: odoo/enterprise#59612
Original PR description
Before this commit, if the end of a table appointment was ending the day after the start day, the appointment wouldn't be displayed. Fixing this, a new issue arises, if an appointment start the day before, showing it next day will create confusion since it will display the starting time of the previous day. To fix this we simply set the starting time to the start of the day. Forward-Port-Of: odoo/enterprise#59612
Before this commit, when an action is loaded, the server is called to find all the information of the action, if the action is a server action kind, a new call to the server is executed to run the server action, the result of this running is a new action (close action or window action). Since [1], when a server action is found in the url, it will be executed to retrieve the window action when is the current action. If the server action is found in multiple places in the url, it will be exe
Original PR description
Before this commit, when an action is loaded, the server is called to find all the information of the action, if the action is a server action kind, a new call to the server is executed to run the…
Before this commit, when an action is loaded, the server is called to find all the information of the action, if the action is a server action kind, a new call to the server is executed to run the server action, the result of this running is a new action (close action or window action). Since [1], when a server action is found in the url, it will be executed to retrieve the window action when is the current action. If the server action is found in multiple places in the url, it will be executed each time it becomes the current action. For instance, /crm/12, will execute the server action crm to retrieve the window action at the first load, and the same server action will be executed again when clicking on the breadcrumb to go back to the multi-record view. Now, when an action is loaded, if the action is a server action, the server will execute the action directly and return the resulting action. This is to avoid a back and forward between the client side and the server side. Note that, this will also use the correct display name on the breadcrumb, the one of the window action. [1] https://github.com/odoo/odoo/commit/c63d14a0485a553b74a8457aee158384e9ae6d3f Forward-Port-Of: odoo/enterprise#59600
**Before this PR:** The permission panel was not being updated when its values changed, resulting in outdated values being displayed. **After this PR:** the permission panel now re-rendered to reflect the updated values correctly. **Task**-3792165 Forward-Port-Of: odoo/enterprise#59561 Forward-Port-Of: odoo/enterprise#58825
Original PR description
**Before this PR:** The permission panel was not being updated when its values changed, resulting in outdated values being displayed. **After this PR:** the permission panel now re-rendered to reflect the updated values correctly. **Task**-3792165 Forward-Port-Of: odoo/enterprise#59561 Forward-Port-Of: odoo/enterprise#58825
Before this commit: The generated XAF file while exporting the general ledger is missing the declaration of the accounts with no lines for the given time period but which have an opening balance. The file contains the information regarding an opening balance for an account that is never declared in the file. This leads to an error for some customers when they send the file to the agency. After this commit: All the accounts with an opening balance but no line for the time period are declared
Original PR description
Before this commit: The generated XAF file while exporting the general ledger is missing the declaration of the accounts with no lines for the given time period but which have an opening balance. The file contains the information regarding an opening balance for an account that is never declared in the file. This leads to an error for some customers when they send the file to the agency. After this commit: All the accounts with an opening balance but no line for the time period are declared in the appropriate section of the XAF file. opw-3567617 opw-3624000 Forward-Port-Of: odoo/enterprise#59639 Forward-Port-Of: odoo/enterprise#53532
Steps to reproduce: ------------------- 1. Create a first FSM task with an assignee (e.g. Mitchel Admin) and a planned date 2. Create a second FSM task with another assignee (e.g. Marc Demo) with the same planned date as in the first task 3. Create a third FSM task with both assignees (e.g. Mitchel Admin and Marc Demo) with again, the same planned date 4. Save the third task or change anything in it 5. A traceback occurs Fix: ------------------- In the computed method "_compute_planni
Original PR description
Steps to reproduce: ------------------- 1. Create a first FSM task with an assignee (e.g. Mitchel Admin) and a planned date 2. Create a second FSM task with another assignee (e.g. Marc Demo) with the…
Steps to reproduce: ------------------- 1. Create a first FSM task with an assignee (e.g. Mitchel Admin) and a planned date 2. Create a second FSM task with another assignee (e.g. Marc Demo) with the same planned date as in the first task 3. Create a third FSM task with both assignees (e.g. Mitchel Admin and Marc Demo) with again, the same planned date 4. Save the third task or change anything in it 5. A traceback occurs Fix: ------------------- In the computed method "_compute_planning_overlap()", the "overlap_mapping" dictionary is iteratively updated with the data of the tasks of the users which overlap with the current one. When there were multiple assignees, it was possible that overlap_mapping[task_id] did not contain the user_id key of the assignee yet, hence the KeyError. To prevent that error, we check whether the user_id key exists and if not, we set it to an empty dictionary that will be filled in afterwards. Tests: ------------------- To be consistent with tests from TestPlanningOverlap in project_enterprise, the same test suite was reproduced for FSM tasks in TestFsmPlanningOverlap. task-3812556 version-17.1 Forward-Port-Of: odoo/enterprise#59638 Forward-Port-Of: odoo/enterprise#58824
This reverts commit 55cba9f899be0f058834bcd81bd239547c9cebd6. The issue this intended to fix was rooted in the fact that no timesheets were created for public holidays, leading to the remaining hours shown in Timesheets & Planning analysis being wrong. This is no longer an issue starting from version 16.3, timesheets do get created, so any *planned* hours that fall on a holiday get subtracted by the corresponding effective hours from timesheets. opw-3509155 Forward-Port-Of: odoo/enterp
Original PR description
This reverts commit 55cba9f899be0f058834bcd81bd239547c9cebd6. The issue this intended to fix was rooted in the fact that no timesheets were created for public holidays, leading to the remaining hours shown in Timesheets & Planning analysis being wrong. This is no longer an issue starting from version 16.3, timesheets do get created, so any *planned* hours that fall on a holiday get subtracted by the corresponding effective hours from timesheets. opw-3509155 Forward-Port-Of: odoo/enterprise#59645
The product tracking is enabled by default in the demo data. Running the test without those data will break, as the 2 lines in the tour won't be grouped. runbot 54158 Forward-Port-Of: odoo/enterprise#59647
Original PR description
The product tracking is enabled by default in the demo data. Running the test without those data will break, as the 2 lines in the tour won't be grouped. runbot 54158 Forward-Port-Of: odoo/enterprise#59647
The wrong number was used for identifying the user to the Belastingdienst through SBR when submitting their Tax Report. This new field has to be added through a new module but will be correctly merged in master. opw-3786956 Forward-Port-Of: odoo/enterprise#59370 Forward-Port-Of: odoo/enterprise#58485
Original PR description
The wrong number was used for identifying the user to the Belastingdienst through SBR when submitting their Tax Report. This new field has to be added through a new module but will be correctly merged in master. opw-3786956 Forward-Port-Of: odoo/enterprise#59370 Forward-Port-Of: odoo/enterprise#58485
Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4: https://github.com/odoo/odoo/pull/153203 Part 5: https://github.com/odoo/odoo/pull/153425 Part 6: https://github.com/odoo/odoo/pull/153700 Part 7: https://github.com/odoo/odoo/pull/154054 Part 8: https://github.com/odoo/odoo/pull/154579 Part 9: https://github.com/odoo/odoo/pull/155073 Part 10: https://github.com/odoo/odoo/pull/155639
Original PR description
Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4: https://github.com/odoo/odoo/pull/153203…
Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4: https://github.com/odoo/odoo/pull/153203 Part 5: https://github.com/odoo/odoo/pull/153425 Part 6: https://github.com/odoo/odoo/pull/153700 Part 7: https://github.com/odoo/odoo/pull/154054 Part 8: https://github.com/odoo/odoo/pull/154579 Part 9: https://github.com/odoo/odoo/pull/155073 Part 10: https://github.com/odoo/odoo/pull/155639 Part 11: https://github.com/odoo/odoo/pull/156255 / https://github.com/odoo/enterprise/pull/58135 Part 12: https://github.com/odoo/odoo/pull/156869 Part 13: https://github.com/odoo/odoo/pull/158384 / https://github.com/odoo/enterprise/pull/59019 Community: https://github.com/odoo/odoo/pull/158916 This pull requests brings various improvements and fixes to Hoot and the Odoo unit test ecosystem. See the different commit messages for more details. Note: these changes are made in stable to avoid having to support multiple versions of the HOOT API. As such, these changes are intended to be strictly limited to unit tests as to not put the rest of the code base at risk. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/enterprise#59291
Changing the pricelist on a confirmed SO is now forbidden. It was done in a fsm test, but the test is working fine without the pricelist, so the pricelist creation and SO update has been removed. See also: https://github.com/odoo/odoo/pull/157742 Forward-Port-Of: odoo/enterprise#58744
Original PR description
Changing the pricelist on a confirmed SO is now forbidden. It was done in a fsm test, but the test is working fine without the pricelist, so the pricelist creation and SO update has been removed. See also: https://github.com/odoo/odoo/pull/157742 Forward-Port-Of: odoo/enterprise#58744
Before this commit, the test fails since 23 March 2024 because next week the hours changed (summer time). The problem is there if the timezone is not UTC. This commit ensures the whole test uses the same timezone and only UTC one to avoid having to manage summer/winter time in the test. runbot-60932 Forward-Port-Of: odoo/enterprise#59366
Original PR description
Before this commit, the test fails since 23 March 2024 because next week the hours changed (summer time). The problem is there if the timezone is not UTC. This commit ensures the whole test uses the same timezone and only UTC one to avoid having to manage summer/winter time in the test. runbot-60932 Forward-Port-Of: odoo/enterprise#59366
The term "Upsell" has a negative impact on customers in some countries. It has been changed to "Quotation" task_id: 3699064 Forward-Port-Of: odoo/enterprise#58645
Original PR description
The term "Upsell" has a negative impact on customers in some countries. It has been changed to "Quotation" task_id: 3699064 Forward-Port-Of: odoo/enterprise#58645
The aim of this commit is having a correct Partner VAT listing report. Before this fix, the report has a SQL query that uses the load_more_limit value as the limit. The issue was that we applied the limit on a set of 3 queries, as each of these query computes one column, the report gave us enough line but the last column was wrongly computed (as we exceed the limit after the second query). This means that we had an empty column. It was totally wrong. In the same time, other bugs were found. R
Original PR description
The aim of this commit is having a correct Partner VAT listing report. Before this fix, the report has a SQL query that uses the load_more_limit value as the limit. The issue was that we applied the limit on a set of 3 queries, as each of these query computes one column, the report gave us enough line but the last column was wrongly computed (as we exceed the limit after the second query). This means that we had an empty column. It was totally wrong. In the same time, other bugs were found. Report lines are by default ordered by using the res.partner order (based on the complete name), causing that when we generate the xml report, the groupby (from itertools) wrongly grouped lines as we don't sort these lines on the groupby key (vat number). To avoid this issue, we changed the groupby by using the one from odoo.tools. opw-3802689 opw-3766777 opw-3797584 opw-3791023 Forward-Port-Of: odoo/enterprise#59573 Forward-Port-Of: odoo/enterprise#59454
# [FIX] knowledge: remove the focus on click on anchors This commit fixes an issue where the focus of the user's mouse would be moved to the comment box when clicking on the corresponding anchor. This renders the edition inside of the anchors very hard to do. Now, we removed this behavior and you only trigger the focus when clicking on the comment box. Simplifying the edition of text inside of the anchors. # [FIX] knowledge: remove color superposition in anchors This commit fixes
Original PR description
# [FIX] knowledge: remove the focus on click on anchors This commit fixes an issue where the focus of the user's mouse would be moved to the comment box when clicking on the corresponding anchor. This renders the edition inside of the anchors very hard to do. Now, we removed this behavior and you only trigger the focus when clicking on the comment box. Simplifying the edition of text inside of the anchors. # [FIX] knowledge: remove color superposition in anchors This commit fixes an issue where multiple anchors intertwined inside the body would stack their background colour, rendering the text harder to read. Now, we removed the background colour of the anchors that are inside another one. This way there's no more colour stacking. task-3790314 Forward-Port-Of: odoo/enterprise#58146
Steps: - install time sheet module - click on start button - before clicking on start button,width is different - after clicking on start button ,width is different Issue: - the width is unstable,seems different before and after clicking on start button Cause: - The problem occurs because of height issue solution: - if we give the height to that class the problem will be solved task-3645747 Forward-Port-Of: odoo/enterprise#59571 Forward-Port-Of: odoo/enterprise#50100
Original PR description
Steps: - install time sheet module - click on start button - before clicking on start button,width is different - after clicking on start button ,width is different Issue: - the width is unstable,seems different before and after clicking on start button Cause: - The problem occurs because of height issue solution: - if we give the height to that class the problem will be solved task-3645747 Forward-Port-Of: odoo/enterprise#59571 Forward-Port-Of: odoo/enterprise#50100
When reserving a serial number on a rental order with pickings activated, Odoo will assign whatever serial number is chosen without checking if there's a quantity available. With this fix, it will check if the chosen serial are available before assigning them. Forward-Port-Of: odoo/enterprise#59559 Forward-Port-Of: odoo/enterprise#58968
Original PR description
When reserving a serial number on a rental order with pickings activated, Odoo will assign whatever serial number is chosen without checking if there's a quantity available. With this fix, it will check if the chosen serial are available before assigning them. Forward-Port-Of: odoo/enterprise#59559 Forward-Port-Of: odoo/enterprise#58968
[FIX] account_inter_company_rules: Fix inter-company invoicing issue This fix is to solve a bug that was introduced due to the new change to multi ids in the key of the analytic distribution where the existing code does not consider that and ends up trying to parse a bunch of comma-separated, string of ids. opw-3756270 Forward-Port-Of: odoo/enterprise#58675 Forward-Port-Of: odoo/enterprise#57159
Original PR description
[FIX] account_inter_company_rules: Fix inter-company invoicing issue This fix is to solve a bug that was introduced due to the new change to multi ids in the key of the analytic distribution where the existing code does not consider that and ends up trying to parse a bunch of comma-separated, string of ids. opw-3756270 Forward-Port-Of: odoo/enterprise#58675 Forward-Port-Of: odoo/enterprise#57159
Steps to Reproduce: - Set up a website for the helpdesk team. - Navigate to the website. - Observe redirection issues. Issue: - The configured website for the helpdesk team is not redirecting appropriately, leading to navigation issues. Cause: - get_client_action function is not getting the website which is linked with the helpdesk team, that's why it redirects to the default website. Solution: - Override open_website_url in helpdesk_website module and assign correct websi
Original PR description
Steps to Reproduce: - Set up a website for the helpdesk team. - Navigate to the website. - Observe redirection issues. Issue: - The configured website for the helpdesk team is not redirecting appropriately, leading to navigation issues. Cause: - get_client_action function is not getting the website which is linked with the helpdesk team, that's why it redirects to the default website. Solution: - Override open_website_url in helpdesk_website module and assign correct website_id in website_id parameter of get_client_action. task-3607646 Forward-Port-Of: odoo/enterprise#52630
This fix resolves an issue where the payment button would become enabled even when the shipping method had errors. When customers unchecked and rechecked the terms and conditions during checkout, the system would incorrectly allow them to proceed to payment without a valid shipping method selected. The fix ensures the payment button only becomes enabled when both terms are accepted AND a valid shipping method is available.
Original PR description
Steps to reproduce: - Setup sendcloud shipping (shipping product 10-30KG) - Enable demo payment - On the website proceed to checkout (customizable desk) - Select sendcloud (Pay button is disabled) - Edit website and add terms and conditions - Now if you uncheck and recheck terms and conditions - Pay button is enabled although carrier is in error Fix: when reenabling the pay button we check that the carrier is ready but we only check if there's pickup point ensure that the shipping method is avialable before enabling the pay button opw-3698804 Forward-Port-Of: odoo/odoo#159133
This update resolves a memory error that could occur when installing the check printing module. The fix optimizes how the system creates a required field during installation by using a more efficient database method instead of the standard computation process, ensuring smoother installations even with large datasets.
Original PR description
When installing the module `account_check_printing`, it is possible that a MemoryError is raised during the computation of `_compute_check_number`. To avoid that, the `_auto_init` function is overridden to create the field through SQL. opw-3790729 Forward-Port-Of: odoo/odoo#159499
Luxembourg tax regulations changed in 2024, requiring two new tax report fields (769 and 770) with a 17% rate to be added to monthly, quarterly, and annual tax reports. This update ensures Odoo's Luxembourg localization module remains compliant with current local tax requirements.
Original PR description
In 2024, Luxembourg has added two new fields in the monthly, quarterly, and annual reports: 769 and 770 (rate of 17%). These fields should be added in our reports too. Part of: task-3814151 See also: https://github.com/odoo/enterprise/pull/58837 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#159887 Forward-Port-Of: odoo/odoo#158016