Modify ↓
Opened 18 years ago
Closed 18 years ago
#4185 closed defect (fixed)
timeline.rss not updated with r4214 and r4224
| Reported by: | Owned by: | Jonas Borgström | |
|---|---|---|---|
| Priority: | low | Milestone: | 0.11 |
| Component: | timeline | Version: | devel |
| Severity: | minor | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
templates/timeline.rss needs to be updated for the changes made to 4214 and 4224. I'm attaching my try, which appears to work.
Attachments (1)
Change History (6)
by , 18 years ago
| Attachment: | timeline-rss-4214-4224.diff added |
|---|
comment:1 by , 18 years ago
comment:2 by , 18 years ago
| Milestone: | → 0.11 |
|---|
I actually applied the patch in [4334], but agree it would be better to use wiki_to_html to get the full text.
comment:4 by , 18 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Since this has eliminated the use of the use_oneliner and shorten_oneliner options they should be removed from the code as well.
comment:5 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
No, those remains useful for the HTML view. There, the ITimelineEventProvider are in control of what should be shown, and those fields are set according to the various configuration options we already have.
Note:
See TracTickets
for help on using tickets.
Well, the
wiki_to_htmlwas done on purpose for the RSS output. The reasoning was that the RSS Reader would eventually truncate the message when appropriate, but otherwise it would have the full information at its disposal.So do you really think it would be better to make it a one liner?