…e, and make sure when fetching the values, they are fetched from the correct scope.
Changes:
most config settings where configurable on storeview scope but not on website scope, which is strange, these have been corrected
some config settings shouldn't be allowed to be configured on storeview scope (the ones that relate to caches) I think, but I might be wrong?
When getting the values of the configurations in the Config Model, previously it defaulted to the 'default' scope, even though you were able to configure some values on storeview scope
Purpose of this PR:
Having the ability to hide prices on certain websites only
Questions:
It would be nice to see some extra explanations of certain config values in the backoffice, like
Show Price Per UOM => what does UOM stand for?
DB Caching => what purpose does this has, what are the benefits or the downsides of enabling this?
DB Caching => mentions 'Ajax loading', even though the config setting that's called like that behind the scenes is called B2B Pricing Enabled, which is kind of confusing
…e, and make sure when fetching the values, they are fetched from the correct scope.
Changes:
Purpose of this PR:
Questions:
It would be nice to see some extra explanations of certain config values in the backoffice, like
Show Price Per UOM=> what does UOM stand for?DB Caching=> what purpose does this has, what are the benefits or the downsides of enabling this?DB Caching=> mentions 'Ajax loading', even though the config setting that's called like that behind the scenes is calledB2B Pricing Enabled, which is kind of confusing