Hi Stefan,
only a guess by having a quick look at the code you showed:
config->setShopId is not a good idea. It will not reload the config object
for current the process. So you will have a mix config objects and
configuration values from different shops.
I know that oxid console is using somethi
Hi there,
in OXID EE 5.3.x we were using a util class to activate modules based on
whitelist/blacklist for multiple subshops.
For OXID 6, that is not working 100% anymore, if a module defines its
own "controllers" in metadata.php, e.g.
https://github.com/OXIDprojects/oxid-module-internals
