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
Hi robert,
I think the module prefix in the oxconfig table is fine, also using it with
getShopConfVar does not sound new for me. But I remember I fixed a module
about a year ago by adding that prefix so I agree that it probably was
added some time ago.
You should give the method getConfigParam a
Hi Robert,
your link from the docu is right, and maybe support was removed, sorry for
not beeing on the current status about that.
I remeber support for savepoints where integrated into dbal some time ago
so know I am also abit confused.
It seams that api from dbal was changed also without an
