So what am I supposed to do with this? Only solution offered so far by magento is remove module … is that where we leave this ? When I do remove stripe the Magento cloud deploy Process does in fact work as they say …
It’s not hard to understand, its just not a real answer. Magento says this:
Vidal Yesterday at 00:34
Hello Sam,
Unfortunately, the creator of the extension must determine the cause of the issue between Magento and the extension. The integration of any 3rd party application is the responsibility of the SI and/or the creator of the extension.
Best,
Vidal
Meanwhile we can’t even deploy Magento to the Cloud without removing Stripe our pay processor. And neither you or Magento seem to care.
All my extensions are 100% Open Source and published on GitHub: https://github.com/mage2pro
So they can be easily explored and debugged by other developers and customers.
Magento Enterprise Cloud is a closed source and undocumented (!) service with (as you said) 2 weeks delay in customer support.
I do not know what is the cause of your issue, and I do not have any ability to debug it because of lack of the Cloud’s source code and specification.
I recommend you just leave Magento Cloud and use your own server, which you can control and debug.
Hey!
Look at the error I was just able to reproduce in a docker container. It happened when I disabled all modules from command line and then re-able them. Magento-Cloud does exactly this when it deploys. Does this help figure out why that error shows up? It does not look specific to Magento-cloud anymore…
Yes and I upgraded which still did not work and you had said to wait for a solution forever because this was undocumented and closed source. But I am not even using Magento Cloud now and get the same error so is it still some black box code ??
I think, you have upgraded your system in some low-quality way, because the module:enable Magento 2 core bug was fixed by me 9 days ago.
If you state that you have upgraded correctly, then give me acccess to your upgraded installation where the module:enable command fails, and I will point you to your mistake exactly.
As a guess from your words, look at your action «I disabled all modules from command line».
Congratulations, you have disabled my patch too!
So, if your run module:enable after this action, the Magento 2 core bug will reproduce again (nobody patches it, you have disabled the patch by your own arms).
It is just one of my guesses from your exact words. Actually, there are plenty wrong ways to implement my 4 step upgrading instruction.
I was just trying to do what the Cloud deploy scripts do … that is probably the reason then why it still fails. Cloud build function disables all modules, and then re-enables them again.