postcodeservice/postcode-magento2

[BUG] Onestepcheckout.com compatibility

Closed this issue · 7 comments

Paulsky commented

To Reproduce
Steps to reproduce the behavior:

  1. Enable Onestepcheckout
  2. Sort and enable postcode, tig_housenumber, tig_housenumber_additional and tig_street field

Expected result
Postcode field is rendered before tig_housenumber and tig_housenumber_additional

Actual result
Postccode field is sometimes rendered before tig_housenumber, sometimes completly elsewhere

Workaround
None, I'm wrting some JS for fixing this bug and other TIG bugs

  • Magento version: [Magento 2.4.5]
  • PHP version: [8.1]
tig-jeffreybranderhorst commented

Hi @Paulsky ,

We do support some one-step checkouts, which one-step checkout do you got? Do you use the https://www.onestepcheckout.com/ extension? Because that is one we do not support, unfortunately.

If you use another one-step checkout we would like to here which checkout and what version of this checkout.

Have a great day,
Jeffrey

Paulsky commented

Yes I'm using Onestepcheckout.com. We weren't aware you didn't support that extension. Do you have this mentioned somewhere? When did you drop the support on this? Because you had an extension postcode-magento2-checkout-support to support it.

  • 👍1
tig-jeffreybranderhorst commented

Hi @Paulsky ,

In the past, we did have an extension called postcode-magento2-checkout-support that was able to help with onestep checkouts. Since we refactored the complete code of the extension, this extension is no longer working and the support for onestepcheckout.com was dropped for now.

Have a great day,
Jeffrey

tig-jeffreybranderhorst commented

Hi @Paulsky ,

Just a small update, I have placed support for onestepcheckout.com on our long term backlog, because in the future we do want to be compatible with the checkout. I will link this GitHub issue to our backlog issue as an upvote on the feature.

If you have other onestepcheckouts available, like the amasty or mageplaza checkout, these checkouts should work with the postcode extension.

For future references or updates, you could ask about the status of POSTCODENL-446 this is our backlog issue internally.

Have a great day,
Jeffrey

erwinromkes commented

@tig-jeffreybranderhorst do you maybe made some progression on this issue?

tig-support commented

Hi @erwinromkes, I don’t have an update on this at the moment. It is on our long term backlog.

  • 👍1
schldwcht commented

Hi @Paulsky, @erwinromkes
I wanted to inform you that, after careful consideration, we have decided not to support the OSC of OneStepCheckout.com at this time. Although we may revisit this decision in the future, we have decided to close this issue for the time being.

Thank you for your understanding and please let us know if you have any questions or concerns. Have a great day!

Best regards,
Joost