Fenix Complete Reference (Dennis's Worklog)
The complete reference for Fenix support 
Data Model - Update
Purging the system will prevent vandalists to sabotage the system. There are two ways.
1)
To keep the speed of updating the content, every user is able to change items. These items are shown on the pages.
However, every item is stored in an extra table called "Approved_Items". A special authenticated user is able to commit changes to cerain items to this table; or rollback. Rolling back will get the original data out of the Approved_Items table (if no old data is present the item gets deleted(!)).
2)
The same system but instead of showing all Items, show only Approved Items. (slower to update since everything must be checked before showing, but you're absolutely 100% sure everything is approved).
---
which to choose now? hm...
1)
To keep the speed of updating the content, every user is able to change items. These items are shown on the pages.
However, every item is stored in an extra table called "Approved_Items". A special authenticated user is able to commit changes to cerain items to this table; or rollback. Rolling back will get the original data out of the Approved_Items table (if no old data is present the item gets deleted(!)).
2)
The same system but instead of showing all Items, show only Approved Items. (slower to update since everything must be checked before showing, but you're absolutely 100% sure everything is approved).
---
which to choose now? hm...
(Posted on September, 30th 2006, 16:36)
Comments
Sandman said:
If malicious items can be removed and the good items put back at any time: 1.
(Posted on September, 30th 2006, 16:50)
yonni said:
1, but it might be an idea to have a small but noticable message saying that an item is not authenicated yet if it has not been.
(Posted on September, 30th 2006, 23:49)