Changes between Version 14 and Version 15 of TracUnreadPlugin


Ignore:
Timestamp:
Dec 3, 2015, 3:34:30 PM (8 years ago)
Author:
figaro
Comment:

Further cosmetic changes, removed duplicated screenshots

Legend:

Unmodified
Added
Removed
Modified
  • TracUnreadPlugin

    v14 v15  
    55== Description
    66
    7 This plugin tracks ticket page views and provides "last unread" link __on ticket pages__ (those that end with `/ticket/XYZ`).
    8 Similar to one you've probably seen on most forums.
     7This plugin tracks ticket page views and provides "last unread" link '''on ticket pages''', ie those pages that end with `/ticket/XYZ`. This is similar to a feature you have probably seen on most forums:
    98
    109[[Image(last.png, border=1)]]
    1110
    12 The only difference is that this plugin is better: it does not just uses your last login time, but actually tracks time when you requested each ticket - and that's why a Trac environment upgrade is required.
     11The only difference is that this plugin does not just use your last login time, but actually tracks time when you requested each ticket. This is also the reason that a Trac environment upgrade is required.
    1312
    14 Of course, it does not work for anonymous users.
     13Of course, it does not work for anonymous users:
    1514
    1615[[Image(no_unread_metanav.png, border=1)]]
     
    1817Tested on Trac 0.10 and current trunk of Trac 0.11.
    1918
    20 This plugin can be used in reports and a [source:tracunreadplugin/0.11/trac7_with_unread.sql sample SQL report for PostgreSQL] is included in distribution.
    21 
    22 Screenshot:
     19This plugin can be used in reports and a [source:tracunreadplugin/0.11/trac7_with_unread.sql sample SQL report for PostgreSQL] is included in its distribution:
    2320
    2421[[Image(trac_unread_report.png, border=1)]]
    2522
    26 But there are limitations:
    27 
    28 First of all, you will need PostgreSQL (not tested with MySQL). SQLite lacks string functions required to extract comment number from "parent.reply" pair in the database, which invalidates the use of SQLite for this plugin.
    29 
    30 Then, you must dump all `_description`, `description_` and `_description_` fields from your report (they are hidden in default reports). Reason: we will need this field to provide link to "unread comment". The only way to include another link to report row is generating wiki markup in `description` field. At least, I found no other way (in Trac 0.10.4).
     23Known limitations:
     24 1. This plugin works with PostgreSQL: SQLite lacks string functions required to extract comment number from "parent.reply" pair in the database. Nor has it been tested with MySQL.
     25 2. Also, you must dump all `_description`, `description_` and `_description_` fields from your report (they are hidden in default reports). The reason is that these fields provide the link to "unread comment". The only way to include another link to report row is generating wiki markup in `description` field. This could be improved however, and patches welcome.
    3126
    3227== Bugs/Feature Requests
     
    5247General instructions on installing Trac plugins can be found on the [TracPlugins#InstallingaTracplugin TracPlugins] page.
    5348
    54 == Example
    55 
    56 A couple of screenshots:
    57 
    58 [[Image(last_metanav.png, border=1)]] attachment:last_metanav.png
    59 
    60 [[Image(no_unread_metanav.png, border=1)]] attachment:no_unread_metanav.png
    61 
    6249== Recent Changes
    6350