As modules on the whole use their own custom tables that could be quite a tall order I would think?...

Perhaps the better solution would be to adapt the module itself to store historical content (changes and revisions)... which of course my bloat your database if you are not careful. How are your customers screwing up modules?

Thanks Alex. Say there is a complicated text/html, table or multi-page module, etc. that they (or perhaps FCK formatting) horribly messes up. It can take me much time to go in and get it back to how it was before the problem.

Maybe it would have to be functionality sort of like the recycle bin rather than a module - it would save the module as it was at say 2am for the last  X 24 hour periods that you could choose.  Could be bloatish as you say. Maybe you could just apply it to a few select module instances where this was more likely to happen.

thanks,

Will