You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 6, 2022. It is now read-only.
If you make an entry into the Magento2 core_config_data table for a store ID which is not present in the Magento installation, Magento will throw an Error on each page in frontend and adminhtml and also for most of the bin/magento commands: The store that was requested wasn't found. Verify the store and try again.
Due to that not beeing really a bug in magento, because you should not provide any config data for stores which do not exist, it should may be implemented here to provide the security of page availability, even if wrong config data is provided in the config files.
This is not really a bug, but would be worth an enhancement i guess. So mageconfigsync wont break magento if you import wrong config data.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If you make an entry into the Magento2 core_config_data table for a store ID which is not present in the Magento installation, Magento will throw an Error on each page in frontend and adminhtml and also for most of the bin/magento commands:
The store that was requested wasn't found. Verify the store and try again.
Due to that not beeing really a bug in magento, because you should not provide any config data for stores which do not exist, it should may be implemented here to provide the security of page availability, even if wrong config data is provided in the config files.
This is not really a bug, but would be worth an enhancement i guess. So mageconfigsync wont break magento if you import wrong config data.
The text was updated successfully, but these errors were encountered: