Product versioning history log ?

[p4guru]

Similar to vB's template history and post revision history logs. As I plan to have staff managing and updating the reviewpost database, it would be nice to have a product versioning history log which writes to a table other than rp_products i.e. history logs in rp_products_revisions. So if a staff member accidentally foobars and messes up the product's original data, it can be easily reverted from version history log.

Admin end to have ability to prune history log with following criteria
- prune by date i.e. last 24hrs, older than 7, 14, 30, 60, 90 days etc
- prune by category id(s) and/or product id(s)
- prune by username (uploader)

Yay or Nay ?

[Chuck S]

Well the only huge problem there is images. I mean cloning the products table so you can restore lost products is not a bad idea however thats easy on a forum it does not take much. I doubt the vast majority of our customers would want if we are to do something like that correctly that they would not want to have there diskspace doubled immediately by using such a feature since we have to clone the images as well.