Similar as in #2 for Akeneo 1.5 I wanted to ask about the state of PIMGento-2 compatibility with Akeneo 1.6.

The readme so far does not state anything about Akeneo in that version 1.6, last mentioned version is 1.5.

Background

We'd like to use PIMGento-2 in a Akeneo 1.6 based project but so far (because auf PIMGento-2) we're using Akeneo 1.5 because it's documented that way in the readme.

References:

• #2
• Agence-DnD/PIMGento#140
• https://github.com/akeneo-labs/EnhancedConnectorBundle

The module was installed via Composer into a Magento 2.0.2 environment. When I attempt to upload the file after clicking the "Import" button, nothing is outputted in the log. Upon further inspection I discovered the POST request is receiving a 500 response.

Where can I start to debug this? I initially suspected this is occuring because it cannot write to the directory it needs to write to so that the file is temporarily saved for processing by PIMGento, but I am not sure where that location is.

Here is the payload:

Content-Disposition: form-data; name="file"; filename="PIMcategories.csv"
Content-Type: text/csv

Here is the actual header itself:

{"name":"PIMcategories.csv","type":"text\/csv","error":0,"size":123,"file":"PIMcategories_1.csv"}

cc @magentix

Thanks for the help!

Hi,

i just stumbled across a pretty strange issue which took me a while to hunt down:
There is an attribute name "tested". Now the attribute options are something like this: "dinen123_tested", "tested_for_fire".
Now this query is used to replace the options with the entity id's:

SELECT 
    DISTINCT `p`.`sku`, `p`.`_entity_id` AS `entity_id`, 
    GROUP_CONCAT(`c`.`entity_id` SEPARATOR ",") AS `tested-de_DE` 
FROM 
    `tmp_pimgento_entities_product` AS `p`
    INNER JOIN `pimgento_entities` AS `c` 
        ON FIND_IN_SET(
            REPLACE(`c`.`code`, "tested_", ""),
            `p`.`tested-de_DE`
        )
        AND `c`.`import` = "option" GROUP BY `p`.`sku`

The REPLACE will remove all appearings of "tested_". But this means that all attribute options with "tested_" in it cannot be mapped.

After modifying the query to use "TRIM" instead, it seems to be working better:

SELECT 
    DISTINCT `p`.`sku`, `p`.`_entity_id` AS `entity_id`, 
    GROUP_CONCAT(`c`.`entity_id` SEPARATOR ",") AS `tested-de_DE` 
FROM 
    `tmp_pimgento_entities_product` AS `p`
    INNER JOIN `pimgento_entities` AS `c` 
        ON FIND_IN_SET(
            TRIM(LEADING "tested_" FROM `c`.`code`),
            `p`.`tested-de_DE`
        )
        AND `c`.`import` = "option" GROUP BY `p`.`sku`

Regards,

Hi,
I have tried several times to import products csv file that contains some configurable products, but I can't manage to create them as configurables, they are always created as simple products. I think I'm missing something but I don't know what.
The Pimgento2 configurations are very simple, so I guess that the problem can be in the csv file structure or maybe with the variants file.

Variants file is just:
code;axis;label;type
accessories_se_variation;sap_material_description;accessories se variations;VARIANT

What I have seen is that in my products file the column groups is empty, is that ok?

Thanks for your help

First import.. a CSV file with 13 rows. No product gets imported

SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (magento.catalog_product_entity, CONSTRAINT CAT_PRD_ENTT_ATTR_SET_ID_EAV_ATTR_SET_ATTR_SET_ID FOREIGN KEY (`attribute_s

Hi,

I got a bug when I try to use multiple attribute mapping with the same pim code. I want to set the same image (field image in my csv) to thumbnail, small_image and image attribute in Magento 2.

So I apply this mapping :

In that example, the tmp_pimgento_entities_product table created by the import doesn't have all fields that I want.
We only had the field image and thumbnail. It seems that the module take only the last attribute mapped. I tried to change the name of pim column, and my field small_image was in the table.

I search why in the code, and I guess it is when we add product required data. More precisely, in file Product/Model/Factory/Import.php, function addRequiredData().
I did not go further in my search.

Is it possible to fix it ?
Thanks a lot.

Hi,

this is not a issue, but juste a question.

on Pimgento for Magento 1, there was lots (and very useful) of configurations about crons to import automatically new files for each profiles.

on Pimgento for Magento 2, i do not find it. Is it in the roadmap ?

best regards,

Laurent

Hello,

Dans le ReadMe, il est indiqué qu'il n'est pas nécessaire d'utiliser le bundle EnhancedConnectorBundle pour le format d'export si Akeneo est en version 1.5

Hors ce n'est pas le cas, PimGento refuse l'import du format CSV natif d'akeneo pour les familles de produit et les attribut produit (je n'ai pas pu essayer les produits).

Il faudrait discuter de la prise en charge du format natif, mais en attendant, je conseillerais de modifier votre ReadMe.

Laurent

I’m trying to create demo environment with Akeneo CE 1.5 and Magento 2.1 CE by using Pimgento.
I get this weird error message at the end of installation process:
ubuntu@ip-172-31-46-149:/var/www/html/pim-community-standard$ sudo php composer.phar require akeneo-labs/pim-enhanced-connector:~1.2
Running composer as root/super user is highly discouraged as packages, plugins and scripts cannot always be trusted
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

Problem 1
- akeneo/pim-community-dev v1.5.5 requires doctrine/migrations 1.0.0-alpha3@alpha -> satisfiable by doctrine/migrations[v1.0.0-alpha3].
- akeneo/pim-community-dev v1.5.5 requires doctrine/migrations 1.0.0-alpha3@alpha -> satisfiable by doctrine/migrations[v1.0.0-alpha3].
- Removal request for doctrine/migrations == 1.0.0.0-alpha3
- Installation request for akeneo/pim-community-dev (locked at v1.5.5) -> satisfiable by akeneo/pim-community-dev[v1.5.5].

Installation failed, reverting ./composer.json to its original content.
ubuntu@ip-172-31-46-149:/var/www/html/pim-community-standard$

Lors de l'import du fichier d'attribut suivant :

type;code;label-fr_FR;group;unique;useable_as_grid_filter;allowed_extensions;metric_family;default_metric_unit;reference_data_name;localizable;scopable
pim_catalog_identifier;sku;Réf.;default;1;1;;;;;0;0
pim_catalog_text;name;Nom;default;0;1;;;;;1;0
pim_catalog_simpleselect;color;Couleur;color;0;1;;;;;0;0
pim_catalog_textarea;description;Description;default;0;0;;;;;1;0
pim_catalog_price_collection;price;Prix;price;0;0;;;;;0;0
pim_catalog_boolean;status;Status;default;0;0;;;;;0;0
pim_catalog_simpleselect;size_pant;"Taille pantalon";size;0;1;;;;;0;0
pim_catalog_simpleselect;size_shirt;"Taille T-shirt";size;0;1;;;;;0;0
pim_catalog_image;image;Image;media;0;0;jpg;;;;0;0
pim_catalog_file;manual;"Manuel d'Utilisation";media;0;0;pdf;;;;1;0

Il m'est indiqué que la colonne "families" est manquante, alors que dans Akeneo 1.5.2, ce n'est plus le fichier des attributs qui porte le lien avec les familles, mais le fichier des familles qui indique de quelles attributs est constitué une famille.

J'ai utilisé les profils Akeneo natifs suivant :
Akeneo CSV Connector / Attribute export in CSV
Akeneo CSV Connector / Family export in CSV

J'ai eu le message d'erreur suivant durant un test d'import :

Colinne label introuvable

Colinne => Colonne ;)

Hi,

when selecting a value from a dropdown for a product, it is correctly imported in Magento.
Now switch back the value to "nothing" in Akeneo and reimport. The value in Magento is not changing.

I would expect that it changes back to "noting", too.

Regards,

First of all I want to say thank you for releasing PIMGento-2! :-)

The README says, PIMGento-2 supports Akeneo 1.3+1.4.

As the EnhancedConnectorBundle is now also available for Akeneo 1.5 and nothing big has changed in the CSV output between 1.4->1.5, I think that PIMGento-2 should also work with Akeneo 1.5?

If this is true, maybe you could add V. 1.5 in the README as many new users want to use the newest Akeneo version.

My csv file contains columns like

description-de_DE-ecommerce
description-en_US-ecommerce
name-de_DE-ecommerce
name-en_US-ecommerce
price-de_DE-ecommerce-EUR
price-de_DE-ecommerce-USD
price-en_US-ecommerce-EUR
price-en_US-ecommerce-USD

during import "columPrefix" which exists more than one time (description, name, price,...) the values array gets overriden with the next column in the foreach loop. So the values array takes always the last column. In my example my values array contains

description-en_US-ecommerce
name-en_US-ecommerce
price-en_US-ecommerce-USD

My magento shop setup is localized with "de_DE".

When reimporting the attributes, the labels are duplicated.
In the table "eav_attribute_label" there are several entries for the same attribute_id:
424 132 0 Headline
425 132 1 Headline
562 132 0 Headline
563 132 1 Headline
5 132 1 Headline
6 132 0 Headline
147 132 0 Headline
148 132 1 Headline
286 132 0 Headline
287 132 1 Headline

This results in exceptions in the frontend:
Item (Magento\Catalog\Model\ResourceModel\Eav\Attribute\Interceptor) with the same id "90" already exist

Any ideas?

Hi,

on Magento EE 2.1 RC3, they have added some staging functionality. The pb is that when the staging module is active (it is possible to upgrade to the EE 2.1 version without installing it), it changes all the database structure for products, categories, and others...

more info here: http://devdocs.magento.com/guides/v2.0/release-notes/backward-incompatible-changes-2.1.html

For example, the entity_id field of all the sub tables catalog_product_entity_* does not exists any more, and a new field "row_id" has been added...

=> Pimgento will not be compatible with EE 2.1 + Staging

I think it will be a good think to add a warning on the readme to say that it is not compatible with the "staging" module of Magento EE 2.1 for the moment.

What do you think about it ?

Laurent

Hi,

is there a way to import swatch attributes to Magento 2?
I've looked into the Pimgento settings, but in attribute mapping there is no possibility to choose swatch as type.

Any help would be much appreciated.

Regards,

Hi,

I got and encoding problem when I import csv with special chars (such as ê é à ...).
Can you add an option for specify file encoding ? Default isn't UTF-8 I guess.

The problem is with query like this one :

LOAD DATA INFILE 'myFile' REPLACE
INTO TABLE myTable
...

I tried to add CHARACTER SET UTF8 after INTO TABLE and it worked.

Thanks.

Hi,

for categories and products the url rewrites are generated like this:
'entity_type' => new Expr('"product"'), 'entity_id' => '_entity_id', request_path' => new Expr('CONCAT(' . $column . ', ".html")'), target_path' => new Expr('CONCAT("catalog/product/view/id/",_entity_id)'), redirect_type' => new Expr('0'), store_id' => new Expr($store['store_id']), is_autogenerated' => new Expr('1'),

Right now we have the problem that magento is configured to use a trailing slash instead of .html
So the import breaks the url structure somehow.
This should be configurable, or even better, respect the original magento settings during import.

Thank you!

Regards,

Sur un magento 2 vierge, j'ai associé le store-view default à la locale fr_fr

Lors de l'import du fichier de test suivant :

code;parent;label-fr_FR
master;;Vêtements
tshirts;master;T-Shirts
pants;master;Pantalons

Aucun nom de catégories n'est affichée dans l'arbre :

In pimgento there is an option in admin configuration that allow user to enable a cron job to import csv files to magento, is there any option in pimgento 2 enable a cron job? Where?

Regards

Hi !

about the following 2 points in the roadmap :

• Image files import
• Link related products (related, cross-sells, up-sells)

how can we (Smile) participate ? can we work on the linked related products (bases on what you have done in Pimgento1) ?

Lors de test de l'import des familles de produit, pour un akeneo configuré avec uniquement la locale fr_FR, avec le fichier suivant :

code;label-fr_FR;attributes;attribute_as_label;requirements-magento
shirt;T-shirt;sku,name,color,description,price,status,size_shirt,image,manual;sku;sku,name,description,price,status,image
pant;Pantalon;sku,name,color,description,price,status,size_pant,image,manual;sku;sku,name,description,price,status,image

J'ai obtenu le message d'erreur suivant :

Colinne label introuvable

Hors la colonne label ne peut exister car elle est localisée et est donc suivi du suffix de langue.

Si par contre je modifie le fichier d'import ainsi :

code;label-fr_FR;label;attributes;attribute_as_label;requirements-magento
shirt;T-shirt;T-Shirt;sku,name,color,description,price,status,size_shirt,image,manual;name;sku,name,description,price,status,image
pant;Pantalon;Pant;sku,name,color,description,price,status,size_pant,image,manual;name;sku,name,description,price,status,image

l'import se déroule bien

This bug is coming from the pull request 34, i forgot to add this line:

use \Magento\Framework\DB\Adapter\AdapterInterface;

on the file https://github.com/Agence-DnD/PIMGento-2/blob/master/Product/Model/Factory/Import.php#L15

because we use it here https://github.com/Agence-DnD/PIMGento-2/blob/master/Product/Model/Factory/Import.php#L918

i'm sorry for this mistake :(

Hi,

when creating a simple product, it is automatically enabled.

when creating a configurable product, it is not, and the "status" attribute has no value in the catalog_product_entity_int table.

is it normal (we have to activate it manually), or is it a bug ?

Hi,

Sort of works for me but some small snags....
After some research it appears the file input element is sized at 1000x1000 and overlaps the button, which means when you think you are pressing the import button you actually are clicking again on the file input.

Have not had much luck with trying to resize the input or changing the z-order. For now I have changed Import/view/adminhtml/web/css/style.css

.pimgento-step .primary {
    float:left
}

So the button aligns with the uploaded file and is not over lapped.... then it works

Now just need to figure out why it does not import Chinese (cn_ZH)....

Versions Magento 2.1.0 PimGento2 latest Akeneo 1.5 Chrome 52.0.2743.116

I just tried to install this extension against Magento 2.1.0, but composer returned these errors blow.

Problem 1
- Conclusion: don't install agencednd/module-pimgento 100.0.12
- Conclusion: don't install agencednd/module-pimgento 100.0.11
- Conclusion: don't install agencednd/module-pimgento 100.0.10
- Conclusion: don't install agencednd/module-pimgento 100.0.9
- Conclusion: don't install agencednd/module-pimgento 100.0.8
- Conclusion: don't install agencednd/module-pimgento 100.0.7
- Conclusion: don't install agencednd/module-pimgento 100.0.6
- Conclusion: don't install agencednd/module-pimgento 100.0.5
- Conclusion: don't install agencednd/module-pimgento 100.0.4
- Conclusion: don't install agencednd/module-pimgento 100.0.3
- Conclusion: don't install agencednd/module-pimgento 100.0.2
- Conclusion: don't install agencednd/module-pimgento 100.0.1|remove magento/framework 100.1.0
- Conclusion: don't install agencednd/module-pimgento 100.0.1|don't install magento/framework 100.1.0
- Installation request for agencednd/module-pimgento ^100.0 -> satisfiable by agencednd/module-pimgento[100.0.1, 100.0.10, 100.0.11, 100.0.12, 100.0.2, 100.0.3, 100.0.4, 100.0.5, 100.0.6, 100.0.7, 100.0.8, 100.0.9].
- agencednd/module-pimgento 100.0.1 requires magento/framework 100.0.* -> satisfiable by magento/framework[100.0.2, 100.0.3, 100.0.4, 100.0.5, 100.0.6, 100.0.7, 100.0.8, 100.0.9].
- Can only install one of: magento/framework[100.1.0, 100.0.2].
- Can only install one of: magento/framework[100.1.0, 100.0.3].
- Can only install one of: magento/framework[100.1.0, 100.0.4].
- Can only install one of: magento/framework[100.1.0, 100.0.5].
- Can only install one of: magento/framework[100.1.0, 100.0.6].
- Can only install one of: magento/framework[100.1.0, 100.0.7].
- Can only install one of: magento/framework[100.1.0, 100.0.8].
- Can only install one of: magento/framework[100.1.0, 100.0.9].
- Installation request for magento/framework (locked at 100.1.0) -> satisfiable by magento/framework[100.1.0].

composer.json of this repository specifies "100.0." for magento/framework, but 2.1.0 uses "100.1.".

Hi,

this is not a issue, but juste a question.

on a magento with 3 websites (corresponding to 3 channels), how to import product that will be enable on only 2 websites ? is ther a specific mapping to do ? or do we need a specific attribute ?

best regards,

Laurent

I've tried different attribute codes in Akeneo but nothing happens:
quantity_and_stock_status
is_in_stock

How can i import a stock level from Akeneo to Magento2?
Maybe this needs some sort of attribute mapping?

Any help would me much appreciated.

Hi,

when trying to import a multiselect attribute only the first value is selected.

Example:
An multiselect attribute with the possible values "value1", "value2", "value3", "value4", "value5", "value6"
For the product the according column looks like this: value1,value2,value3

After the import only value1 is selected for the product.

Any ideas?

When trying to import a metric type attribute from Akeneo only the unit is imported, not the value.

Example:
We have a metric attribute named "insulation". The csv has this columns:
insulation insulation-unit
50.0000 MILLIMETER

Because PIMGento2 finding the colum prefix like this: $columnPrefix = explode('-', $column);
only the last column with the same beginning is used as value source.

Best solution IMO would be to combine the value and unit into one attribute field during import (in our example named "insulation"). Alternatively the unit could be saved in a seperate attribute.

Please correct me if i'm missing anything here :)

Test case : we have a category defined on a few locales with custom url keys ; and to match it with a following Akeneo import, we pre-created an entry in pimgento_entities (with correct code). Then we start the category import containing this category but it fails with the following error :

[15:51:46] SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'collections/must-have.html-3' for key 'URL_REWRITE_REQUEST_PATH_STORE_ID', query was: 

INSERT INTO `url_rewrite` (`url_rewrite_id`, `entity_type`, `entity_id`, `request_path`, `target_path`, `redirect_type`, `store_id`, `is_autogenerated`) SELECT `tmp_pimgento_rewrite`.`url_rewrite_id`, "category" AS `entity_type`, `tmp_pimgento_rewrite`.`entity_id`, `tmp_pimgento_rewrite`.`request_path`, `tmp_pimgento_rewrite`.`target_path`, 0 AS `redirect_type`, `tmp_pimgento_rewrite`.`store_id`, 1 AS `is_autogenerated` FROM `tmp_pimgento_rewrite` WHERE (`request_path` <> `old_request_path` AND `url_rewrite_id` IS NOT NULL) ON DUPLICATE KEY UPDATE `url_rewrite_id` = VALUES(`url_rewrite_id`), `entity_type` = VALUES(`entity_type`), `entity_id` = VALUES(`entity_id`), `request_path` = VALUES(`request_path`), `target_path` = VALUES(`target_path`), `redirect_type` = VALUES(`redirect_type`), `store_id` = VALUES(`store_id`), `is_autogenerated` = VALUES(`is_autogenerated`)

In database we can see the following :

• Current url_rewrite table
  
• Temporary tmp_pimgento_rewirte table
  
• Note that URL keys are correctly generated in tmp_pimgento_entities_category
  

In the code, it may be a problem in \Pimgento\Import\Helper\UrlRewrite::rewriteUrls, though I didn't manage to find how to fix the query... The store_id is pasted inside the "SELECT" part of the query (line 98), but there is nothing in the "JOIN" part to restrain the insert to the same store...

Expected : the url keys are udpated according to the localized data, in the correct stores. A temporary fix would be a way to disable the url updates...

In Magento 2.1, the value to put in the website_id field of the table cataloginventory_stock_item has change from 0 (in magento 2.0) to 1.

In order to have the good value, the best way is to use the native method Magento\CatalogInventory\Model\Configuration::getDefaultScopeId

https://github.com/magento/magento2/blob/2.1/app/code/Magento/CatalogInventory/Model/Configuration.php#L149

In magento 2.0, this method return 1.
In magento 2.1, this method return 0.

It could be used here : https://github.com/Agence-DnD/PIMGento-2/blob/master/Product/Model/Factory/Import.php#L730

If the delimiter and the enclosure from the export file is not a static default, importing the CSV file is not possible.

Of course one could edit the config, but it would be much better to have an item in the backend for that.

Hi guys,

I see in the roadmap that there is a Command line tool (bin/magento) options for imports item.

Is it currently in development or not ?

Thanks.

Bonjour,

Si plus d'un website est paramétré dans Magento (avec un mapping tel que 1 website = 1 channel), l'import de produit n'initialise pas qu'une seule ligne par produit simple dans la table cataloginventory_stock_item, mais initialise une ligne par produit et par website, ce qui engendre par la suite l'erreur suivante dès qu'une collection de produit est chargée avec les données de stock (comme sur la grille des produit en BO par exemple):

Item (Magento\Catalog\Model\Product\Interceptor) with the same id "XXX" already exist

le problème semble venir de la méthode Pimgento\Product\Model\Factory\Import::initStock qui boucle sur tous les websites.

Laurent

hi,

in the Attribute Type helper, the given pim type for price is "pim_catalog_price" :

https://github.com/Agence-DnD/PIMGento-2/blob/master/Attribute/Helper/Type.php#L29

but in the fixtures, it is "pim_catalog_price_collection" :

https://github.com/Agence-DnD/PIMGento-2/blob/master/Attribute/fixtures/attribute.csv#L27

What is the good attribute type to use ?

Best Regards,

Laurent

Bonjour,

lors de l'import des CSV des variants puis des produits, afin de créer les configurables et les simples dans Magento, l'alimentation de la table cataloginventory_stock_item a été oubliée pour les configurables.

Etant donné qu'aucune ligne n'est enregistrée dans la table, les valeurs par défaut apparaissent dans lors de l'édition des configurables en BO.

Hors ces valeurs par défaut induise en erreur car Magento a mis par défaut les valeurs "Yes" et pas "Non", et "In Stock" et pas "Out of Stock", du coup on pense que tout est bien configuré, alors qu'en base rien n'est enregistré, et du coup la génération des index n'est pas bonne et indique que le configurable n'est pas en stock, ce qui empêche son affichage en FO.

Il faudrait donc initialiser le stock des produits configurables (lors de leur création uniquement).

Cordialement,

Laurent

Hi,

Did someone already got this issue.

In my Akeneo export I got several groups.

For example group shirt with 200 sku linked to it (same value in groups column in csv file) and all axis are OK

But in my magento "configurable item" i got only 150 sku.

Didn't know why there is some miss like that...

Thanks

During the import of the simple product, if it use a family code that has not been imported yet (because of a user mistake), the error message is not user friendly :

[10:26:58] SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (fbd.catalog_product_entity, CONSTRAINT CAT_PRD_ENTT_ATTR_SET_ID_EAV_ATTR_SET_ATTR_SET_ID FOREIGN KEY (attribute_set_id) REFERENCES eav_attribute_set (attribute_set_id) ON DELETE CA), query was: INSERT INTO catalog_product_entity (entity_id, attribute_set_id, type_id, sku, has_options, required_options, updated_at) SELECT tmp_pimgento_entities_product._entity_id AS entity_id, tmp_pimgento_entities_product._attribute_set_id AS attribute_set_id, tmp_pimgento_entities_product._type_id AS type_id, tmp_pimgento_entities_product.sku, 0 AS has_options, 0 AS required_options, now() AS updated_at FROM tmp_pimgento_entities_product ON DUPLICATE KEY UPDATE entity_id = VALUES(entity_id), attribute_set_id = VALUES(attribute_set_id), type_id = VALUES(type_id), sku = VALUES(sku), has_options = VALUES(has_options), required_options = VALUES(required_options), updated_at = VALUES(updated_at)

It could be cool, at the end of the method updateAttributeSetId https://github.com/Agence-DnD/PIMGento-2/blob/master/Product/Model/Factory/Import.php#L293 to add a check if all the products have a value > 0 for _attribute_set_id, and if it is not, return an error like "The family code of some products are unknown"

what do you think about this ?

Hi !

i try to use the "pimgento/product/configurable_attributes" configuration with a scopable attribute

it was to find a solution on the issue #18 by using a scopable attribute status like explain in #15 .

But is seems that this configuration does not work with scopable attribute. It works only with localizable attribute.

We can see it in the code : https://github.com/Agence-DnD/PIMGento-2/blob/master/Product/Model/Factory/Import.php#L190

Best Regards,

Laurent

Magento uses language code zh_Hans_CN so language codes do not match the generated zh_CN....

So probably an Akeneo issue.....

Context : Variants where imported with a gross_price column, with should match the Magento price. The import is first computing the "attribute mapping" set in backoffice, then it creates the configurable products. This does not allow to use the backoffice mapping for configurable products.

Workaround : We overrode the method \Pimgento\Variant\Model\Factory\Import::_columnName to add our mapping, and then we added price in backoffice "configurable" configuration.

Instead of implementing a new class, it could use the same system than the attribute mapping. Alternatively, maybe it could use the attribute mapping after creating the configurables...

Hi guys,

I'm trying to use PIMGento 2 with a new Magento 2 install.
But I got a problem when trying to import categories with PIMGento2 on Magento2.

[11:34:29] Start import 
[11:34:29] Import id: 5707974599448 
[11:34:29] Create temporary table 
[11:34:29] completed 
[11:34:29] Fill temporary table 
[11:34:30] Warning: PDOStatement::execute(): LOAD DATA LOCAL INFILE forbidden in /myPathToProject/vendor/magento/zendframework1/library/Zend/Db/Statement/Pdo.php on line 228

Query is working with mysql directly, but it do no work with php.
I checked my local_infile from mysql, it is ok :

SHOW GLOBAL VARIABLES LIKE 'local_infile';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+ 
| local_infile  | ON    |
+---------------+-------+
1 row in set (0.00 sec)

It looks like a php bug : https://bugs.php.net/bug.php?id=68226

Any ideas about how to fix it ? LOCAL is really usefull in that query ?
Thanks.

Bonjour,

Suite à l'import d'attribut produit, les deux caches suivants sont vidés :

Block HTML
FPC
Mais sur Magento 2, il faudrait aussi vider le cache EAV structure.

Hi,

i'm trying to import variants into Magento.
It works quite ok with one major drawback:
The configurable (parent) product had no name, so i added the name property to the pimgento configuration. After adding a website to shop mapping (base -> shop) the name is now filled with the name of the first variant.

I think it's because of the way the column names are generated:
array(11) { [0]=> string(4) "name" [1]=> string(10) "name-de_DE" [2]=> string(16) "name-de_DE-admin" [3]=> string(15) "name-de_DE-shop" [4]=> string(10) "name-admin" [5]=> string(9) "name-shop" [6]=> string(8) "name-EUR" [7]=> string(14) "name-admin-EUR" [8]=> string(13) "name-shop-EUR" [9]=> string(20) "name-de_DE-admin-EUR" [10]=> string(19) "name-de_DE-shop-EUR" }

In the variant table the column is called "name-de_DE", but in the product table "name-de_DE-shop". As the array is processed in the same order as above and only the first part of the column name ("name") is used as a key for the result array, "name-de_DE-shop" overwrites the correct value from "name-de_DE"

Maybe i'm just looking in the wrong direction, so any help is appreciated ;)

Regards,

Hi,

as far as i can see, the position of a product inside a category is always set to 1 during import (table "catalog_category_product").

I think it would be better if the position value can be configured and bound to a specific attribute.
Maybe the fixed value can serve as a fallback if nothing is configured?

Now, we have no possibility to change the position as it is overwritten with every import.

Regards,

Hi,

During code compilation after installation I am receiving the following error:

    Pimgento\Import\Block\Adminhtml\Import
        Incorrect dependency in class Pimgento\Import\Block\Adminhtml\Import in /opt/bitnami/apps/magento/htdocs/vendor/agencednd/module-pimgento/Import/Block/Adminhtml/Import.php
\Magento\Framework\AuthorizationInterface already exists in context object

I had installed this awhile ago and don't recall observing this same issue. Any ideas how to fix?

If a product has been deleted manually from the Magento BO, it is impossible to reimport it, because the table pimgento_entities is not cleared.

We must do this manually :
delete from pimgento_entities where import='product' and code="xxxxx";

it could be a good idea, before each import process, to clean the table pimgento_entities from the entities that have been manually deleted in the Magento BO.