[eluser]BradEstey[/eluser]
n0xie: We've spent a lot of time researching the alternatives and to remain competitive our best option is to write a system from scratch rather than attempt to tweak a one-size-fits-all system to meet our specific needs.
flaky: I'm not sure if that's the best solution. I don't think I want a paper trail of changes since that's the point of having administrative approval. I'd rather admins be alerted to which changes are awaiting approval, review them, and then push them though. I will probably keep one simple table to track history storing only:
- changed by userid
- approved by userid
- sectionid
- pageid
- date changed
- date approved
I want to avoid the chance that someone will change one entry 10 times and in effect that one entry taking up 10x the amount of space in the DB it needs to. Multiply that by the 2000+ pages we have and it could be a monster.. I don't need a wiki.
I'd rather a change be made, some small history kept, and all the changed data be discarded. That's why I was thinking temporary txt files or maybe temporary tables?
