Tickets :: Comment on [#7939] Central content reporting system

Search Results: 5 of 9 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

* Your Email Address
* Spam protection	Enter the letters below: . ..__ .__..__ . \|__\|[ __[__]\| \ \| \| \|[_./\| \|\|__/\__\|
Comment	> Currently Ansel, Oscar and Folks has exactly the same code for > reporting malware content to application administrators (members of > app:admin). This code should be moved to an autoload-able Horde > hatchery framework library. So the code is shared and maintained > there. Allowing a nice way to implement new drivers (ex. other ticket > systems, notifications etc). > > > > Currently the implemented drivers are Whups, Mail and Letter. All > allowing attachments, so it should replace even the man Horde problem > reporting screen. > > > > The last updated code is present in Letter. Currently called > Horde_Report, but the name is too vague for a global lib. Maybe can > be added named to fit the new content system currently being > developed for tagging, relationships, trackbacks... > > > > Code > > http://cvs.horde.org/incubator/letter/lib/Report.php > > http://cvs.horde.org/incubator/letter/lib/Report/letter.php > > http://cvs.horde.org/incubator/letter/lib/Report/mail.php > > http://cvs.horde.org/incubator/letter/lib/Report/tickets.php
Attachment
Watch this ticket