Hi Jyve list
After committing the modify_own_* permission feature (also MySQL insert
script stuff is updated now), I am starting my next step:
As I announced earlier I will to add a feature, which allows a
moderation of the entries. Basically, people can add new entries, but a
moderator has to release them first. For this feature I will insert new
permissions as follows:
Existing permissions:
- add_*
- modify_*
- modify_own_*
Planned new permissions:
- add_unreleased_* (meant for user)
- modify_own_unreleased_* (meant for user)
- see_unreleased_* (meant for admin or user)
- release_* (meant for admin)
while '*' is a placeholder for project, faq, topic, question and answer
This requires some changes in the screens:
e.g. a relaese link for admin will be added. Also an email could be
sent to the admin after someone adds a new entry. This email could
contain a URL pointing to the screen, where the change took place.
Furthermore I plan to put the whole security check into a new class.
This to reduce the redundany; updates and bug fixes get easier this way
and the screen and action classes are better readable.
(For the same reason also the database stuff in the screens should be
moved to another class e.g. to RecordExtractor; this makes also sense
to seperate the layout from the db queries.)
Of course, the whole thing will cause more changes than listed here...
This was just to give you a rough idea about my intentions.
Questions? Comments? Feedback? Votes? Objections?
Have fun!
t. Bernie
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
