The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
Private Message Workbench: Read, Search, Delete, Report and more Details »» | |||||||||||||||||||||||||||
Private Message Workbench: Read, Search, Delete, Report and more
Developer Last Online: Dec 2010
PM Workbench v1.00 Beta 5
================================================== ============================ Hack: PM Workbench Version: 1.00 Beta 5 Author: MarcoH64 vB Version: vBulletin 3.5.0. RC2 ================================================== ============================ Important Notice: Depending on the modules installed, a privacy statement might be added to your board. This Privacy Statement can not be removed or hidden by any means. Failure to comply would be against the TOS of this hack, and you would not be allowed to use it. If your board already has a Privacy Notice covering reading Private Messages by Administrators, you can PM me a link to that statement on your board (provide test login if needed) and your email address, and i will mail a Plugin to remove the Privacy link. What is this hack? PM Workbench offers you a variety of tools for working with or extending the standard vBulletin Private Message System. It is a Modular System that will allow you to add those functions that you need for your board. New Modules might be added later. The system is fully phrased and options can be set in vBulletin Options. Permissions to use Modules are given using the includes/config.php for increased security. Currently no file or template edits are needed. More modules might be added later. For some i am waiting for new hooks to be implemented in RC3. Donations are always welcomed to PayPal: marcoh64 AT gmail.com Currently Supported Modules: PM Workbench - Report PM This Module adds a Report PM icon to the postbit when users are reading a PM. The reports and send to the PM Folder of the userid defined to receive them. Administrators who are given access can read the reports, the original PM, and add notes to them. Features: - Access to the PM Reports is controlled in your config.php for added security - Add report button to PM's, no template edit needed. - Usersw can give a reason for the report. - Reported PM's can be seen without modifications to them (PM's are not forwarded, but just added to the inbox of the report userid). - PM's are fully parsed - Notes can be added to reports. PM Workbench - Read/Search Private Messages This Module let administrators who are given permission, search and read PM's Features: - Access to the PM's is controlled in your config.php for added security - PM's can be searched for: - Keyword (title and/or body) - Username (sender/receiver/both, optional exact match) - Send date after - Send date before - With a simple click read the PM and see who still have it in their folders. PM Workbench - Performance Pack Add extra indexes to the pmtext table for faster searching. Known limitations: The 'Report PM' module might not work on some heavily modified Styles. I will be (hopefully) posting another (beta) hack for that tomorrow. Show Your Support
|
Comments |
#22
|
|||
|
|||
Marco did e-mail me the plugin to remove the link when I proved to him that my board already informs members their pms may be read. I just thought everyone should know. I will install the workbench now when I get the opportunity. Thanks Marco.
|
#23
|
|||
|
|||
Your welcome, please click Install once you have it running (that should be in 2 minutes from now )
|
#24
|
|||
|
|||
Quote:
One of the things my users ask for most frequently is more email-like handling of the to and from fields. Particularly in the case of multiple recipients. Ideally, if I send to 5 different people, it's an open conversation with these folks, and in order for them to respond to the group, I have to start the PM with "to: user1, user2, user3, user4, user5" so they might copy that on the response. In a perfect world, if I put 5 people in the to field, then all 5 see the other 4 names as well, and of course myself as the sender. Then they have the option to reply, or reply to all. This would create a need for a bcc field of course, in the event you want some or all not to see who else is being PMed, but that would really only function the standard way vB handles this (hiding everyone else but the sender and recipient), so I assume it wouldn't require any new code. A step up functionally speaking to that would be being able to PM to usergroup (primary or secondary) as well, effectively enabling closed discussion groups between different project teams (I have a community driven site), and the like. Is this practical? Is it a potential feature of your workbench? Or *gulp* are these features available in another hack I've simply managed to overlook? As long as I had it all fresh in my head, wanted to ask here. Mostly because the notion of one complete workbench that overhauls PM functionality seems personally more appealing than several different little ones that might overlap and/or conflict. Another notion I had that sort of speaks to the privacy issue, is affording users the option of encrypting PMs. Giving another layer of privacy and protection would make it a lot easier to have some userbases digest the reality (with this hack) that admins can read their PMs. Obviously that would mean admins having 'content' on their site that they have zero access to, but it could be an optional feature. I suspect I'm way off base talking about these here, as your modification seems to speak more to the administrative side of things than the user experience, but wanted to give it a shot. |
#25
|
|||
|
|||
Thank you for your feedback, all suggestions are welcome and i must say i really like the CC/BCC handling. (Actually vB = BCC, you want to add CC). I will give it some thoughts and if possible i will add it.
Closed discussion groups i am not so sure about yet. Encryption is a different thing. Since 2 (or more) members must be able to encode/decode it, some encryption keys must be exchanged, that could be intercepted by the admin again, and thus given false sense of security. There have been more threads about encrypting/obfuscating private message. |
#26
|
|||
|
|||
Quote:
|
#27
|
|||
|
|||
Quote:
The to/cc/bcc stuff would be a dream come true. More than half the emails I send are to multiple recipients, where the ongoing discussion is something we all want the others in the loop for. Invariably, someone forgets to include everyone else, so the convo fragments, and it gets difficult to keep things linear. Perhaps instead of PMing usergroups, people (admins) could set PM aliases for groups? Something like 'game_preview_team' is defined as 'user1, user2, user34, user765', where any PMs sent to 'game_preview_team' goes to all those people (I run a college athletics site). Although I suppose functionally speaking, that might be no different than mailing usergroups, and might require users to be created for each alias? I have no idea, not a coder at all. The big thing was definitely the cc/bcc stuff, and I'm ecstatic that it's something you might consider. Quote:
|
#28
|
|||
|
|||
Quote:
|
#29
|
|||
|
|||
Report does not work. It gets me a no permission error when I click on the report button on PMs.
|
#30
|
|||
|
|||
Could you provide me with a test account and a link please.
|
#31
|
|||
|
|||
Quote:
|
Thread Tools | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|