Opened 16 years ago
Last modified 10 years ago
#7747 new enhancement
timeline rss-feeds should be able to show diffs of wiki changes
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | next-major-releases |
Component: | timeline | Version: | 0.10.4 |
Severity: | normal | Keywords: | timeline rss wiki diff |
Cc: | leho@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I use rss-feeds to get the latest news about wiki (and other) changes of my project via Thunderbird. Viewing the rss message of a wiki change I only see the whole actual state of that wiki page, which may be even overturned. I’d prefer to see the diffs made on that wiki page directly without having to click through to it (and that even on an other program (Firefox)). Therefore I suggest to add a rss_wiki_show_diff (or so) option to the [timeline] section of the trac.ini; or to change that behavior at the whole. The page the feed shall link to shall be http://wiki.neo-layout.org/wiki/“wiki_page”?action=diff&version=“new_version” (be careful! new_version doesn’t need to mean the up-to-date version, but the one meant by this special change.)
Attachments (0)
Change History (6)
comment:1 by , 16 years ago
Milestone: | → 0.13 |
---|---|
Owner: | set to |
comment:4 by , 16 years ago
I'd second this request. But for versions 0.11.x. It would be vry handy to rad wiki diffs via rss!
comment:5 by , 16 years ago
Version: | 0.10.4 → 0.11 |
---|
As I just have read, there will be no more 0.10.x release, So I set Version to 0.11.
comment:6 by , 16 years ago
Version: | 0.11 → 0.10.4 |
---|
Version is used to specify in which version bug (or a missing feature) was first found, so no need to change it in this case. See NewTicketGuidelines.
comment:8 by , 12 years ago
Cc: | added |
---|
th:AnnouncerPlugin has wiki diff implemented for e-mail notifications (linked a tagged release for stable URL). Perhaps the code fragment could be borrowed for patching timeline.
Yes, I would like to have this functionality as well. I'm not sure if this should be made a site-wide option or per-user, though.