Reproduction:
1. Install eCommerce, and complete a checkout using the Wire Transfer
payment, but don’t confirm the order at the website backend
2. Go to Orders > Unpaid Orders, the new created order should be there
3. Go to Reporting > Online Sales, select the "Unpaid Orders" filter
4. No pivot table shown for the unpaid orders
Reason: the pivot table is restricted for confirmed orders only (‘sale’
or ‘done’), the unpaid orders filter in Reporting has a different domain
from Orders
Fix: Remove the domain constraint for pivot table. Set the "Confirmed
Orders" filter to default
opw-2754932
closesodoo/odoo#86933
X-original-commit: 09b91b4bdf73004b70ff65f8f88ba034978af56b
Related: odoo/enterprise#25473
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
Step to reproduce:
- Search code of product in website_sale search bar
Current Bheaviour:
- No result
Behaviour after PR:
- Search also try to match , similar behaviour to V14 and before
opw-2737648
closesodoo/odoo#86921
X-original-commit: 395643d1377750577f3588506035623f9d0489c9
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
Since the commit [1], it's no longer possible to scroll the page while
dragging a snippet thanks to its thumbnail.
This is because for mass mailing the scroll element is not the same and
to check it we were looking for a class in the DOM. For that we did a
jQuery 'find' but without a 'length', the jQuery 'find' is always
truthy.
[1]: https://github.com/odoo/odoo/commit/29c6c80ac7009aa5068c763778342f7c6b115fad
task-2798872
closesodoo/odoo#87021
X-original-commit: d4b231222c5baf726332deddfe6d4c5e3e7865db
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Expected Behaviour
When adding a shipping cost in a SO, with the shipping method being
associated to a product, the price should be calculated according to
the price of the product in the order's pricelist if available
Observed Behaviour
When adding a shipping cost related to a product, with a fixed price,
the public price of the product is used instead of the price defined
in the SO pricelist
Reproducibility
1. Create a product "Test Shipping" with a public price of 10
2. Create a shipping method "Test Shipping" associated with the
"Test Shipping" product
3. Create a pricelist "Test Pricelist", where the product "Test
Product" has a cost of 15
4. Create a contact "Test Contact" associated with "Test Pricelist"
5. Create a So for the "Test Contact" with "Test Shipping" as shipping
method -> Shipping cost will be 10 instead of 15.
Fix Description
The issue here was that the price computed by the delivery carrier didn't
took into account the selected pricelist. We tried to then change it in
the delivery chooser wizard, but some issue with particular case (i.e.
when the shipping cost should be 0 if the SO total is bigger than X)
appeared, leading us to add the fix directly in the delivery_carrier
classe.
Related Issues/PR
- opw-2754482
closesodoo/odoo#87028
X-original-commit: bb778cd7be835706f54e9e0f342eecf3e5e4e904
Signed-off-by: Adrien Widart <awt@odoo.com>
Signed-off-by: Hendrickx Anthony (anhe) <anhe@odoo.com>
The selector `.fa.fa-trash.text-danger` is not enough precise,
it could select another element using the same classes,
as it's the case in #85682,
and at the binding the event `RevokeTrustedDeviceButton` `_onClick`
event on that other element.
I would have used a dedicated class directly on the element,
such as `o_auth_totp_remove_trusted_device`,
but since we are in stable and cannot rely on the template
being updated, there is no other choice than using what we
currently have without the update.
In addition, the `remove` method must be called on the model
`auth_totp.device`, as since the revision
https://github.com/odoo/odoo/commit/2dee29a7dc6db5cd1f9cc62989b905cff5466f3b#diff-6ea780b2956bc89552a57dd3e711fdd7191d1599c246cc9c887bcc38fa7eabacR11-R12
`auth_totp.device` has been added,
inheriting from `res.users.apikeys` but with a different `_name`
and they therefore do not share the same IDs.
Meaning you would end asking the deletion of the `res.users.apikeys`
record using the same ID than trusted device record.
closesodoo/odoo#87033
X-original-commit: 0aeb0030752e3634218ce7dd3d394447715d403b
Signed-off-by: Denis Ledoux (dle) <dle@odoo.com>
Steps :
Install Recruitment and Surveys.
Recruitment > Settings > Enable Send Interview Survey.
Recruitment > Any Position > Create an Application,
click on Send Interview and then on Send.
Duplicate it, click on Send Interview end then on Send.
Issue :
ValueError: Wrong value for survey.user_input.applicant_id.
Fix :
This is initially caused by the fact that the applicant's response
is also duplicated. As it shouldn't be, copy=False.
opw-2751975
closesodoo/odoo#87023
X-original-commit: bc9dc1d710cee2808e0823bb96064c0f87beee78
Signed-off-by: Kevin Baptiste <kba@odoo.com>
Avoid observing the last message view just for checking the state of self.
task-2800990
closesodoo/odoo#87003
Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
Before this commit:
When user shares the invitation link of the channel(groups restricted), guests
are allowed to access it.
After this commit:
Guests will not be allowed to access channels that are restricted to groups.
Task-2679184
closesodoo/odoo#87004
X-original-commit: ea3232c111546ec636f543db912bf0e2a7ed345b
Signed-off-by: Sébastien Theys (seb) <seb@odoo.com>
Current behavior:
When using a product kit that have a product kit in his BoM some move line where merging when they shouldn't.
Because of this the delivered count wasn't correctly updated in any sale order using this product
Steps to reproduce:
- Create product B to manufacture with a BoM (type Kit) using component A and component B
- Create product A to manufacture with a BoM (type Kit) using product B and component A
- Create a sale order with product A
- Confirm the sale order and validate the delivery
- The delivered count of product A on the sale order stays at 0
opw-2777810
closesodoo/odoo#87000
X-original-commit: 0e6480811e2144a1034f1347a816a0bd052c4516
Signed-off-by: Tiffany Chang <tic@odoo.com>
Signed-off-by: Engels Robin (roen) <roen@odoo.com>
To reproduce
============
- Using ldap server with Microsoft Active Directory
- Set up ldap authentication on Odoo
- Trying to log with a username/password from ldap on Odoo doesn't work
Purpose
=======
Because referral chasing is enabled by default, python-ldap ends up requesting
a completely different unrelated server.
Specification
=============
To solve the issue, a system parameter `disable_ldap_chase_ref` must be created
to have the possibility to disable referral chasing by setting its value to `True`.
opw-2724800
closesodoo/odoo#86993
X-original-commit: f40a98ee9b020782d0097372066c555909253768
Signed-off-by: Olivier Dony <odo@odoo.com>
Signed-off-by: abla001 <abla@odoo.com>
Alexandre Kühn