Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility with Custom Checkout #153

Open
bbrassem opened this issue May 9, 2022 · 1 comment
Open

Compatibility with Custom Checkout #153

bbrassem opened this issue May 9, 2022 · 1 comment
Assignees
Labels
compatibility Compatibility issues

Comments

@bbrassem
Copy link

bbrassem commented May 9, 2022

What problem does this feature solve?

Customer uses a custom checkout together with the MyParcel module, and describes the following issue:

"The problem is that the widget in .myparcel-delivery-options-wrapper is not always displayed and I cannot find out why. This is what I do:

  • I updated myparcelnl.php, to include header scripts also on third party checkout page
  • whenever shipping methods are reloaded, I do trigger:
    prestashop.emit("updatedDeliveryForm", {dataForm:$('#js-delivery').serializeArray(),deliveryOption:$('#js-delivery').find('[name^="delivery_option"]:checked').closest('.delivery-option-row')});

After the customer address is filled in AND I make a full-page reload, then all works well. But before full page reload, the widget won’t show, so I guess I’m missing some resource maybe?"
__

This was discussed internally with one of our developers, and I was told this is a compatibility issue / feature request.

What should the solution look like?

A custom checkout that works in combination with the MyParcel module and does not need an additional refresh to load the widget (as described in the Problem section).

Relevant log output

No response

Additional context

No response

@bbrassem bbrassem added the feature New feature or request label May 9, 2022
@AaronTajriba
Copy link

Hi, is there any update on this one?

@EdieLemoine EdieLemoine added compatibility Compatibility issues and removed feature New feature or request labels Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compatibility Compatibility issues
Development

No branches or pull requests

3 participants