Catch changes from DiscussionPlugin

[Ingmar Heinrich]

It would be nice if the plugin would not only catch wiki pages but also object from other plugins.

Today I can put the General Announcement

ProductDesign/BrainStorms/*

but it would be cool if this announcement would look like

wiki/ProductDesign/BrainStorms/*

so that I could also put e. g.

discussion/2/*

to catch all posts in forum #2 from DiscussionPlugin. I might be talking crap because I don't know the show behind the curtain, but it's worth while a try :-)

[Robert Corsaro]

This will eventually be reimplemented in core. I will consider the idea.

[anonymous]

i tried to set:

watchable_paths = wiki/*,ticket/*,blog/*,discussion/*

when clicking on "discussino" or "blog" the following occurs (while on the single sub-pages, there is a "watch" button):

 Trac detected an internal error:
   ValueError: need more than 1 value to unpack

egg/announcerplugin/subscribers/watchers.py", line 134, in post_process_request:

Local variables:
content_type  	None
data 	{'dateinfo': <function dateinfo at 0x194c670>, 'blog_month_names': ...
path 	u'blog'
pattern 	u'blog/*'
req 	<Request "GET u'/blog'">
self 	<announcerplugin.subscribers.watchers.WatchSubscriber object at 0x18e8b30>
template 	'fullblog_view.html'

[Grigoriy]

I have the same problem. Do you know any solutions?

[Robert Corsaro]

The problem is that this feature doesn't exist.

[Robert Corsaro]

fullblog notifications plugin is implemented in trunk.

[Robert Corsaro]

This feature is not generic enough to pick up any path. It will need to become more pluggable for this to work. Currently, it listens for wiki and ticket events only, so it will only work with ticket and wiki changes. I tested on trunk and there are no longer any errors with watching other paths (like /blog).

[Steffen Hoffmann]

This is a matter of providing code for additional event producers and subscribers. So far there is explicit demand only for

• discussion (DiscussionPlugin)
• blog (FullBlogPlugin, seems resolved: AnnouncerPlugin/PluginSupport/FullBlogPlugin, but see #9110)

I suggest to provide patches, or better: bundle the support with each of these plugins. Thoughts?

[Ryan J Ollos]

Replying to hasienda:

I suggest to provide patches, or better: bundle the support with each of these plugins. Thoughts?

I think it makes sense to bundle the support with the individual plugins. We can do this for DiscussionPlugin since it is currently unmaintained, and Blackhex has offered it up for adoption. I've even pushed some patches recently for that plugin. For FullBlogPlugin, whether or not to include it in opt comes down to the preference of osimons.

[Steffen Hoffmann]

Replying to rjollos:

Replying to hasienda:

I suggest to provide patches, or better: bundle the support with each of these plugins. Thoughts?

I think it makes sense to bundle the support with the individual plugins.
...
For FullBlogPlugin, whether or not to include it in opt comes down to the preference of osimons.

His answer has been given in #9110. I'll have to look at it, but I trust osimons, so it seem that the request holds. Changing ticket summary accordingly.

[Ryan J Ollos]

See #12971.