dweeves/magmi-git

Magmi GitHub

magmi-git's Issues

Error in file 001_skufinder.php (around line number 62)

There is an error in file 001_skufinder.php (around line number 62) :

//now find sku
$sql="SELECT sku FROM ".$this->tablename("catalog_product_entity")." as cpe JOIN catalog_product_entity_".$attinfo["backend_type"]. "ON value=? AND attribute_id=?";

Should be :

//now find sku
$sql="SELECT sku FROM ".$this->tablename("catalog_product_entity")." as cpe JOIN
catalog_product_entity_".$attinfo["backend_type"]. " ON catalog_product_entity_".$attinfo["backend_type"].".entity_id = cpe.entity_id
WHERE value=? AND attribute_id=?";

There has to be a space before "ON" + the sql produced false errors in my case

Custom Options mass import: SQLSTATE[23000]: Integrity constraint violation:

I just ran the Custom Options plugin through DataPump api.
About 30,000 inserts. I chose to go with Custom Options because this shop will not include inventory control.
My syntax was mostly made of drop downs.
Size:drop_down:0:0
l did not receive any errors from the shell output when running the script.
On a second look, I realized I shouldn't have used 0:0 on all of them. I manually attempted to edit the order of the custom attributes and I receive a foreign key constraint error.

SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (mydatabase.catalog_product_option_title, CONSTRAINT FK_CAT_PRD_OPT_TTL_OPT_ID_CAT_PRD_OPT_OPT_ID FOREIGN KEY (option_id) REFERENCES catalog_product_option (option_id) ON DELET)

I'm not sure if this is relative to Magmi or Custom Options plugin or Magento itself, but I figured I would put a post up here just in case.

Thanks.

Magento 1.9.0.1
PHP 5.3.28
Apache/2.2.26 (Unix) mod_ssl/2.2.26 OpenSSL/0.9.8i mod_bwlimited/1.4
WebServer to PHP Interface cgi-fcgi
MySQL 5.1.73
Linux Centos (not sure which version anymore)

Problem with tree separator escaping in categoryimport.php

I may be wrong but I think there is an error in categoryimport plugin in case of category names matching tree separator (which is "/" in my case)

Line 424 is using the original categories string ($item['categories']) but I think it should use $icats (categories string after processing escaped tree separators)

So line:

        $catlist=explode(";;",$item["categories"]);

should be:

        $catlist=explode(";;",$icats);

I don't know if this is the proper way for suggesting code changes. Sorry if I'm wrong

Does Magmi create weird urls?

Hello,
I use Magmi mostly to update existing products.
I have enabled:

• On the fly indexer v0.1.5.
• On the fly category creator/importer v0.2.3
• some other plug-ins also

If I search product by sku in front end and then go to the product page via opening
search result popup. My product page then has URL as follows:
mywebsite.com/root-catalog/default-category/t-shirt.html?___SID=U

Shouldn't it be something like:
mywebsite.com/t-shirt.html?___SID=U

Can someone explain this kind of URLs?
.../root-catalog/default-category/...
Has Magmi created them?

At least they didn't exist before Magmi was taken into use. Is this avoided by different settings somewhere?

Best Regards

Duplicate Manufacturer Values (drop down attribute)

Seems lately Magmi (v0.7.18) creates a duplicate entry in eav_attribute_option_value when the manufacturer name already exists. (manufacturer is drop down attribute)

csv file only has 2 columns (sku, manufacturer) - manufacturer is manufacturer name (ie Apple) - tried manufacturer_value but no update occurred... if 'Apple' is already in eav_attribute_option_value, it creates an additional entry with same value and a new option_id (store_id is zero in both instances) .. Magmi Optimizer v1.0.5 is the only plugin selected when importing.

Seems like it's not checking the option value before inserting a new record ???

Thanks!!

multi sotre import

Hello.

