Just wanted to say "Me Too" to this.
Please correct me if I'm wrong but this is what I think happened.
I think the data integrity problem was in product_productpricelookup
table. I guess when we deleted the product variations the system did not
delete the associated rows in product_productpricelookup. Satchmo/Django
was probably looking at product_product table for product variations
that did not exist, thats why it gave the error "Product matching query
does not exist" when looking at the product_productpricelookup parentid
column.
I hope I'm making sense.
My designer was working on this today, I don't know if she deleted the
variations using Change Configurable Product or /admin/product/product/
I'm using satchmo 0.9
Jay Hargis wrote:
if you delete product variations without using the variation manager,
you can't get to the parent (configurableproduct) anymore.
also, the exception says it cant find the parent, using the parent
slug. which is wrong.
i manually did that in shell, and it works fine.
so, the exception is also not propagating properly ?
--
You received this message because you are subscribed to the Google Groups "Satchmo
users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/satchmo-users?hl=en.
