+
Skip to content

Tags: ursais/odoo

Tags

18.0-20250714

Toggle 18.0-20250714's commit message
[FIX] auth_totp_mail_enforce: rpc api keys only

task-4933992

17.0-20250714

Toggle 17.0-20250714's commit message
[FIX] web: fix progressbar field's input on firefox

Before this commit, the input of the progressbar field couldn't be
updated on firefox. It works on the other browsers by chance.
In the list renderer, we call `preventDefault` on enter keydown.
The event is first catch by the list renderer. This call is enough
to prevent "change" event to trigger but on chromium browsers it is
actually triggered (but should not). The progressbar field catches
it and saves the new value. On firefox, the "change" event is never
triggered.

The commit fixes the input by using the input field hook to make it
behave correctly.

task-4881210

closes odoo#215770

Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>

18.0-20250708

Toggle 18.0-20250708's commit message
[FIX] html_editor: replace <div> with baseContainer on paste

Before this commit:

- Visually empty <div> elements could be inserted during paste.
- These empty blocks created invisible spacing in the editor.
- External styles inside pasted <div> elements were not removed.
- The placeholder (`Type '/' for commands`) could not render correctly
  in those areas.

This regression was introduced in commit `odoo#196481`, which stopped replacing
blacklisted tags like <div> with <p>. As a result, cleanForPaste no longer
stripped inline styles from <div> elements.

After this commit:

- Non-empty <div> elements are now replaced with a valid baseContainer element.
- Empty <div> elements are automatically removed from pasted content.
- This restores the expected cleaning behavior and removes unwanted styles.

task-4805536

closes odoo#210797

Signed-off-by: David Monjoie (dmo) <dmo@odoo.com>

17.0-20250708

Toggle 17.0-20250708's commit message
[FIX] web_editor: prevent direct writing to history

This commit prevent direct write to history, also,
removes it from copy_data as it would fail anyway when trying to
write the history

closes odoo#217167

Signed-off-by: David Monjoie (dmo) <dmo@odoo.com>

18.0-20250630

Toggle 18.0-20250630's commit message
[FIX] stock_account: get singletone value within loop

I'm not sure how to reproduce right now. Clue: these modules are installed:
- sale_stock_margin
- stock_account

Other clue: user is going to an mrp.production order and clicking on "Set as done".

Some unknown combination of facts under this situation make multiple `sale.order.line` have to recompute their `purchase_price`. It happens that some product involved is measured in Units, while some other is measured in Kg.

At the end of the rabbit hole, the code ends up here, where there's a pretty obvious bug: a singleton value being extracted from a multi-record variable.

So, yes, this is probably the worse fix description ever. 😅 However, the bug is so obvious that I'm not sure I really need something more elaborate in this case. So, here's the fix!

@moduon MT-7556

closes odoo#211504

X-original-commit: 9ec7acf
Signed-off-by: Quentin Wolfs (quwo) <quwo@odoo.com>
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>

17.0-20250630

Toggle 17.0-20250630's commit message
[FIX] stock_landed_costs: preserve sign for vendor refunds in landed …

…cost

Before this commit, creating a landed cost from a vendor refund (move_type = 'in_refund')
incorrectly treated the refund amounts as positive, leading to an unintended increase
in stock valuation.

After this commit, the landed cost line amounts preserve the correct sign based on
the invoice type. If the source document is a refund (in_refund), the price_unit is
negated to properly reduce the stock valuation instead of increasing it.

closes odoo#216378

X-original-commit: 6aa19a9
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>

16.0-20250630

Toggle 16.0-20250630's commit message
[FIX] website: allow defaut value for data-for form field

Scenario:
- go to the /contactus page
- edit the subject field and set a default value then save

Result: the default value is not saved.

Reason: in 13.0, field default value had priority over data-for so an
issue was solved by b637a5e that if you
saved a form, the data-for would become the default for all the uses of
that form (so eg. a job position would be set for all job positions).

In 8d0a63f the priority was changed so
data-for has higher priority than the default value, that made the
prior fix unnecessary (just a nice to have, to not save the data-for as
default that would be overridden by another data-for).

The fix was reintroduced by ca433f3 but
it removes default value if there is a data-for.

Fix: remove the filling and removing of data-for value in edition: the
data-for is not shown in the editor (allowing us to set default) but has
the priority when rendering the field in non-editable mode. This is
mirroring what is already done for data-fill-with.

The added test steps, verify that the default value that is overridden
by a data-for is kept for type/email/text shown inputs.

Side note: this commit also remove useless data-fill-with="undefined"
attributes that are added when editing field. They shouldn't cause any
issue unless someone add a "undefined" field in the prefilled fields.

opw-4794903

closes odoo#211083

Signed-off-by: Outagant Mehdi (mou) <mou@odoo.com>

18.0-20250623

Toggle 18.0-20250623's commit message
[IMP] hw_drivers: allow saving db_name to conf

See odoo#214960 (master)

The PR mentioned above adds fixes to connect to a DB that is part of a
multi-DB instance. This includes saving a new configuration key,
`db_name`, to keep track of the current database name.

This commit backports just this functionality, making older versions
compatible with the new pairing token that includes to DB name. This
prevents a potential traceback if using this new token format.

task-4815521

closes odoo#215286

X-original-commit: a24aca2
Signed-off-by: Louis Travaux (lotr) <lotr@odoo.com>
Signed-off-by: Max Whale (mawh) <mawh@odoo.com>

17.0-20250623

Toggle 17.0-20250623's commit message
[FIX] l10n_jo_edi: Credit notes lines matching by discount

When generating a credit note for an invoice with multiple lines of the same product
(same product_id, name, and price_unit) but different discounts,
the system incorrectly matches both credit note lines to the same invoice line.
This commit solves this issue by adding line discount to
the criteria used to match credit notes lines with invoices lines.

task-4876849

closes odoo#214779

Signed-off-by: Maximilien La Barre (malb) <malb@odoo.com>

18.0-20250616

Toggle 18.0-20250616's commit message
[FIX] tools: facade, support isinstance of the wrapped class

Oversight of c6eb8bb

opw-4838986
点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载