Vat Validation URL for EU Vat numbers changed. (Vies Service)

[WIKAWebmaster]

An Vat Validation is not possible anymore because in the file:
https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Customer/Model/Vat.php

On line 47 the is the following code available
const VAT_VALIDATION_WSDL_URL = 'http://ec.europa.eu/taxation_customs/vies/services/checkVatService?wsdl';

This url is not working anymore and should be changed to the new one to get it working again:
[http://ec.europa.eu/taxation_customs/vies/checkVatService.wsdl]

New Code
' const VAT_VALIDATION_WSDL_URL = 'http://ec.europa.eu/taxation_customs/vies/checkVatService.wsdl';

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

[Screenshots, logs or description]

Actual result (*)

[Screenshots, logs or description]

[m2-assistant]

Hi @WIKAWebmaster. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@WIKAWebmaster do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @shikhamis11. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[shikhamis11]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @shikhamis11. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @shikhamis11, here is your Magento instance.
Admin access: https://i-27874-2-4-develop.instances.magento-community.engineering/admin_49d6
Login: facdbe41 Password: ef8c306dbeb5
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

✅ Confirmed by @shikhamis11
Thank you for verifying the issue. Based on the provided information internal tickets MC-33515 were created

Issue Available: @shikhamis11, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[m2-assistant]

Hi @shikhamis11. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[magento-engcom-team]

Hi @WIKAWebmaster. Thank you for your report.
The issue has been fixed in #27886 by @shikhamis11 in 2.4-develop branch
Related commit(s):

• faaec185511ccd0d8ca2797c5ea281894522df84
• 49dc77b9e76e3964ec10a4428bfe7ffd319f2e16

The fix will be available with the upcoming 2.4.0 release.

[grossmann]

@magento-engcom-team
Question: Is this going to be backported to Magento 2.3.x or do I have to upgrade to 2.4.0 when it is released? I could not find any documentation about how backports are handled in Magento 2.
Thanks for your reply.

[hostep]

@grossmann: the @magento-engcom-team user is just a bot, it never replies when you ask it something 🙂
If you need a fix, you'd best create a patch yourself and apply it to your shop somehow, that's usually the fastest approach.

@slavvka: can you answer the question above if this fix will be backported to 2.3.x? (maybe the bot can somehow automate its answers when a fix is being backported, that could be really helpful for informing the people interested)

[grossmann]

@hostep Thanks for the hint with the bot ;-).
Sure, I already fixed it on my local 2.3.4-p2 installation. But if I do an composer update in the future, say to 2.3.x then the fix gets lost as it is not back ported.
A release for 2.4.0 is not yet available.

[chernenm-zz]

Hello @hostep,

This issue has been backported into 2.3.x and will be released in 2.3.6.

Best regards,
Misha Chernenko.

[grossmann]

@chernenm Your link to the pull request gives a 404 error. Can you show me to the correct url?

[chernenm-zz]

Hello @grossmann,

I am sorry, it is not merged yet, it will be released in 2.3.6.

[slavvka]

The link above is from internal repos.

[hostep]

Thanks @chernenm!

Would Magento consider opening up a 2.3.6-preview branch for upcoming new versions to the community. Since that would make things a lot clearer and we can search that branch to see if things are being backported yes or no?
A couple of years ago, these preview branches were available, but for some reason they got removed?