View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004722 | OXID eShop (all versions) | 4.07. Source code, Test | public | 2012-11-21 12:40 | 2024-01-17 15:33 |
Reporter | arturas.sevcenko | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Product Version | 4.5.11 revision 46050 | ||||
Fixed in Version | 7.0.0 | ||||
Summary | 0004722: Shop config is not reloaded on shop id change | ||||
Description | oxConfig::setShopid() can cause problems, if used after oxConfig::init() call, because it only changes shop id without triggering object reload / reinit | ||||
Steps To Reproduce | Reproduced by ERP SOAP plugin oxGetConfigParametersPlugin. | ||||
Additional Information | Problem is more generic, and can show up anywhere in ERP system where subshop configuration is any different than of the mainshop. | ||||
Tags | ERP, Subshops, Varnish | ||||
Theme | All | ||||
Browser | All | ||||
PHP Version | Not defined | ||||
Database Version | Not defined | ||||
related to | 0004538 | resolved | arturas.sevcenko | OXID ERP Interface | In ERP calls getShopConfVar always select config params from Supershop but not from Subshop |
parent of | 0005939 | resolved | SvenBrunk | OXID eShop (all versions) | EE: AutoLoader does not work with ERP SOAP and Subshop Modules |
|
Changing current logic of this place can make more problems than fix them. The shop id is reset when user is logging in to subshops, when new subshops are created also in modules. So this should be taken into account when refactoring oxconfig. |
|
there is a pull request related to that issue: https://github.com/OXID-eSales/oxideshop_ce/pull/373 i know two workarounds 1. change the shopid within a new php process and set the shopid early e.g. by $_POST['shp'] so everything gets reloaded with the correct shopid 2. clear oxconfig from registry, call setConfig on once on every objecttype you use (also the indirectly used objecttypes) clear all objects that may hold the config object or derivated data) |
|
this issues effects ERP Module, it does not have the correct subshop configuration when importing things into subshop, so e.g. it would sends the wrong hostname in invalidation request to varnish server. There is module available, that fixed that for at least that use case. -- EDIT -- there is a related ticket to that ERP module, so maybe ERP related issues can be worked around by using sub shop specific login. ---------- |
|
ERP interface now has 1 Controller per subshop |