Version: 2.01, by Paul M
Developer Last Online: Nov 2023
Version: 3.5.x
Rating:
Released: 06-13-2005
Last Update: 09-15-2005
Installs: 458
No support by the author.
This modification is no longer available or supported.
This plugin modifies the reported post system to create a new thread in a pre-selected forum and disables the send of reported post e-mails. This is a port of the version run on our forums, which is based on the original Xenon hack. This is posted with his permission.
Version 2.01 is now released as a product. Download the xml file and then import it into your forum using the product manager.
Everything you need is now imported - there is also no need to edit the plugin anymore - instead you set the id of your reported posts forum in the vBulletin Options > General Settings area.
If you wish to upgrade from version 1 then delete the current plugins and template associated with this hack - then import the product - and set the forum id in the vb options.
History:
v2.01 : First Release.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
I've been using this plugin for a month or so and it remains my, and my moderators, favourite.
I have a subforum in my moderators where all the bad post reports go. The result is mods can comment on the thread and the user and we have a history of any problem posters. It also saves a lot of time.
After a bit of clicking around and trying to figure out why I couldn't get it to work on a 3.5.1. It appears it doesn't go with the Advanced Admin Editing Options installed. That disabled the reporting works fine.
Making a wild guess I think it's this hack not using the 'editlevel' field from posts? Then again I've only started with 3.5.x so don't hit me if that's bs
Well if the advanced editing hack alters vbulletin such that it requires its custom field 'editlevel' to be set then yes - it will fail - since obviously this hack will not set that field.
Hmm, looks like the currently released version has no phrases. I didn't realise I'd never updated this - the current version (that runs on our site) was phrased a while ago. I'll have to update it to the latest version sometime.
If a Forum Title has an ampersand (&) in it's name, it's stored in the db using it's unicode ( & ). When I use the following code to put the Forum title in the reported thread, any forums with '&' in the title are showing up as '&'. For instance, We have a 'Media & Popular Culture' forum which is displaying as 'Media & Popular Culture' in the thread title using this code.
PHP Code:
'title' => 'Reported post in : ' . $foruminfo['title'] .' : ' . $threadinfo['title']
I also tried $foruminfo['title_clean'] but I am still encountering the same problem. Any way to fix this?
Other than that - sorry, but no, I cannot fix it. This hack has never included the forum title in the thread text, that must be something you have changed locally. While you are free to change things to suit yourself, I'm afraid I cannot support any such changes.
I didn't ask for it to be supported or even fixed, I was just looking for clues (from anybody) as to why it wouldn't process the unicode.
Unfortunately, with over 20 forums and over 40 mods differentiated by forum, needing to know which forum the reported post is from is vital to using this hack.