Opened 16 years ago
Last modified 5 years ago
#3657 new enhancement
Configure GeneralWikiSubscriber not only to page names, but tags too
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | low | Component: | AnnouncerPlugin |
Severity: | normal | Keywords: | subscriber tags |
Cc: | Robert Corsaro | Trac Release: | 0.10 |
Description
it would be great if GeneralWikiSubscriber could be configured not only to pagenames, but tags.
Attachments (0)
Change History (8)
comment:1 Changed 15 years ago by
Status: | new → assigned |
---|
comment:2 Changed 15 years ago by
Priority: | normal → high |
---|
comment:3 Changed 14 years ago by
Cc: | Steffen Hoffmann added; anonymous removed |
---|---|
Keywords: | subscriber tags added |
Summary: | GeneralWikiSubscriber should be configured not only to pagenames, but tags → Configure GeneralWikiSubscriber not only to page names, but tags too |
comment:4 Changed 14 years ago by
I would just have a comma delimited list of tags in the user's preference page. We could add some ajax to autocomplete for js users. If we want to get really fancy, we could add a subscribe link when the user hovers over the tag. But ultimately, the first step is a comma delimited list, or multi-select on the user preference page.
comment:5 Changed 14 years ago by
Priority: | high → low |
---|
Since tags are not a standard feature of trac (didn't realize this) I'm pushing this down in priority. It can easily be added as a plugin using the announcer API. patch welcome.
comment:6 Changed 12 years ago by
Cc: | Ryan J Ollos Robert Corsaro added; Steffen Hoffmann removed |
---|---|
Owner: | changed from Robert Corsaro to Steffen Hoffmann |
Status: | assigned → new |
As a side-note, I agree now, that creating an independent TaggedResourceSubscriber
should be preferred.
comment:7 Changed 8 years ago by
Owner: | Steffen Hoffmann deleted |
---|
comment:8 Changed 5 years ago by
Cc: | Ryan J Ollos removed |
---|
This would certainly be useful, however the difference between tags and pagenames given has to be recognizable, so we would need
both preferably with keyword-suggest support
I'm undecided, which way to go. At least a) looks more straight forward, while b) would save us from further extending the already long user preferences page with another input.