Hello,
Huge thanks for this plugin, it is in use on our forum and working very well by and large.
Big +1 for the option to have reported chats made available to all moderators rather than just admins as it is presently. As requested above, it would be great to have similar functionality to the core vB 'report post/pm' button whereby when you click on 'Report chat' on a chat in the chatbox, the chat is reported in the same way as for reported posts - ie an email is sent out to all moderators and a 'reported chat' thread created on the forum. Hopefully it's possible to use the same core reporting code in the vb codebase.
One important thing regarding that option though if it is implemented -
can the reported chat please be an exact copy of the original chat that was reported.
As an example if users click on 'report chat' and then the user that wrote the chat edits it or deletes it after it's reported, at the moment the 'report chat' admin control panel (ACP) feature is not much use because it just retrieves the latest version of the chat from the db and displays that in the admin panel on the 'reported chats' ACP page (so by and large it will just appear to be an innocent chat, or worse if the chat was deleted the chat entry will be completely blank in the ACP). In the case that someone reports a chat it would be best to have a verbatim copy of the original chat that was reported otherwise it makes it very easy to avoid your chat being read again as it was originally written (even if users don't know about this exploit/hole, generally if they've written something wrong or bad they will just automatically edit it anyway to protect themselves, making the original chat disappear for all time).
On a similar note, another great addition would be the ability to have a history for each chat - so for example if someone edits or deletes a chat, a copy of the previous chat is stored on the server and is accessible when you click on that chat's history in the archive page drop down list next to the chat (perhaps if the chat was deleted have the chat content ghosted out in the main chat entry in the archive table?). I can appreciate this probably isn't massively required and must admit myself it would only be used occasionally on our chatbox (although we had an incident the other night where someone went into meltdown and said a lot of seriously litigious things but then deleted or edited all their chats before any of the mods could see what was said and we can't really switch editing of chats off for one reason or another! Also because of the 'bug' in the chat report page above, none of the reported chats were visible because the user had deleted all of his chats before a mod could ban him!).
Bug report: Channel names listed incorrectly in archive page navigation drop down lists
In the archive page, if you have more than one additional channel then any non-default channels are displayed with the same channel name as the last channel that was created in the navigation drop down list. For example:
As you can see above, the channels are named:
- General channel archives (the default channel)
- Channel Poker Chat archives
- Channel Poker Chat archives
In fact there is only one General Poker Chat channel - however we do also have a 'Mods Chat' channel as a 3rd channel, but that isn't listed and is instead a duplicate of the Poker Chat listing (just to confirm I do have permissions as the logged in user to view that channel and it's archives).
Selecting either of the Poker Chat options ^ does just list the Poker chat archives (ie it isn't a case of one of the labels just being incorrectly displayed).
The 'Mods Chat' archive IS viewable by manually editing the GET options / URL in the addressbar (ie /mgc_cb_evo.php?do=view_archives&
channel_id=1).
I don't know if it makes a difference but the Poker Chat channel (channelid=1) was created after the Mods Chat channel (channelid=2) and then the order of the channels was changed so Poker is display order 1 and Mods is display order 9. Both channels are restricted to different usergroups.
Looks to me like it might just be a simple looping error in the codebase perhaps?
Anyway, thanks again for a great product, keep up the great work.