#80 1.13x Indexing Issue

v1.0_(example)
open
nobody
1
2014-09-09
2013-12-05
S.Peery
No

When importing files using Magmi on a 1.13.02 or newer implementation, URL rewrites are not generated correctly. The issue can be rectified using the following SQL statement after creation, but this is not sustainable.

TRUNCATE catalog_product_entity_url_key;
set @position := 0; 
INSERT INTO catalog_product_entity_url_key 
SELECT
   null
 , url_key_col.entity_type_id
 , url_key_col.attribute_id
 , url_key_col.store_id
 , url_key_col.entity_id
 , url_key_col.value
FROM
 catalog_product_entity_varchar url_key_col
 LEFT JOIN eav_attribute a
  ON a.attribute_id = url_key_col.attribute_id 
WHERE
 a.attribute_code = 'url_key'
ON DUPLICATE KEY UPDATE value = CONCAT(VALUES(value), '-', @position := @position + 1)
;

Discussion

  • S.Peery

    S.Peery - 2013-12-05

    I should also add that not only are the records not generated at time of import, but they also will not generate when a new URL Rewrites index is performed.

     
  • Sebastien Bracquemont

    Hi, thanks for spotting. In fact this is due to EE 1.13/CE 1.8 Database major change about url keys.
    They added a table. I need some time to analyze CE 1.8 DB changes in order to adapt magmi.
    However, your request could be done by modifying slightly default attribute processor plugin and modifying handleUrl_keyAttribute method.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks