View Issue Details

IDProjectCategoryView StatusLast Update
0006483OXID eShop (all versions)4.12. Subshop handlingpublic2017-08-01 09:43
Reportermichael_keiluweit 
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version4.10.1 / 5.3.1 
Target VersionFixed in Version4.10.5 / 5.3.5 
Summary0006483: oxConfig.aServersData is for shop id !1 sometimes empty, somestimes filled
DescriptionIt depends if the to creating subshop has a parent shop or not.
If no parent shop is setted, the array entry will be empty:

a:0:{}

Has the new shop a parent shop the array is filled:

a:1:{s:32:"770d9ca56c7f12cf4f44ec9d9e93260f";a:6:{s:2:"id";s:32:"770d9ca56c7f12cf4f44ec9d9e93260f";s:9:"timestamp";i:1471522486;s:2:"ip";s:9:"127.0.0.1";s:17:"lastFrontendUsage";i:1471522486;s:14:"lastAdminUsage";N;s:7:"isValid";b:1;}}


Furthermore there's no need to create oxConfig.aServersData for each subshop as it is an array which holds for each server an own entry. So this config name can be added to the $aOnlyMainShopVars array:

$aOnlyMainShopVars = array('blMallUsers', 'aSerials', 'IMD', 'IMA', 'IMS');

And it is currently bugged. See the linked entry.
Steps To Reproduce1. install an EE (I tested with 5.3.1)
2. create a subshop with the parent shop id 1.
3. create a subshop, do not choose a parent shop nor set any checkbox.
4. goto the mysql and execute the command:

select oxshopid, oxvarname, oxvartype, DECODE( oxvarvalue, 'fq45QS09_fqyx09239QQ') as oxvarvalue from oxconfig where oxvarname = "aServersData";

You will that the entry for shop id 2 is exactly the same as for shop id 1. The entry for shop id 3 has an empty array as value.
TagsSolution Provided
ThemeNot defined
BrowserNot defined
PHP VersionNot defined
MySQL VersionNot defined

Relationships

related to 0006484 resolvedvilma_liorensaityte oxConfig entry aServersDatais is always deleted and selected by shop id 1, but written by the actual active shop id 

Activities

michael_keiluweit

2016-08-19 09:26

developer   ~0011746

Please note: if 0006484 is fixed as suggested, then this bug entry can be automatically closed, too.