I have two store one "admin" and "Kr"
Id like to read different language for name and descriptions.
this is what i set for csv that store column "admin" and "kr"

store,websites,attribute_set,type,category_ids,sku,name
admin,base,toy,simple,4,b1234,happy bear
kr,base,toy,simple,4,b1234,곰돌이

I have searched.. couldn't find yet.
Can you give me some idea please?

Thank you.
Kelly

importing into different stores

I have products that need to be imported into different stores

sku, name, store1, store2, subcat
111, item1, coke, pepsi, subcategory

i wrote out some logic that works for the value replacer plugin:
[{item.store1}]/{item.subcat};;[{item.store2}]/{item.subcat}

the problem is, what if i have some items that only have a value under store1 and are blank for store2 or the opposite?

I get an error when importing that says Cannot find site root with names : ,

Is there a way to work around this?

Spaces or dashes in sku in bundle_skus field

While testing I found the following possible issue.

I was unable to get the bundle_skus field to upload when the sku's had spaces or dashes in them. (Why our products have spaces in them in the first place is unknown.)

Error from profile run:
1 SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (magento.catalog_product_bundle_selection, CONSTRAINT FK_CAT_PRD_BNDL_SELECTION_OPT_ID_CAT_PRD_BNDL_OPT_OPT_ID FOREIGN KEY (option_id) REFERENCES catalog_product_bundle_option (optio) - 2 SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (magento.catalog_product_bundle_selection, CONSTRAINTFK_CAT_PRD_BNDL_SELECTION_OPT_ID_CAT_PRD_BNDL_OPT_OPT_IDFOREIGN KEY (option_id) REFERENCEScatalog_product_bundle_option(optio) - ERROR ON RECORD #1

bundle_sku input:
SIZE:"13441^65 - VENTURE";SIZE:"13441^67 - BURNER";SIZE:"13441^69 – CHARGER";SIZE:"13441^71 – MAGNUM";SIZE2:"10522^MINI";

categoryimport.php Undefined offset, Warning: array_merge() and Undefined index

We've just updated to Magmi 1.7.19a (and we tried also in the latest 7.20_git). As soon as we run the importer we get the following errors:

PHP Notice: Undefined offset: 0 in /var/www/vhosts/magento.local/httpdocs/magmi/plugins/extra/itemprocessors/categories/categoryimport.php on line 64

PHP Notice: Undefined offset: 1 in /var/www/vhosts/magento.local/httpdocs/magmi/plugins/extra/itemprocessors/categories/categoryimport.php on line 326

PHP Warning: array_merge(): Argument #2 is not an array in /var/www/vhosts/magento.local/httpdocs/magmi/plugins/extra/itemprocessors/categories/categoryimport.php on line 326

PHP Notice: Undefined offset: 0 in /var/www/vhosts/magento.local/httpdocs/magmi/plugins/extra/itemprocessors/categories/categoryimport.php on line 369

PHP Notice: Undefined index: in /var/www/vhosts/magento.local/httpdocs/magmi/plugins/extra/itemprocessors/categories/categoryimport.php on line 369

We're on Magento 1.9.0.1
We've got the importer to import last category of each branch, however much of the products belong to one and one only category

Error after full site backup

I had to do a full site backup on my Magento site the other day. Before the backup we had no issues with Magmi, after the backup we can log in, but there are errors on the screen and if we click on the "Save Profile" button are directed back to the login page. See image for errors on screen

thank you!

Translate categories names for store views

Can you please add options for translate of categories for each store view.
Or I have not found this option?

Viewing details on errors collapses while import runs

While import is running, if I click "show details" for the errors box, it expands & collapses real fast so I can't read the errors.

Import categories and products from csv file under existing categories in magento webshop with magmi

In my Magento shop i have some categories like "Baby", "Persoonlijke verzorging", "Wonen" with sub categories like "Slaapkamer", "Woonkamer" etc.

From my manufacturer i have a large csv file with lots of categories and products. The categories names in the csv file of my manufacturer are ok, but i want them to be importerd under the already existing categories in my shop.

The csv file of my manufacturer looks like this: articleNumber title brand description ean weight stock price recommendedPrice taxPercentage categoryId1 categoryId2 categoryId3 categoryId4 categoryName1 categoryName2 categoryName3 categoryName4 image1 image2 image3 image4 image5 image6 image7 image8 image9 image10 delivery warranty 1030 "Hama 1030 Hamafix Diaramen 5x5 cm 100 Stuks" Hama "Materiaal: Kunstof Inhoud: 100 Diaformaat: 5 x 5 cm Filmformaat: KB 24 x 36 mm Uitvoering: Lijst Diadikte: 2,3 mm Systeem: Hamafix " 4007249010308 1 true 1 5 21 2593 3392 "Foto / Video" "Diaprojektoren / Accessoires" http://url.nl "Direct leverbaar"

What i want to do is import all the products with magmi and with use of the magmi "On the fly category creator/importer". But if the categoryname1 from the csv file of my manufacturer equals "Foto / Video" it must be imported under an already existing category of my shop, lets say "Wonen".

The Magmi column "Categories" should than be like "Wonen/Foto / Video"

Is this possible with Magmi? or do i have to write a php script for this? I also want to exclude some products and categories from the manufacturer csv file. Lets say, if there is a column in the csv file like "Bricks". This column and all the products assigned to this column in the csv file, should not be imported.

Hope you can help me out with this one.

Thanks!

share improve this question

magmi product import into multiple categories

I have a site with different sores. In a csv file there are products that need to live in multiple categories. Each product appears multiple times in the csv file but on each line the only change is the store name and the category.

Here is what I have:

Cat,name,sku,SubCat
STORE1,test,123,category1
STORE2,test,123,category1

When i try to upload a product, it overwrites instead of updating, meaning that first magmi puts it into [STORE1]/category1 then erases that and puts it into [STORE2]/category1. How do I get it to append rather than overwrite? I want it to be in both.

Looks in wrong spot for import folder

Import location defaults to var/import, and below that it says "No csv files found in /media/Data/mag_17/var/import"

FYI I'm running magento out of /home/josh/www/vehiclefits/magento and magmi is a subfolder inside of that. There is no mag_17 in any path anywhere on my system, confirmed this with recursive globbing on the command line.

options_panel.php contains error on line 43

{{substr("{item.sku}",0,4}}

should be :

{{substr("{item.sku}",0,4)}}

There is a ")" missing

Error right after clean install

Hi,

Just a quick error in the following file :
/home/vivreperfumes/www/magmi/plugins/extra/itemprocessors/categories/categoryimport.php on line 88

You forgot a ')' at the end.

Bye!

Bundled Products

I know this has been mentioned in a few other places, but I figured I open an 'official' feature request for it.

I see a funding page here: http://funding.openinitiative.com/funding/1877/#feature_1878 which I randomly came across via Google Search, but I don't see it mentioned anywhere else.

I'm willing to contribute to to this, if some other are also willing.

Thanks

Remove store view from SKU

Hi,

we're getting nuts on this problem.

We have a multi-store setup with two websites and some store views (one website with four and one with two store views).

• Website 1 (Website)
  -- Store 1 (Store)
  --- ws1_german (Store View)
  --- ws1_english (Store View)
  --- ws1_german_b2b (Store View)
  --- ws1_english_b2b (Store View)
• Website 2 (Website)
  -- Store 2 (Store)
  --- ws2_german (Store View)
  --- ws2_english (Store View)

When we import products with magmi, we can set the store views, e.g.

"store","sku","price"
"ws1_german,ws2_german","12345","9.99"

We tried to remove the second store view from sku 12345, but nothing worked.

Is there an easy way to handle this? Like with the "product relater" plugin?
There you can delete related products with a minus (-) as a prefix. So what
we want is something like this:

"store","sku","price"
"ws1_german,-ws2_german","12345","9.99"

to remove the store view ws2_german. But that doesn't work, because -ws2_german
is recognized as the whole store view name and so "-ws2_german" is not found.
Of course! ;-)

Thanks a lot for your patience :-)

Regards,

Josch

Timezones of updated_at and created_at fields are not forced to UTC

This is as much a question as a possible bug/behavior issue.

When a product is updated, it looks the updated_at field is set to the current time using the timezone of my server. If I am correct, Magento stores all times in the database as UTC irrespective of the timezone of the server? (also noting that all Magento SOAP responses provide time in UTC too).

So if the timezone of my PHP is different, this seems to be storing the date/time at an invalid timezone in the database which puts the product being updated out of sync.

Is this intentional? Or is there a configuration fix to this?

Shouldn't all timezones be forced to UTC?

Shouldn't the conditional if be removed at

magmi-git/magmi/inc/magmi_defs.php

Line 10 in 8815a4c

if ($dtz == "")

?

Testing Magento 1.8 results

Hi Sebastien,

I'm testing Magmi (latest GIT files) for a few days now. It seems that there are two things going wrong while importing (configurable) products. It didn't make a url key and even after reindexing, the products didn't appear on the category page. Also tested it with using the On the fly indexer extension.

Are you familiar with this problem? Is there a solution? Or can I help with trying out different settings? Let me know.

Best regards,

Magmi Base Image Getting Excluded

We are using Magmi to import 500 products to our Magento 1.9 store.

Right now, everything works, except one single thing.

The base image is not getting included in the media gallery. We need this to show in media gallery too.

Everytime we import it, its excluded in the backend. And doesnt get listed on the media gallery too.

How do we fix this ? Is there a one line SQL code to run on the phpmyadmin, so all the EXCLUDE selection is removed from all the products in the store ?

Or any Magmi fix for this ?

As per Magmi documentation, we need to put + in front, but that doesnt work with remote images. It shows warning.

Problems when using spaces in columnlist

I experienced some problems when using spaces in columnlist :

columnname1, columnname2, ... : not OK
columnname1,columnname2,.. : OK

I took me a lot of time to figure this out.
This can be solved easily by changing the code like in file 000_columnmapper (line 73) :

foreach($mapped as $mname)
{
$item[$mname]=$item[$oname];
}

in :

foreach($mapped as $mname)
{
$mname = trim($mname);
$item[$mname]=$item[$oname];
}

Probably this should be done in all code parts where columnlist strings are "exploded"

.core_store' doesn't exist -

Hello Dweeves.

I installed a v0.7.19_git and test it then got a message ".core_store' doesn't exist -"

I checked my db and I found that all db table had "rfu_" .

so
".core_store" should be "rfu_core_store". I think....

Please help me how can I change it. :(

Thank you in advance for any help you can provide.

Kelly

SKU Finder not holding value

In SKU Finder v0.0.1, when enabled and configure is clicked, values input in the "sku find attribute code" field reset to blank after the profile is saved.

Importer appending data instead of updating

I'm having an issue with Magmi where the data being uploaded in the CSV seems to be appended rather than updated.

For example, lets say I have a color column. In the column I import red|green. The colors are uploaded successfully. Then at a later date I decide to change the colors and now change them to blue|yellow and it uploads successfully.

The issue I end up having, is after I upload the second CSV, in Magento the selected colors are red, green, blue and yellow.

Why is this? If I change the colors in the CSV, I except the colors to be change in Magento, not added to the current selection.

This issue appears to be a problem with all fields I've tested. For example, if I first set a product to store1 then later change it to store2, in Magento it now shows store1 and store2 for the product rather than just store2.

I'm using Magento 1.8.1 with Magmi v0.7.18 and set Magmi import to create new items & update existing ones when updating/importing products.

Could someone please tell me what the issue might be?

getting the following sql error when running product import

1 SQLSTATE[HY093]: Invalid parameter number: no parameters were bound - SELECT cce.entity_type_id,cce.attribute_set_id,cce.level+1 as level,COALESCE(MAX(eac.position),0)+1 as position
FROM catalog_category_entity as cce
LEFT JOIN catalog_category_entity as eac ON eac.parent_id=cce.entity_id
WHERE cce.entity_id=?
GROUP BY eac.parent_id
2 SQLSTATE[HY093]: Invalid parameter number: no parameters were bound - ERROR ON RECORD #1

on the fly indexer with no suffix

When I want to use the on-the-fly indexer without any suffix, it defaults to .html. This happens in the form, as well as in the code. Because of this, it's not possible to use the indexer with URL's without a suffix.

The fix is easily done, by changing the occurrences of

$this->getParam("OTFI:urlending",".html")

to:

$this->getParam("OTFI:urlending","") 

Magmi documentation missing

Hi all,
I was looking for documentation about Magmi and it's plugins. It was on Sourceforge, but I cannot find it anywhere.
It's just me or documentation is really missing?
Thanks.

Unable to Import Dropdown Attribute

Hi,

I'm using uDropship Marketplace Extension from Unirgy. It created an attribute called "udropship_vendor" whose properties are http://gyazo.com/830306d45fed760d56a5f2157881f123 . Now, when I import values for this attribute using Magento Default Import, it works fine. However, when I perform the same using Magmi, it creates new values instead of selecting the existing ones. Sample CSV for reference : http://gyazo.com/e74557836234e41a73f0c2eb52ead890

Kindly suggest.

store values for select attribute options not created

There is a bug in \Magmi_ProductImportEngine::getOptionIds.
When the "translation" syntax is used, the default (admin store) value and the store specific value are splitted with preg_match("|^(.*)::\[(.*)\]$|", $val, $matches).
But the store specific value (added to the $svalues array) is never used.

I guess the problem is that in line 652 of commit b7d739d
(

magmi-git/magmi/engines/magmi_productimportengine.php

Line 652 in b7d739d

$new = array_merge(array_diff($avalues, $exvals));

)
only the admin values are added to the array $new.

This line 652 looks very strange, as there is only one array as parameter for array_merge. I think the $svalues should be checked against existing values for that store, and then added to $new (this was probably meant to be the second parameter of the array_merge call).

Would be great if this issue could be fixed soon... ;-)

Integrate Magmi improvements made by understandingE.com...

Hi, was interested to know if there are any plans - by either party - to merge these changes into main github repo?

For those that haven't heard of understandingE they have taken Magmi and made a number of significant improvements, such as:

• Installer improvements.
• UI improvements
• Password protection by default

A video detailing the changes made can be seen here:
http://understandinge.com/tutorial/imp-0004/

The code itself can be downloaded from:
http://understandinge.com/getmagmi

Add documentation for bundle import

We need to add documentation for the bundled product import plugin introduced with #31. I thought of this:

== What it does ==

This plugin is able to associate simple products with options on bundle products.

== Usage ==

This plugin uses 2 extra columns:

* '''bundle_skus''' associate skus with options.
* '''bundle_options''' specify settings for options (optional).

Non-existing options found in '''bundle_skus''' or '''bundle_options''' will be created. Existing options will be updated or left alone. You can explicitly delete options by prepending them with a minus in '''bundle_options'''.

These Magento-columns might also be of interest:

* '''type''': The product type must of course be set to bundle.
* '''sku_type''': Whether the sku will be displayed dynamically (0) or fixed (1).
* '''weight_type''': Whether the weight will be calculated dynamically (0) or fixed (1).
* '''price_type''': Whether the price will be calculated dynamically (0) or fixed (1).
* '''price_view''': How to display the price: "As Low As" (1) or "Price Range" (0)

=== Format of '''bundle_skus''' ===

Settings per sku (called selection in Magento) are separated by colon. More skus are separated by semicolon.

"Option title in admin store:sku-of-product:[selection_qty]:[selection_can_change_qty]:[position]:[is_default]:[selection_price_value]:[selection_price_type];"

* '''Option title in admin store''': (string) The title of the option that is set in the admin store. It is used as a kind of code.
* '''sku-of-product''': (string) The sku of the product to associate with the option. It has to exist.
* '''selection_qty''': (float) Optional. The default selection quantity. Defaults to 1.
* '''selection_can_change_qty''': (bool) Optional. Specifies whether the user can change the quantity. Defaults to 1.
* '''position''': (int) Optional. Position of selection. Defaults to 0.
* '''is_default''': (bool) Optional. Sepcifies whether the selection is the default selection. Defaults to 0.
* '''selection_price_value''': (float) Optional. The price of the selection. Applies only when column price_type is set to 1. Defaults to 0.
* ''' selection_price_type''': (int) Optional. Whether the price value is fixed (0) or a percentage (1). Defaults to 0.

=== Format of '''bundle_skus''' ===

Settings per option are separated by colon. More options are separated by semicolon.

You can delete an option by prepending it with a minus "-". You can delete all existing options by specifying an option with the title "-*" (minus followed by asterisk). Deletions are handled before creations, regardles of position. So you may delete and create an option in one step.

"Option title in admin store:[Option title in item store]:[type]:[required]:[position];"

* '''Option title in admin store''': (string) The title of the option that is set in the admin store. It is used as a kind of code.
* '''Option title in item store''': (string) Optional. The title of the option that is set in the current store. Defaults to the admin store title.
* '''type''': (string) Optional. The input type to be used on the option. One of select, radio, checkbox or multi. Defaults to select.
* '''required''': (bool) Optional. Whether the user must do a selection on the option. Defaults to 1.
* '''position''': (int) Optional. Position of the option. Defaults to 0.

== Samples ==

=== Minimal version to set one option with two selections. ===

<pre>
....,bundle_skus,....
....,"CPU:athlon;CPU:intel",....
</pre>

=== Full blown version, delete all existing options, create new ones ===

<pre>
....,store,bundle_options,bundle_skus,....
....,en,"-*;CPU:Central Processing Unit:radio:1:0;RAM:Random Access Memory:multi:1:1","CPU:athlon:1:0:1:0;CPU:intel:1:0:0:1;RAM:1GB;RAM:2GB;RAM:4GB",....
</pre>

== Configuration ==

In the configuration you may change the defaults used for all optional settings.

----
''Back to [[Product Import Related Plugins]]''

Current Version of Magmi also on Github

It would be cool, if the Github Repo would have the same Release (currently this is 0.7.18 on http://sourceforge.net/projects/magmi/ ) as on Sourceforge. It would be good, if there would be only one release (currently there are two folders with older releases in the Github Repo)

To provide older releases for users, it would be great to work with the Relase Feature of Git.

Stock Management

I'm having an issue where some products have:

• "use_config_manage_stock" = 1; and others have:
• "use_config_manage_stock" = 0 and "manage_stock" = 1 or 0

The Magmi import will always overwrite these values because of the code:

// line 898 - magmi_productimportengine.php
if(!isset($item["manage_stock"]))
{
    $item["manage_stock"]=1;
    $item["use_config_manage_stock"]=0;
}

My import doesn't contain fields/values for "manage_stock" or "use_config_manage_stock".
The import process enters the "IF" for these rows and overwrites the values.
Currently the only way I can see to get around this is to have these values on my import, which just isn't feasible because the values are being updated quite often by our admins.

I simply want a way to leave these values as they are during an import.
My temporary fix is:

if(!isset($item["manage_stock"]))
{
  $item["manage_stock"]=1;
  $item["use_config_manage_stock"]=0;
}
else if($item["manage_stock"] === "ignore") {
  unset($item["manage_stock"]);
  unset($item["use_config_manage_stock"]);
}

With this I can give "manage_stock" an ignore value if I don't want any changes to the current values.

Plugin SKUFinder - not save and read settings

Plugin SKU Finder cannot save and read settings.
When I create by hand conf file, then read on import. However, in the UI settings are not displayed. When the settings edit in the UI that are not saved.

Undefined index in itemprocessors/itemindexer

Hi,
when running magmi-cli I get this error:

PHP Notice: Undefined index: 1 in /var/www/vhosts/chs.local/httpdocs/magmi/plugins/extra/itemprocessors/itemindexer/otfindexer.php on line 226
PHP Notice: Undefined index: 1 in /var/www/vhosts/chs.local/httpdocs/magmi/plugins/extra/itemprocessors/itemindexer/otfindexer.php on line 182

Products still seem to import but with 80k products it's an issue due to the size of the log files after a cli-import.

Slugger class is missing several national letters...

I got issue with generated urls by On the fly category creator/importer module. To function properly with slovak (and czech) language I had to append
'Č'=>'C', 'č'=>'c', 'Ľ'=>'L', 'ľ'=>'l', 'Ĺ'=>'L', 'Ť'=>'T', 'ť'=>'t', 'Ň'=>'N', 'ň'=>'n', 'Ŕ'=>'R', 'ŕ'=>'r', 'Ř'=>'R', 'ř'=>'r'
to $_translit property in Slugger class (magmi_utils.php)

basedir="../../../.." for magmi.ini.default

It should correct the 'basedir="../.."' to be 'basedir="../../../.."' for default configure file 'magmi.ini.default', if we use 'modmain clone' to install this project under the magento root directory.

It'd be better to link the image, instead of copy a new one, for ImageAttributeItemProcessor.php

At present, The plugin 'ImageAttributeItemProcessor.php' copys a image from media/import/xyz.jpg to media/catalog/product/x/y/xyz.jpg.
But, I think it'd be better to link the image with a relative path.
cd ./meda/catalog/product/
mkdir -pv x/y
cd x/y/
ln -s ../../../../import/xyz.jpg -t ./

Bring back websites-column

Why is the websites-column removed? I'm currently running into an issue where I have 3 websites with 12 languages each. There is one website with all products, and 2 websites with a sub-set of products.

I try to use the websites-column, but it does nothing (as expected when a feature is obsolete).

So I try to populate the store-column with a comma-separated list of either 12, 24 or 36 values (12 languages for each website). But still all the products get added to all 3 websites.

So I created a post-magmi-function where my SQL the database to set the correct website ID's. This works, but as soon as magmi runs an update or something, store gets defaulted back to 'admin' and all websites are included again.

So I was wondering, is this a bug or a feature? Because I've been trying for a couple of hours now how to setup my CSV so a product gets imported in website A and B, but not in C.

What was the main reason for obsoleting the websites-column anyway?

Flushing import results

I have setup an import script that runs from the Magento Admin and utilizes the Magmi import via Data Pump.

I'm having an issue where some import steps send a flush() after they have completed and stops headers being sent, in this case a Redirect to a success page.

This is by no means a major issue, but it would be nice to have a profile setting to disable flushing. Or even something in Data Pump that, if it's enabled, disables flushing.

"state" not being writable

Upon installing it gives an error about "state" not being writable, which doesn't exist. I have to create it & then make it writable. You should have it automatically create it, or check the empty folder into VCS.

[Proposal] Use Magento backend

First of all, I really love Magmi, saved me from a lot of import problems :)

Would it be an idea to use the Magento extension architecture to make an interface in the Magento backend, like other plugins? So instead of going to magmi/web/magmi.php, just log in in the backend, so we can rely on the user/roles etc, and provide a more recognized interface?
Or are there specific reasons why this isn't done?
An alternative could be a simple frontend with limited options. Eg. select a profile and upload a file, and leave the rest of the configuration as was before, so the developer can configure Magmi and just let the end-user use the Magento interface.

Value replacer not working when import value contains some characters

The easiest way to replicate : replace an attribute by itself (so no php syntax errors are possible). For example :

Value replacer configuration :
Replaced attributes :
greenock_datum_laatste_verkoop
New value for greenock_datum_laatste_verkoop : {{{item.greenock_datum_laatste_verkoop}}}

Now make sure that import string value contains characters like in for example (date value) : "07/13/2013 00:00:00"

-> import value doesn't get "updated" : just an empty result is returned

Plugin SKU Finder - error in sql

sql query in SKU Finder is incorrect:

$sql="SELECT sku FROM ".$this->tablename("catalog_product_entity")." as cpe JOIN
catalog_product_entity_".$attinfo["backend_type"]. " ON value=? AND attribute_id=?";

should look like this:

//now find sku
$sql="SELECT sku FROM ".$this->tablename("catalog_product_entity")." as cpe JOIN
catalog_product_entity_".$attinfo["backend_type"]. " ON cpe.entity_id = catalog_product_entity_varchar.entity_id AND value=? AND attribute_id=?";

Emptying / Deleting varchar data when missing attribute data

Hi Dweeves - We have some extra text attributes for InStore stock qtys. We were running 0.7.18 and found that when Stock Qty reached 0, it was not updating the field because I guess it read it as a null value and didn't update.

We migrated from 0.7.18 to 0.7.19_git as it seemed to resolve our issue with 0's in text fields. The problem of course is that in PHP 0 == false == null.

in 0.7.19_git, you're now handling it differently for text fields so that if the field is empty, it REMOVES the attribute, which has caused us a bit of grief, because we have Product Managers that fill in the gaps where our automation can't work due to insufficient information from the ERP system.

What's happened now is that Magmi removed that information where we sometimes filled with Magmi and sometimes left it alone for the Product Managers to fill for us. Now when we left it empty, Magmi removed these attribute options from the MultiSelect.

Line 739 of productimportengine.php has if($ovalue=="MAGMI_UNHANDLED") then sets $ovalue as false; but it seems MAGMI_UNHANDLED is not actually implemented anywhere and additionally, once we implemented it in magmi/plugins/inc/magmi_defaultattributehandler.php, then approx Line 768 if ($ovalue==null) evaluates false as null and still deletes it. So needs to be evaluated with ($ovalue===null).

I'm not clear if I've really got my head around this yet but I have a working solution at the moment where I can choose to ignore / not update, using MAGMI_UNHANDLED instead of a blank field. I will try and put it all together in a pull request.

Support for 1.8?

The Magento versions listed in

magmi/web/magmi_config_setup.php
<?php foreach(array("1.7.x","1.6.x","1.5.x","1.4.x","1.3.x") as $ver){?>

Has Magmi been tested against Magento 1.8?

[Category creator] Root categories behaviour changed

The documentation for the On the fly category creator/importer says:

IMPORTANT
STORE CATEGORY ROOT NAMES HAVE TO BE PUT BETWEEN SQUARE BRACKETS [] TO BE IDENTIFIED AS CATEGORY ROOT NAMES

But that changed in this commit: 6c4a54b

Before that commit, I could set categories to [rootcat]/[cat]/[sub], but after that commit, it creates a new category called [rootcat](with the brackets).

Is this intended or am I misunderstanding the docs?

It doesn't import anything, "query was empty"

On every record I get this error:

SQLSTATE[42000]: Syntax error or access violation: 1065 Query was empty - ERROR ON RECORD #443

FYI I've gotten magmi to work in the past, not sure if this is a new bug? My file imports mostly fine into Magento's data flow (it doesnt assign the category)