For your SQL-Error during the image import, we had exactly the same point recently. The reason was that for a multistore the name of the store that is displayed in the backend differed from the constant in the table core_store for the store.
MAGMI did not find a storeid in getStoreIdsForStoreScope and therefore
was not executed and therefore vinserts[] was empty and that caused the SQL error.
@dweeves
Perhaps one could contemplate about reporting that getStoreIdsForStoreScope did not find a corresponding store to the user. Some users might find this info helpful.
reason is reindexing.
i would suggest you to check “on the fly reindexer” which will do main part of the job. (url_rewrite index & catalog_category_product index)
but not all of it.
you need to use also “Magmi magento reindexer” and check “catalog_product_price”
but alas, your setup on which i tested it cannot run php cli scripts , so magmi magento reindexer plugin cannot call magento indexer cli script :(
so you’ll have to run this last index (catalog_product_price) from magento backend.
The code to put in store column is the store view code , not the store code.
this is explained in latest wiki
however, you’re right, i could check for it & send an error or warning in case of an invalid store code detected.
Thank you for your quick response and help with multiple store import. To be honest, I have not already understood your point.
Within the function getStoreIdsForStoreScope I see the following code:
$cs=$this->tablename("core_store"); $sql="SELECT csmain.store_id from $cs as csmain WHERE csmain.code IN ($qcolstr)";
In Magento 1.5.1.0 the table core_store has the following attributes:
store_id code website_id group_id name sort_order is_active
What we have observed is, that when we used the content of the core_store.code in the column store in the csv-import file,
than the SQL-statement that was build in addImageToGallery in version 1.0.16 of the image processor was okay.
I’m really glad Magmi helped you finalizing your project.
Hope you’ll find some time to write about it on a blog explaing how magmi helped you and how it integrated in your workflow.
Magmi does not create “multilanguage” values but will create one value per store.
At the end,the result will be the same on frontend, but on the admin side, you won’t see “translated” value.
The explanation is simple:
With a single value in the column, there is no way to know which “translation” of other value it could be.
