Closed Paulsky closed 1 year ago
Hi @Paulsky ,
I tried reproducing this on a clean Magento with version 2.4.5, the moment I switch to Germany we are getting the street fields of Magento. Is this happening with your OSC enabled or on the default Magento checkout?
What other bugs are you referring to, the issue with the OSC you also submitted, or are there other issues?
Have a great day, Jeffrey
@tig-jeffreybranderhorst,
Thank you for your reply. Yes, this is happening with OSC enabled. I'm referring to the other bugs (https://github.com/tig-nl/postcode-magento2/issues/52, https://github.com/tig-nl/postcode-magento2/issues/53, https://github.com/tig-nl/postcode-magento2/issues/46)
Hi @Paulsky ,
Which OSC is this? And which version of the extension? I have also replied on your other github issues. I see #46 should be fixed in the newest version of the extension.
Have a great day, Jeffrey
@tig-jeffreybranderhorst this is https://knowledgebase.onestepcheckout.com/magento-2/getting-started-with-m2/changelogs/ ver_1.2.059
Hi @Paulsky ,
Thank you for the update, we do not have support on the OSC of onestepcheckout.com at this moment. In the future it is possible we are compatible with the OSC from onestepcheckout.com, but at this moment the extension is not yet compatible. Because I was not able to reproduce the issue on default checkout, I suspect the issue is caused by a conflict between the OSC and the postcode checker.
Have a great day, Jeffrey
Hi @Paulsky, 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. Best regards, Joost
To Reproduce Steps to reproduce the behavior:
Expected result TIG Street is hidden and not required
Actual result TIG Street is shown and required. Now there are two street fields
Workaround None, I'm wrting some JS for fixing this bug and other TIG bugs