tbirnseth

An item id is a system generated id that uses the product_id and the options to generate a unique key.  It is how the cart determines if an item has been changed as well as a way to have multiple instances of a product_id in the cart with different option settings.

If you have 2 items in the cart with quantity 1 for the same tee shirt but one's a large and the other is a small, you'll have 2 item_ids.  If you go in and change the small to a large, then the cart will be regenerated with a single item and quantity 2 since they are the same product and options specification.

This id must be maintained between export/import so that the math works.

Hope this helps people understand how these ids are used and generated.

addons must go trought somekind validation process before publication on the markeplace

Why?  This had nothing to do with the addons themselves.  If the addon archives had been extracted/installed via the '+' icon in cs-cart rather than being uploaded via FTP, none of those issues would have happened.  Additionally the description also implies that the practice used would create ownership issues on the site anyway which (depending on what the addon needs to do) could also break that addon. 

If an upgrade completes successfully, why aren't the phinxlog* tables removed?  I understand if there was a problem, but if it's successful they shouldn't be being left in the DB.  Even on failure, I'm not sure how useful they would be.  Minimally they should be exported and put with the upgrade backup.