add history & rollback capabilities to structures (record dump somehow when struct. changes, or allow saving structure dump for backup...)
This way, when the structure gets mixed by machine or human error, the structure can be rolled back to the previous state.
This way, we could be more open for registered users to manage http://doc.tikiwiki.org/Documentation (or others) without the risk of failure when nodes get moved to the wrong place (due to some bug in the code). Or due to mistake by benevolent newbies mixing things without bad intention.
---
UPDATE: Still desired for some LTS version. {sign user="xavi" datetime="2013-11-17T09:31:50+00:00"}
Tracker view item history (tiki-tracker_view_history.php) doesn't store data from an admin changing the associated username in a tracker item.
e.g.
# a tracker contains some fields. One of them is field type username, with creator as param.
# a registered user adds an item (so that this user has associated it's username to the field in that item)
# an admin user (user with admin perm on that tracker) changes status from open to pending.
# another admin user (with tiki_p_admin) edits that item, to change the field username from a value to another one.
# tiki-tracker_view_history.php does not show that change in the table of values, but just the change from open to pending.
The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.
Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.
This way, when the structure gets mixed by machine or human error, the structure can be rolled back to the previous state.
This way, we could be more open for registered users to manage http://doc.tikiwiki.org/Documentation (or others) without the risk of failure when nodes get moved to the wrong place (due to some bug in the code). Or due to mistake by benevolent newbies mixing things without bad intention.
---
UPDATE: Still desired for some LTS version. {sign user="xavi" datetime="2013-11-17T09:31:50+00:00"}