Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running app:config:import after setup:db-data:upgrade doesn't create new websites/stores #67

Open
rikwillems opened this issue Sep 21, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@rikwillems
Copy link
Contributor

I found that the current order of commands during a deploy doesn't (fully) import the configuration properly.

The setup:db-data:upgrade command sets the config_hash in the flag table. This in turns makes the app:config:import think it doesn't need importing. In my case it turns out new website and stores are not created.

Reversing the order of commands helps out but I'm not sure if that has any side effects.

@rikwillems
Copy link
Contributor Author

Although the documentation isn't very specific about it, it appears you need to run config import before the setup upgrade steps: https://devdocs.magento.com/guides/v2.4/config-guide/deployment/pipeline/technical-details.html

@osrecio
Copy link
Collaborator

osrecio commented Oct 24, 2020

I will check.

@osrecio osrecio added the enhancement New feature or request label Oct 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants