- Oct 10, 2022
-
-
Martin Trigaux authored
closes odoo/odoo#102902 Related: odoo/enterprise#32633 Signed-off-by:
Martin Trigaux (mat) <mat@odoo.com>
-
Victor Feyens authored
* clean and improve docstrings in orm * fix typos found with codespell * rely on the Environment class docstring instead of doc content (and therefore move part of the doc inside the class docstring) closes odoo/odoo#102896 Related: odoo/documentation#2798 Signed-off-by:
Victor Feyens (vfe) <vfe@odoo.com>
-
Mathias Mathy (MAMA) authored
When a warehouse is renamed, associated route's name shall be renamed accordingly. As previously, the call to 'route.write()' in method '_update_name_and_code' was done after the 'super().write()', there was no way to remember the old name of the warehouse, and the 'replace' was so uneffective. The effectivenes of the replace is reestablished by doing the 'super().write' after the call to '_update_name_and_code', however, it breaks the method '_get_sequence_values' because it expects the name and code to be already written. That's why the optional parameters 'name' and 'code' are added to this last method. Task : 2985735 closes odoo/odoo#102456 Signed-off-by:
Arnold Moyaux (arm) <arm@odoo.com>
-
luvi authored
This commit fixes the behavior of the website app when creating content. Since commit (1), once a new record was created, it was no longer redirected to the correct page. Now, this behavior is reintroduced and works as expected. (1): https://github.com/odoo/odoo/commit/916a5bebb3e74047a66503ddc59299540c252831 closes odoo/odoo#102883 Signed-off-by:
Quentin Smetz (qsm) <qsm@odoo.com>
-
clesgow authored
Adapts the layouts of the immediate production and the production's backorder to match the new grid css for groups. Part of task-2985735 closes odoo/odoo#102881 Signed-off-by:
William Henrotin (whe) <whe@odoo.com>
-
Pierre Masereel authored
When an electronic payment is done in the POS, the payment lines contains the status of the electronic payment and the corresponding button to perform actions. We are now correctly display those informations. closes odoo/odoo#102866 Signed-off-by:
Masereel Pierre <pim@odoo.com>
-
mafo-odoo authored
Problem: If you have a customer assigned to an invoice/quotation without an e-mail address and then share a payment link with the customer. If the customer clicks on 'Pay', he won't be redirected to Stripe's checkout page. He'll get instead 'Invalid e-mail address: False' (see the image attached). Explanation: When there is no e-mail address defined, Odoo sends 'False' to Stripe but Stripe sees it as the e-mail address which is indeed Invalid. To solve the issue we replace False by None for the email value of a customer without email address. opw-3007866 closes odoo/odoo#102859 X-original-commit: 647a5fd7 Signed-off-by:
Antoine Vandevenne (anv) <anv@odoo.com> Signed-off-by:
Fockedey Martin (mafo) <mafo@odoo.com>
-
Anna Janiszewska authored
closes odoo/odoo#102858 X-original-commit: 7ceea15c Signed-off-by:
William Braeckman (wbr) <wbr@odoo.com>
-
pedrambiria authored
Before this commit: if an event's attendee didn't have a state, it couldn't get synced with Google. The solution is first to set a default value for it. opw-2915661 closes odoo/odoo#102857 X-original-commit: 89b53744c668183913b8a188730bd350fe778807 Signed-off-by:
Arnaud Joset <arj@odoo.com> Signed-off-by:
Pedram Bi Ria (pebr) <pebr@odoo.com>
-
Romain Derie authored
Commit [1] introduced a mismatch in tags, `<xpath>` is closed with `</t>`. [1]: https://github.com/odoo/odoo/commit/85905934c2ad2507cfc6f74428db61ac97a3bc41 closes odoo/odoo#102856 Signed-off-by:
Quentin Smetz (qsm) <qsm@odoo.com>
-
Bruno Boi authored
In legacy, an m2x autocomplete would not display extra lines received from the server inside the dropdown menu. This commit reintroduce that behavior as it was lost in the wowl conversion. closes odoo/odoo#102847 Signed-off-by:
Mathieu Duckerts-Antoine <dam@odoo.com>
-
luvi authored
Since o_form_view class was not placed on the right element, as the form is displayed in a dialog, some styles were not applied in x2Many dialogs using a form view. Now, the selector matches all cases and dialogs will be stylized as expected, since the class is placed on the dialog container instead of the first div. Now, we are consistent both for dialogs and standard form views. Tests have been adapted to work as expected. closes odoo/odoo#102834 Signed-off-by:
Michaël Mattiello <mcm@odoo.com>
-
Didier (did) authored
Current code can't work since session doesn't contain partner_id. task-3010650 closes odoo/odoo#102617 Signed-off-by:
Alexandre Kühn (aku) <aku@odoo.com>
-
Horacio Tellez authored
Before this commit a constraint between the `ir_ui_view` and `payment_provider` view made impossible for providers to be uninstalled. After this commit the constraint is correctly treated. A similar issue is found on a constraint on the `payment_custom` module. To fix this and future possible problems we added the possibility to modify the way providers are uninstalled following each provider needs. Task - 3002532 closes odoo/odoo#102265 Related: odoo/documentation#2799 Signed-off-by:
Antoine Vandevenne (anv) <anv@odoo.com>
-
Julien Mougenot authored
In PR https://github.com/odoo/odoo/pull/101763 the page_kanban template in website has been changed because it was thought that the xpath was meant to be inserted in the default slot. However this wasn't the case (we want it applied to the Layout) so it crashed the view. This commit restores the proper xpath. closes odoo/odoo#102842 Signed-off-by:
Romain Derie (rde) <rde@odoo.com>
-
Romeo Fragomeli authored
The field was not correctly aligned because the invisible rule was not the same on the field and the sibling's DIV. So in some case, we can have an empty DIV present with no label (e.g. when `is_log = false` and `composition_mode = mass_mail`). Note that now with grid, we need two filled columns otherwise we will have a shift for the next following labels/fields, because grid will try to fill the empty space. Steps to reproduce: * Open Helpdesk * Select a Team * Select the list view * Check a row (line) * Click on "Action" menu * Click on "Send Email" => BUG closes odoo/odoo#102840 Signed-off-by:
Adrien Dieudonné (adr) <adr@odoo.com>
-
Mathieu Duckerts-Antoine authored
closes odoo/odoo#102839 Signed-off-by:
Michaël Mattiello <mcm@odoo.com>
-
sofiagvaladze authored
One should be able to delete time off from the calendar view in validate and refuse states. task - 2857233 closes odoo/odoo#102836 Signed-off-by:
Kevin Baptiste <kba@odoo.com>
-
Victor Piryns (pivi) authored
Current behaviour: Currently when settling an account in a POS session, in Saudi Arabia, there is QR code on the receipt and a title "Simplified Tax Invoice", which should not be present on settlement Expected behaviour: Receipts generated from a settlement in Saudi Arabia localisation shouldn't generate a QR code and a tax title. Steps to reproduce: - install the modules: `l10n_sa`, `l10n_sa_pos`, `settle_due` - Switch to the Saudi Arabia company - Enter POS and create at least 2 payment method: - Cash: Identify Customer = false, Journal = Cash - Customer Balance: Identify Customer = true, Journal = empty - Create a new POS Session, just add "Customer Balance" to payment methods, the rest of settings are as default (might need to add "Customer Invoices" to the journal of the session) - Start a new session, find a customer with some "Amount Due" and click on the value, choose one of the payment methods - On the payment screen choose "Customer Balance", now you should have 2 payment lines, one is the payment methods for settling, the other is the customer balance with a negative value. - When validating, the receipt has a QR code and Invoice title, when it shouldn't. Reason for the problem: There is currently no state that differentiate between a normal order and a settlement. Fix: Implement a settlement state (computed) in the localistation order model. Add the state to the data that goes to the templating engine. Add conditional rendering for the templates related to the QR code and the "Simplified Tax Invoice" title. Affected versions: - 15.0 - saas-15.2 - saas-15.3 - 16.0 - master opw-2976267 closes odoo/odoo#102833 X-original-commit: 0b04230d3c5e7fc1bc83340ec2fca9cf646cbc60 Signed-off-by:
Piryns Victor (pivi) <pivi@odoo.com> Signed-off-by:
Masereel Pierre <pim@odoo.com>
-
Ahmed Khalaf (ahkh) authored
This commit updates some tooltips in workcenters and operations forms ENT PR: odoo/enterprise#32519 closes odoo/odoo#102672 Signed-off-by:
Arnold Moyaux (arm) <arm@odoo.com>
-
yhu-odoo authored
1. Except for registering components, the portal should be readonly 2. Don't open sm form when click it. closes odoo/odoo#102637 Signed-off-by:
Arnold Moyaux (arm) <arm@odoo.com>
-
Sébastien Theys authored
Form view has multiple containers that are exclusive, before this commit switching from one container to the other would lose all current chatter state. closes odoo/odoo#102636 Related: odoo/enterprise#32605 Signed-off-by:
Alexandre Kühn (aku) <aku@odoo.com>
-
Mathias Mathy (MAMA) authored
Simplify the tooltips for 'Security Lead Time for Purchase' and 'Days to Purchase' in the 'Advanced Scheduling' part of Inventory configuration. Task : 2985735 closes odoo/odoo#102577 Signed-off-by:
Arnold Moyaux (arm) <arm@odoo.com>
-
Odoo's Mergebot authored
Purpose ======= Convert the remaining legacy views in OWL. Before this PR, the list and form views are still in legacy in Project Sharing feature. The goal of this PR is to convert those views to have all views in OWL in Project Sharing. Details implementation ---------------------- - Convert the list view in OWL - Convert the chatter portal in OWL to be able to convert the form view in OWL - Convert the form view in OWL and integrate the chatter into it. - Review the assets used in Project Sharing to reduce the size of the assets since all components and views existing in the backend are not used (only the list, kanban and form views are used) - Review the rows attribute set on `textarea` HTML element in`TextField` to be able to altered it with a props. - Change the `FileInput` component to be able to override it to be able to use it when the route is different than the one set by default. - Fix the `useInputField` hook to be able to use the `TextField` component without any `record` set on its props (since this prop could be optional). task-2947516 closes odoo/odoo#102130 Signed-off-by:
Laurent Stukkens (ltu) <ltu@odoo.com>
-
Horacio Tellez authored
If `payment_custom` is installed before `account`, not bank account information is set up and the `pending_msg` remains `False`. This implies that no pending message is shown on the portal after transaction confirmation. After this commit, if `payment_custom` is installed before the `account` module, then the pending message falls back to the default message defined in the `payment` module. Task - 3000442 closes odoo/odoo#101593 Signed-off-by:
Antoine Vandevenne (anv) <anv@odoo.com>
-
Alexandre Kühn authored
*: mail, website_livechat This commit adds new option in Livechat Button visibility "Show with notifcation", which allow to see livechat button and also display a customizable floating text next to button. This text appears 1 second after the livechat button become visible. Task-2937993 closes odoo/odoo#100689 Signed-off-by:
Louis Wicket (wil) <wil@odoo.com>
-
Tiffany Chang (tic) authored
Followup to inventory back2basics task 2882539 - order stock.move.line tree (Moves History) view by "id desc" for better performance (prev: create_date is not indexed) - order stock.valuation.layer tree (Valuation) view by "id desc" for better performance (prev: date is not indexed) - hide "Moved Quantity" column when in current valuation (not at date) - remove the action: "Set" and print: "Count Sheet" from stock.quant.view when not in "Inventory Adjustment" related view - Fix "Inventory At Date"/"Valuation At Date" button visibility issue that came up due to OWL refactoring - Don't show consumables in stock.valuation.layer (Valuation) report view action (forgot to include domain when creating new action) - Add stock.move menuitem back in under "reporting" in debug mode since this view isn't accesible anywhere else and it is used a lot for qty forecasts by users - Add "Created By" (as "Done By") to stock.move.line history view for easier tracking of inventory adjustments closes odoo/odoo#100268 Task: 2965586 Signed-off-by:
Arnold Moyaux (arm) <arm@odoo.com>
-
xO-Tx authored
*: website_event, website_event_sale, website_forum, website_sale, website_sale_slides, website_slides, website_slides_forum This commit removes the remaining controllers that are no longer used since the use of form views on website new content dialogs (following the website in backend merge at [1] and the many iterations afterwards). With the website in backend work, a feature was lost for the creation of events: dummy tickets were created. This commit actually removes the feature for good. Events default values are managed by templates. Moreover there are links in frontend to edit the event when being allowed to edit it (event groups), notably when there is no ticket in registration page. So it makes no sense to create dummy tickets, without price, for 1000 seats. Those values are random so they will have to be edited. Better let users create real tickets if necessary, than editing and/or removing dummy tickets. [1]: https://github.com/odoo/odoo/commit/31cc10b91dc7762e23b4bde9b945be0c4ce3fe3b task-2687506 closes odoo/odoo#99042 Signed-off-by:
Quentin Smetz (qsm) <qsm@odoo.com> Co-authored-by:
qsm-odoo <qsm@odoo.com>
-
Arnold Moyaux authored
Use case to reproduce: - Create a new db - Go to warehouse and create a new one. Expected behavior (same than enable location options from settings): - Internal location has been enable - It's possible to create locations It happens because during the warehouse create call, the multi warehouse and multi locations groups are set. However `res.config.settings` contains a hook on `set_values` that enable some views and internal location. Write directly on the groups won't go throuhg this code. closes odoo/odoo#102828 Signed-off-by:
William Henrotin (whe) <whe@odoo.com>
-
Romain Estievenart authored
In 15.3, the width was applied on `o_form_sheet_bg`. As the form view has been refactored in 16, we have to apply it on the new parent `o_form_view_container`. We also restore the chatter width to the same value as in 15.3: ```scss .o_FormRenderer_chatterContainer { &.o-aside { width: $o-chatter-min-width; } } ``` Steps to reproduce: - Open Helpdesk on screen at 1534x657 - Open a vip support - Unfold 'Done' - Click on 'Ugly Chair', the chatter take a lot of space => bug Steps to reproduce - Open Sales - Open a quotation - Switch between Order lines, Other info, Customer Signature notebook tabs a flicker occurs => bug closes odoo/odoo#102781 Signed-off-by:
Adrien Dieudonné (adr) <adr@odoo.com>
-
Jacky (trj) authored
- Gift cards can now be sent alongside the receipt via mail in the Receipt Screen. - The gift card report no longer show n² gift cards - Properly download all PDF files for the gift cards when there are multiple gift card programs closes odoo/odoo#102676 Signed-off-by:
Masereel Pierre <pim@odoo.com>
-
Xavier BOL (xbo) authored
Before this commit, the assets used in project sharing takes almost all assets in `web.assets_backend`, this way is not a good idea since only the kanban view and list are used and the chatter is not the backend one. So the assets could be filtered to minize the size of the bundle for project sharing to also reduce the loading when the user goes to project sharing feature. This commit reviews the assets used in the project sharing to reduce the size. task-2947516
-
Xavier BOL (xbo) authored
Before this commit, the form view in project sharing was always in legacy. Moreover, in that view, the chatter used is the portal one and so it is also a legacy widget. This commit converts the form view and then convert the chatter in OWL to be able to correctly compile and add the chatter in the form view. Also, some styling has been done to remove the overflow. Only the overflow on the y axis in the chatter can be scrolled on the page. task-2947516
-
Xavier BOL (xbo) authored
Before this commit, the `FileInput` component can be used with another route only if the route has the same params than the default one. For instance, the portal chatter route does not have the same params name and so, the component cannot be used. This commit refactors the component to easily override the component to be able to use it in each case. task-2947516
-
Xavier BOL (xbo) authored
Before this commit, the rows attribute given on the TextField component was always 2, it is not possible to alter it without overriding the component. This commit adds a props to be able to update the rows with a prop called `rowCount` and this prop can be set via `rows` attribute set on the field. task-2947516
-
Xavier BOL (xbo) authored
Before this commit, when a component using the `useInputField` hook (for instance `TextField`) and the `record` is not given in its props, the hook will crash since it assume the `record` is always defined. However, the props definition the `record` is optional. This commit checks if `record` is defined in the component before using it to be sure to avoid any crash because it is not defined. task-2947516
-
Xavier BOL (xbo) authored
This commit converts the list view used in project sharing in OWL and remove the legacy definition. task-2947516
-
oco-odoo authored
closes odoo/odoo#102674 Signed-off-by:
Josse Colpaert <jco@odoo.com>
-
rhe-odoo authored
It was possible to sell gift cards without mail template or report link to the gift card program. Thus, it was impossible to get the info related to the card unless you have backend access rights. We now make sure the gift card program have a template and a report when starting the session. closes odoo/odoo#102613 Signed-off-by:
Masereel Pierre <pim@odoo.com>
-
William Braeckman authored
Prior to this commit the base_unit_price was computed using the price of the template instead of the list price displayed on the eCommerce, so it sometimes made no sense when compared to another currency. It will now be converted properly and use the list_price instead of template price to compute the base_unit_price. Some other issues with the base_unit_price display in the form view have also been fixed (mainly mobile stuff) TaskId-3006015 closes odoo/odoo#102543 Signed-off-by:
William Braeckman (wbr) <wbr@odoo.com>
-