Skip to content

Conversation

davidalger
Copy link
Member

Fixes bug where if you setup a store with a store code of 'default' and also have another store configured as the default store on the given website, the config values for the configured default store would be loaded when requesting the config for the store|default scope code. This results in the system displaying and using incorrect config values.

I've update the unit test to guarantee that this does not happen happen again within the affected method by mocking a default store, which if by the tested method will break the test. Also corrected the method so it correctly loads the correct config based on the passed in store code regardless of what that code may be.

…load associated config valueues when not configured as default store.
@vpelipenko vpelipenko added the PS label Jun 25, 2015
@paliarush
Copy link
Contributor

@davidalger Thank you for the provided fix, it looks good. We should be able to accept it if all tests pass on our CICD.

@magento-team magento-team merged commit 54ec80a into magento:develop Jul 17, 2015
@davidalger davidalger deleted the feature/fix-reading-store-config branch July 20, 2015 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants