10.0 #10
Open
10.0 #10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…te error closes #32607 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
Backport of 9a48f67 to 10.0 Needed for odoo/enterprise#5422 Closes #36609 closes #36614 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
Add nakometal closes #36546 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
Before this commit, search view was barely usable with Japanese IME. For instance, when pressing ENTER while in composition mode and IME prompts some suggestions, it made a search with the updated input content. The expected behaviour should have been to update the input content, without making the search yet. This commit fixes the issue by turning off some actions of the search view when typing during composition mode. opw-2061590 Closes #35789 closes #36284 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
closes #36616 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
When .with_context() is called with a dictionary as 1st positional argument, it will replace context (and not modify the referenced keys) It may create bugs when losing the content of the context (e.g. remove partner's language) This is a partial backport of #36164 with the website part as discussed. closes #36692 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
Suppose that a Task is added on a task via a studio customisation. Then the _get_message_needaction method gets called on the onchange of the toplevel task, which triggers another call to _get_message_needaction. During that update, we get a self with a model.newID; its ids field is empty, so the list of tasks res itself is empty. As a result the method crashes on a malformed query. This can in turn prevent the completion of some higher-level operation, e.g. a state change on the task. opw 1909043 closes #29084 closes #36813 Signed-off-by: Nans Lefebvre (len) <len@odoo.com>
before this commit: it gives error when we redirect to payumoney site after this commit: payment testing in payumoney is working as expected closes #36764 Signed-off-by: Nicolas Martinelli (nim) <nim@odoo.com>
closes #37063 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
Missing log for analyzing cron issues.
KWD has 3 digits. opw-2071909 closes #37229 Signed-off-by: Nicolas Martinelli (nim) <nim@odoo.com>
closes #37453 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
closes #37445 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
Avoid comparing bool and datetime Fixes #36435 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
This makes you actually able to install the module with demo data and unplugged from network. Otherwise, it's impossible. closes #28098 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
This commit prepares the eCommerce module for the changes introduced in the new Stripe SCA module. It does exactly 2 things: - disable using token saved on Stripe for the eCommerce (slight feature loss, but non-blocking since eCommerce customers can still use the normal checkout flow) - widgetize some eCommerce JS code so that the new module can plug itself 'cleanly' into the payment flow (note the quotes) Co-authored-by: Nikunj Ladava <nla@odoo.com>
This commit prepares the website payment module for the changes introduced in the new Stripe SCA module. Co-authored-by: Nikunj Ladava <nla@odoo.com>
This commit prepares the eCommerce module for the changes introduced in the new Stripe SCA module. It does exactly 1 thing: - widgetize some website_quote JS code so that the new module can plug itself 'cleanly' into the payment flow (note the quotes) Co-authored-by: Nikunj Ladava <nla@odoo.com>
This commit prepares the payment base module for the changes introduced in the new Stripe SCA module. It does exactly 2 things: - allow to specify 'black-listed' providers for s2s request in some flows (needed because using Stripe tokens in the eCommerce will no longer be supported and this blacklisting must be done at the model level) - allow to read some data on transactions from the frontend without leaking too much info (by whitelisting the fields that will be included in the response) Co-authored-by: Nikunj Ladava <nla@odoo.com>
With the PSD2 directive coming into effect on September 14th, was had no choice but to switch our Stripe integration to use newer APIs that support Strong Customer Authentication (SCA for short). This meant switching from the old stripe.js implementation for 'redirection' flow to the Stripe Checkout API and from the Charge API to the newer SetupIntent API for s2s flows. This new modules introduce these changes in a non-intrusive way, this means that installing this module is *not* required for all customers (e.g. instances only accepting payment to and from countries that are not part of the EU), that installing it will support SCA flows and that uninstallation leaves you with a working instance as well. Essentially a backport of 9f5f2fc in a seperate module. Task 2039100 Co-authored-by: Nikunj Ladava <nla@odoo.com>
Revision c621da5 factorized some JS code from the ecommerce so that it may be cleanly overriden in a 'fix' module required for a Stripe update. Unfortunately, it broke the confirmation mechanism when paying with a pre-recorded token in the eCommerce flow. This commit reintroduces the required event handler so that token payment confirmation works again. opw-2283661
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
14 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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