1
私は非常に具体的な例を挙げることができます。 INDEXING AFTERなぜmagentoはcore_url_rewriteテーブルに重複した書き換えを生成していますか?
mysql> SELECT * FROM core_url_rewrite WHERE target_path = 'catalog/category/view/id/4';
+----------------+----------+-------------+------------+--------------+--------------+----------------------------+-----------+---------+-------------+
| url_rewrite_id | store_id | category_id | product_id | id_path | request_path | target_path | is_system | options | description |
+----------------+----------+-------------+------------+--------------+--------------+----------------------------+-----------+---------+-------------+
| 1508 | 1 | 4 | NULL | category/4_1 | food.html | catalog/category/view/id/4 | 1 | | |
+----------------+----------+-------------+------------+--------------+--------------+----------------------------+-----------+---------+-------------+
1 row in set (0.00 sec)
:インデックス付けする前に
mysql> SELECT * FROM core_url_rewrite WHERE target_path = 'catalog/category/view/id/4';
+----------------+----------+-------------+------------+--------------+--------------+----------------------------+-----------+---------+-------------+
| url_rewrite_id | store_id | category_id | product_id | id_path | request_path | target_path | is_system | options | description |
+----------------+----------+-------------+------------+--------------+--------------+----------------------------+-----------+---------+-------------+
| 1508 | 1 | 4 | NULL | category/4_1 | food.html | catalog/category/view/id/4 | 1 | | |
| 8512 | 1 | 4 | NULL | category/4 | food-1.html | catalog/category/view/id/4 | 1 | | NULL |
+----------------+----------+-------------+------------+--------------+--------------+----------------------------+-----------+---------+-------------+
2 rows in set (0.01 sec)
だから私の質問は、なぜ地球上でMagentoのは、重複したリライトを作成していますか?これはバグですか?
洞察力は非常に高く評価されます。ありがとう!
Aaron
ちょうど冗談です。それは再び起こっています。 –