Thursday, September 7, 2023
9 changes · master
Resolved issues and error corrections
Fixed how Point of Sale order dates are prepared so they use the format expected by the system. This helps prevent issues when retrieving or processing sales tickets, including restaurant orders, caused by incompatible date values.
Original PR description
Before this commit ================== Previously, the order date was being passed in the incorrect format: 'Fri Aug 04 2023 18:37:27 GMT+0530 (India Standard Time)'. Our code requires the format 'yyyy-MM-dd HH:mm:ss'." After this commit ================= Implemented changes to rectify the order date format, ensuring compatibility with 'yyyy-MM-dd HH:mm:ss'. This update includes adjustments to the processing flow to precise handling of order dates. task - 3451384
Calendar events that include properties fields can now be opened without causing an error. This improves reliability for users working with customized calendar records in Odoo.
Original PR description
Before this commit, in a calendar view with a properties field, a crash will be display when you click on an event. 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
The self-ordering kiosk now correctly shows the combo page header with steps and product names. This helps customers follow the ordering flow more easily and avoids confusion when selecting combo items.
Original PR description
Previously, header height in pages was managed by `kiosk_template.js` and in the various other components via props. This caused a bug in the `combo.xml` page, as the header with steps and product names was not displayed. Now the height of header, content and footer is managed entirely via the components and never via the template. This corrects the error in question.
Fixed an issue where automated server actions saved the display label of a selection option instead of its actual stored value. This prevents crashes when those actions update records, making automation more reliable for users.
Original PR description
Server actions that 'update the record' have a mechanism to allow users to easily select a selection value if the field they want to update is a selection field (instead of having to type the technical value directly). Before this commit, this mechanism incorrectly stored the selection's name instead of the value (e.g. 'Done' instead of '01_done'), making the write crash when the action was run.
This fixes an issue where Point of Sale could keep loading only products from previously restricted categories even after category restrictions were turned off. Stores using POS will now see the full expected product catalog when restrictions are disabled, reducing missing-product confusion during sales.
Original PR description
The products are not correctly loaded in the POS because of a bug regarding the `Restrict Categories` feature. Steps to reproduce: 1. Create a `pos config` with `Restrict Categories` set to: `categ1` and `categ2` 2. Disable `Restrict Categories` 3. Open the POS and notice that although all the categories are present in the category selector, only the products from `categ1` and `categ2` are loaded. Task: 3497308 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix restores an error-handling behavior that some older web requests still depend on. It helps ensure errors can be recognized as handled, reducing the risk of unnecessary error popups or disrupted workflows for users.
Original PR description
Previously we removed some code related to handling errors in legacy RPC, that would wrap errors in an object and give them an event that could be defaultPrevented to mark the error as handled, but this code is still needed. This commit restores it.
The auto-reconcile wizard now works even when users leave the start date blank. In that case, reconciliation starts from the earliest possible date, preventing unnecessary errors or manual date entry.
Original PR description
…in if not set In the auto-reconcile wizard, user should be able to let from_date empty, in this case we will auto-reconcile since date.min.
QIF bank statement uploads no longer fail when the file uses an encoding other than UTF-8, such as ISO-8859-1. The system now detects the file encoding automatically, making imports more reliable for users receiving statements from different banks or regions.
Original PR description
When uploading a QIF file, the UTF-8 encoding is assumed, which causes a traceback if a different encoding is used (e.g. ISO-8859-1). To solve the above, encoding is automatically detected. X-original-commit: 8f43bc558c16f67e394cb76fc3e4a7ea9128d585
Opening a Knowledge article from an embedded calendar view no longer crashes. This keeps calendar-based Knowledge content accessible and ensures article properties display correctly.
Original PR description
Since PR https://github.com/odoo/odoo/pull/114024, open a knowledge article from an embeded calendar view display a crash. Because the extension knowledge.ArticleItemsCalendarCommonPopover.body should use fieldInfo.name instead of fieldName. FielName is not defined anymore. Since Commit https://github.com/odoo/odoo/commit/29c7b23e22317ae06ec4052dd3edd9e2478e14ab, PropertiesField need the definition field (parent_id) to generate the separator.