|
to dweeves:
I’ve been looking what effect the multistore/websites have on the data too.
Here’s our setup:
store id 0: base (admin values)
store id 1: Website 1 - store 1 - view = Dutch
store id 2: Website 1 - store 1 - view = English
store id 3: Website 1 - store 2 - view = Dutch (Store 3 has different kinds of items)
store id 4: Website 2 - store 1 - view = Dutch (WEBSITE 2 has different pricing!)
SKU 00012 (entity_id 76938) is available in storeid 1,2 and 4
in catalog_product_website it has entries for website_id 1 (base) and 2 (b2b)
breakdown of the changes made in DB: (as far as I could find)
example value: NAME (catalog_product_entity_text - attribute id 57)
backend settings: scope=store_view
by default (in our setup) Magento sets an imported item at it’s base value (store id 0)
catalog_product_entity_text:
attribute_id 57
store_id 0
value: NAME
Depending on the product settings, item is now available in all views
if you change the title in the English store view (storeid 2) (untick use default value box for selected store view in backend, change name) , it adds a line in the catalog_product_entity_text DB:
catalog_product_entity_text:
attribute_id 57
store_id 2
value: NAME FOR ENGLISH VIEW
it only seems to add a line for the entry needed (so no extra line for the other views - just storeid 0 (=base) and storeid 2 (=english) - the others are taken from the baseview
When you edit the product in the backend to change the Name back so it uses the default value (in store view for storeid 2, tick Use Deafult Value ON again), then it removes the entry from the DB again
Example 2: price (scope=website)
we have 2 prices - 1 for website 1 (use base/admin values), 1 for website 2 (storeid 4)
in catalog_product_entity_decimal:
storeid = 0, value = PRICE A
storeid = 4, value = PRICE B
I couldn’t create an export for all values in 1 export file (maybe it’s me, maybe it’s magento settings..)
hope this helps
|