2.4.7-p1: "Could not create an acl object" after disabling Magento_PaymentServices* modules about magento2 HOT 12 OPEN

This one is quite annoying

Adobe decided to pack magento with their own service which I cannot use anyway (not available in my country). And to add insult to injury I cannot remove it properly.

from magento2.

Hi @OvalMedia. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

from magento2.

Hi @engcom-Delta. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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.

from magento2.

Hi @OvalMedia ,

Verified the issue on 2.4-develop community as well as commerce edition and we are not able to reproduce this issue.

Steps to reproduce:-

1.Install magento
2.disable all paymentservices modules: bin/magento module:disable Magento_PaymentServicesBase
Magento_PaymentServicesDashboard Magento_PaymentServicesPaypal Magento_PaymentServicesSaaSExport
Magento_PaymentServicesPaypalGraphQl
3.bin/magento setup:di:compile
4.Login to admin panel

disable all payment services modules

Run bin/magento setup:di:compile

Login to admin panel

Please refer the attached screenshots and let us know if we missed anything.

from magento2.

Whatever you did, you did not disable the mentioned modules. As a matter of fact your own screenshot shows (highlight in red) that upon trying to disable them magento is trying to tell you these modules do not exist (for whatever reason). So you basically changed nothing and ran another compilation.

from magento2.

Hi @OvalMedia ,

Verified the issue on 2.4.7 and it is reproducible.

Hence, Confirming the issue.

Steps to reproduce:-

1.Install magento
2.Disable all payment services modules: bin/magento module:disable Magento_PaymentServicesBase Magento_PaymentServicesDashboard Magento_PaymentServicesPaypal Magento_PaymentServicesSaaSExport Magento_PaymentServicesPaypalGraphQl
3.bin/magento setup:di:compile
4.Login to admin panel

Disable all payment services modules

bin/magento setup:di:compile

Login to admin panel

from magento2.

✅ Jira issue https://jira.corp.adobe.com/browse/AC-12287 is successfully created for this GitHub issue.

from magento2.

✅ Confirmed by @engcom-Delta. Thank you for verifying the issue.
Issue Available: @engcom-Delta, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

from magento2.

❌ Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-12287

from magento2.

This one is quite annoying

from magento2.

@OvalMedia, there is a way to remove them with a composer trick:

1. Add this to your composer.json file:

    "replace": {
        "adobe-commerce/os-extensions-metapackage": "*"
     }

2. Run composer update adobe-commerce/* magento/*
3. Run bin/magento setup:upgrade

That should get rid of them. This is a pretty common practice done by Magento veterans, to remove unwanted modules this way, it was first described in this blog post as far as I remember.

from magento2.

I am familiar with that technique. I don't use adobe commerce. And I doubt this will make the exception go away as it is triggered in module-config. The way I interpret that exception a field that used to be optional ("title") is now required. But since the ACL files are all merged the title was eventually set by the adobe payment modules. That way it was not noticed the title attribute is missing in other modules.

from magento2.