Timeline for Set Category Product Position of Products
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 15, 2017 at 16:40 | comment | added | Jey DWork |
Mage::getSingleton('catalog/category_api')->assignProduct is truly insane in terms of resource/time consumption. As soon as you have a couple of thousands products of which you want to adjust the position regularly you really should go for this SQL based approach.
|
|
| Jun 14, 2016 at 15:16 | comment | added | Darren Felton | I stumbled upon this post again randomly and it's interesting to see how things change. These days I would probably use your solution over the API that I had recommended as it eliminates a lot of the overhead that Magento's save methods often have. Especially with large data sets I more and more resort to straight SQL queries (keeping in mind however, that any event observers are lost using such an approach). Anyhow.. +1 for direct SQL :) | |
| Jan 13, 2015 at 20:54 | comment | added | Peter O'Callaghan | Nice, I've had very little exposure to the API, good to know. | |
| Jan 13, 2015 at 19:12 | comment | added | Darren Felton | There is an API method specifically for this, please see my answer. | |
| Jan 13, 2015 at 18:20 | history | answered | Peter O'Callaghan | CC BY-SA 3.0 |