Missing Product Descriptions after upgrade from 1.4 to 1.6

[tivicrdotcom]

Hello fellow geeks, So after two days of literally living on my desk, I successfully migrated my shop from 1.4.7 to 1.6 and everything looks good. No issues so far but all products are missing the short and long descriptions. Any clue?

The site can be seeing here:

Old site:
http://www.tivicr.com/es/

 

Upgraded site:
http://www.tivicr.com/fishing/es/

 

Thanks in advance,

AJ

[tivicrdotcom]

Another issue and it could be related is that customers can't add items to cart, is like the product page is missing stuff

UPDATE: So ignore this because for some reason the db didn't updated the quantities, I did it manually on one product, not before being warned that the product must be on the default category so I selected again the default category under the product and then it allowed me to change the quantity and it worked. So it seems as if the db upgrade missed some items such as quantities, and product description were not fully migrated.

Edited October 13, 2016 by tivicrdotcom (see edit history)

[tivicrdotcom]

So overall on the upgrading process from 1.4.7 to 1.6, for some reason the db missed the product quantities, short/long description and wouldn't surprise me attributes as well but this last one haven't tested.

[tivicrdotcom]

So checking the db's from the live site (1.4.7) and the future one (1.6), they both have the "ps_product_lang" table with what it looks like the same values. I ran a query with that table from the old site into the new one and got this error:

Unknown column 'pl.id_shop' in 'on clause'

SELECT `name`, `meta_title`, `meta_description`, `meta_keywords`, `description_short`				FROM `ps_product` p				LEFT JOIN `ps_product_lang` pl ON (pl.`id_product` = p.`id_product` AND pl.id_shop = 1 )				 INNER JOIN ps_product_shop product_shop		ON (product_shop.id_product = p.id_product AND product_shop.id_shop = 1)				WHERE pl.id_lang = 2					AND pl.id_product = 398					AND product_shop.active = 1 LIMIT 1

I kind of figured something like that would happen because you cannot simply go hardcore db to db from 1.4 to 1.6. so I reverted the process and back to where I started. Anybody has any clue?

cheers,
AJ