Bug #1088
[PATCH] Jabber Notification
| Status : | Closed | Start : | ||
| Priority : | Normal | Due date : | ||
| Assigned to : | scott - | % Done : | 0% |
|
| Category : | backend | |||
| Target version : | - | |||
| Resolution : | fixed |
Description
Jabber notification didn't work for me, so I fixed it. Here's the patch. It's against 4.0.3. I had absolutely no luck in getting jabber4r to work, so I used xmpp4r instead. I also added the url to the comment notification, which makes it handy for replying/moderating comments. I don't know if the content_state just presumed ham is the "right" place, but it's working for me.
Associated revisions
Clean up API exception reporting. Closes #1088