Edgewall Software

Opened 19 years ago

Last modified 9 years ago

#1245 new enhancement

Highlight changes of a wiki page since last visit

Reported by: kilian.cavalotti@… Owned by:
Priority: lowest Milestone: next-major-releases
Component: wiki system Version: 0.8
Severity: normal Keywords:
Cc: kilian.cavalotti@… Branch:
Release Notes:
API Changes:
Internal Changes:


  1. It would be very handy to be able to choose the versions we want to see the diff between. A la moinmoinwiki, see here for an example.
  2. It would be nice to display the changes of a page since last visit
  3. It would be nice to have a diff mode where only changes are displayed (not the whole page source), with perhaps a preview of the rendered page below the diff.

Just ideas. :)

Attachments (0)

Change History (9)

comment:1 by Jochem, 19 years ago

I can agree for the 'mark changes since last update'. I use the CSS Timeline of Trac to keep trac and sometimes pages are changed and I cant see too good, what is changed. I would go for a in text marking of changes since last visit. Or something like a vertical line in front of the text if that is possible in CSS (left-border solid 1 px).

comment:2 by Christopher Lenz, 19 years ago

Component: generalwiki
Priority: normallow
Summary: Diff display enhancementHighlight changes of a wiki page since last visit
  1. has been implemented in [1973].
  2. would be nice indeed
  3. is how wiki diffs work in trunk (0.9-pre)

Adjusting summary to reflect that only 2. is still open.

comment:3 by sid, 17 years ago

#1772 has been marked as duplicate of this ticket.

comment:4 by Christian Boos, 17 years ago

Milestone: 2.0

(Feature request for point 2. accepted, but no idea when it could be done…)

comment:5 by Carsten Klein <carsten.klein@…>, 14 years ago

Side Note: Tracking last visit status of an authenticated user or an anonymous user on a per resource basis will boost storage requirements for high traffic sites a lot.

Apart from that, a cookie must be implemented stating when the (anonymous) user last visited the site, if not already done. Based on that cookie, one could track the visits to each page and keep a timestamp with each visit, which will be updated as soon as the user once again visits the page.

I'd like to propose an extra table for tracking individual page/resource visits on a per realm basis, so that we could also implement such a "difference" view for for example the ticket system, the roadmap, the timeline itself and so on.

Implementation should go into the main request handler, as this would be a feature common to all subsystems.

In the configuration I would like to have an option for either enabling or disabling individual realms from being tracked, or even individual resources (considering high volume access to individual resources) or collections thereof being matched by for example a regular expression or wildcard.



or something like that

comment:6 by Christian Boos, 14 years ago

Milestone: 2.0unscheduled

Milestone 2.0 deleted

comment:7 by Christian Boos, 14 years ago

Milestone: triagingnext-major-0.1X
Priority: lowlowest

comment:8 by Christian Boos, 10 years ago

Owner: changed from Jonas Borgström to Christian Boos
Status: newassigned

The hardest part would be of course to render the differences in the rendered wiki content, in a way that makes sense.

comment:9 by Ryan J Ollos, 9 years ago

Owner: Christian Boos removed
Status: assignednew

Modify Ticket

Change Properties
Set your email in Preferences
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.