Closed Aquive closed 2 months ago
Is in this case the module already in config.php as enabled or isn't it in the config.php and enables setup:upgrade it on deploy?
Hey @peterjaap thanks for your fast reply. It is deployed after running/testing/commiting everything locally. So the module is present in config.php with a 1 (enabled) like below.
'Magento_Csp' => 1,
This is just an example. We experience sometimes a second deploy is needed. I am not sure if it is allways when enabling a module. It might be the case in other situations too. I will pay attention and check it from now on.
Hi @Aquive, No idea if you still have this issue, but I had similar issues (more specifically about missing classes). I fixed it by using rotating cache prefixes, as explained here. Hope this helps!
I didn't came accross it too often lately, but it is good to know there is a possible solution. I will test it out when I encounter it again.
Btw, any idea why this is not default? Does it come at a cost?
This issue has been automatically closed. Please, open a discussion for bug reports and feature requests.
Read more: [https://github.com/deployphp/deployer/discussions/3888]
This issue has been automatically closed. Please, open a discussion for bug reports and feature requests.
Read more: [https://github.com/deployphp/deployer/discussions/3888]
Very often we need to do a second deploy to make magento 2 working again after a first "succesfull" deploy. (The deploy is succesfull but Magento throws an erros, see below). I am not exactly sure when this problem occurs but I think it happens when enabling a previously disabled module.
This time it was this error. The CSP module was disabled, and with this deploy it was being enabled.
Deploy.php
Upvote & Fund