Tags:
archive_me1Add my vote for this tag create new tag
, view all tags
I think a feature is missing: having TWiki automatically send you an email once when a single topic changes, in the following 2 cases:
  • Somebody re-edits a topic you were the last to edit. This may not be desirable
for all pages, so this may be a box to check when saving.
  • Editing a page failed because it was locked by somebody else: you should receive
an email when the page is ready to be edited. This also could be an option of the oops page presented when trying to edit.

Implementation: This cannot use the WebNotify topic, as it can be locked by a human. It cannot be in a metadata field (it would not work for the second case). The best solution seems to be in a separate Topic.mail page, that can be just appended to, and that will be processed on save.

Comments?

-- ColasNahaboo - 09 Mar 2002

I like both of these suggestions, but, if this gets implemented, it would be nice to also be able to add your name to individual pages to be notified anytime that page changes.

-- RandyKramer - 10 Mar 2002

We don't need an unlock notification if we get rid of RCS locking. (Instead of locking, we could adopt a CVS-style merge strategy. Presenting the conflicts in a way that people with a non-geek background can understand them could be a challenge though.)

-- JoachimDurchholz - 10 Mar 2002

RCS locking isn't really used by TWiki (all files are locked by the same user ...). TWiki uses its own locking mechanism to avoid the merge/contention problem - not a bad solution, but a problem for a distributed system.

-- JohnTalintyre - 10 Mar 2002

Edit | Attach | Watch | Print version | History: r7 < r6 < r5 < r4 < r3 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r7 - 2008-09-02 - TWikiJanitor
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.