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
The config fixture step provides the ability to specify a config scope (that is "default", "website" or "store"). For example:
When I set config value for "some/config/path" to "1" in "store" scope
The problem is, to be usable with anything but "default", a scope identifier needs to be specified, for example as follows:
When I set config value for "some/config/path" to "1" in "store""usa" scope
In the table core_config_data the scope ID is stored as an integer ID, using 0 for the "default" scope.
To make this more reusable the scope ID should be specifiable as a website or store view code.
The config fixture step provides the ability to specify a config scope (that is "default", "website" or "store"). For example:
The problem is, to be usable with anything but "default", a scope identifier needs to be specified, for example as follows:
In the table
core_config_data
the scope ID is stored as an integer ID, using0
for the "default" scope.To make this more reusable the scope ID should be specifiable as a website or store view code.
References:
The text was updated successfully, but these errors were encountered: