Hi Jyve users I have just committed an update of Jyve. With this it is possible to let a moderator release new entries, before they are visible for others. (If you don't care about this, just give all your roles the permissions add_* and modify_* (or modify_own_*), so that new entries are released immediately). For updating existing installations, you have to update your table shemes. Use the ALTER TABLE * statements in the tables.schema. Furthermore the permissions should be updated, using the jyve_roles_permissions_auto.sql (this can be costumized by the Perl script; see INSTALL.doc). Futhermore you have to release all existing entries. At the moment the Jyve version doesn't build with the current CVS version of Turbine. I'll have a look at the SessionValidator and the path, that was recently porposed to the list. I hope I will have enough time to fic this issue. For the meantime, I provide you my turbine-2.0.jar and the corresponding TurbineResources.properties on URL http://www.ee.ethz.ch/~faq/ This version was build before the Seesion Validator changes in Turbine. Open issues / To do: -------------------- --- Feel free to work on those --- Currently only the MySQL scripts are updated (NOT oracle). DisplayUnreleased If there is only an unreleased project, faq, topic (but no question), it doesn't appear. Release: - The Classes ReleaseProject, ..., ReleaseAnswer could be implemented somehow smarter. I was thinking using a Hashtable or similar construct. Maybe put this Strings to a seperate class, so that they are re-usable for future classes, which only differ in the tablename (project, faq, ..., answer) - There is no check yet, if someone releases e.g. an answer, but the question (topic, faq or project) is not released. (Currently a way to detect such problems is to run DisplayUnreleased) Look/Feel/Colors: - I am aware of that the Look/Feel/Colors of the Display* and Search* classes could be improuved in general. Especially the marking of the unreleased entries doesn't look satisfactonary to me yet. Release email: - An optional feature, which sends an email to one ore more addresses, if an unreleased entry has been added. This could contain a link to e.g. screen/DisplayUnreleased/action/ShowEdit/showedit/true or directly to the correponding Display* screen (with action ShowEdit) What I changed (copy - paste of CVS commit message) -------------- New: feature for moderation - New permissions: add_unreleased_*, modify_own_unreleased_*, see_unreleased_*, release_* - New classes: - actions/Release, Release*: sets an entry released in the database (if corresponding release_* permission granted) - screens/DisplayUnreleased: Show all UNreleased entries, (depending on permissions) - Unreleased entries are usually displayed with different color. - Release button, if corresponding release_* permission granted. - Updated SQL insert scripts (only for MySQL) - Updated all other affected classes New: Some colors can be customized in TurbineResources.properties. Change: localization string for consistency - DISPLAYPROJECTS_MODIFYPRJ -> DISPLAYPROJECTS_MODIFY Bug fix: SearchResults - Sort out duplicates (Before an entry appeared twice, if e.g. the search string was found in two answers of the same question) I hope that's all you need to know... Feel free to email your comments, questions, complaints, proposuals ! I am really looking forward to your feedback. Have fun! Bernie -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html> Problems?: [EMAIL PROTECTED]
