The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
LAM - Dispute Resolution Details »» | |||||||||||||||||||||||||||||||||||||||||
This product will allow you to configure a forum so that only a thread creator, their nominated list of disputed members, and moderators are able to reply to the thread. When a dispute thread is created a PM will be sent to all those involved in the dispute.
On my site we have a lot of people selling items, and occasionally something goes wrong during the process. Before we had this product a member would post up about their problem and it became a free-for-all with 'friends' of both sides posting up slating the other side for being wrong and generally turning into a slanging match until the thread eventually got locked. Now, thanks to this product, only those actually involved in the dispute can reply. This has resulted in almost all of our disputes being resolved in a way where both sides are happy. As of version 4.0.8.1 it is now possible to configure this product to run in "Private Dispute" mode. This extends the normal functionality described above to also prevent those not in the dispute from being able to view the contents of the thread. They can still see it exists but any thread preview text, or opening the thread itself, will show a "You are not authorised to participate in this dispute" message. As of version 4.0.8.2 it is now possible to configure this product to run in "Extra Privacy" mode. This extends the "Private Dispute" functionality described above to also prevent those not in the dispute from being able to see the thread exists. With this setting enabled dispute threads will not be shown when browsing a forum if the user is not the thread creator, on the disputed list, or a moderator. As of version 4.1.3.0 it is now possible to make entering the disputed user names optional via the "Optional Disputes" setting. You can also enable the dispute functionality on all forums by enabling the "Globally Enabled" setting. As of version 4.1.4.0 it is now possible for the thread creator, or a moderator, to edit the threads dispute list by performing an advanced edit on any post in the thread which they have permission to edit. Upgrade instructions for this version can be found here. As of version 4.1.4.1 it is now possible to create a dispute against a single user group by enabling the "Enable Usergroups" setting. This will allow anyone in the user group to participate in the dispute, as well as anyone on the normal dispute list. PM notifications won't be sent to the user group. This version also fixes several bugs with the Private Dispute option where searches would still show a dispute thread even if the user wasn't allowed to participate in the dispute. Tapatalk Users - Please see this important note about Tapatalk support. Installation
Configuration You need configure which forums you want this product to run in, or globally enable it to run in all forums. You can also specify if creating a "dispute" thread in a dispute forum is optional. There is a setting that lets you override who the notification PM is sent from should you prefer it to come from an admin account rather than the user's account. And finally there are the privacy and user group options as detailed above. Example When creating or advanced editing a thread in a disputes forum there is now an additional row where the user can edit the user names (and user group if enabled) of those they are disputing... When the thread is created (or advanced edited) a PM is sent to those involved in the dispute (only newly disputed members are PMd when editing a thread)... When the thread is viewed it shows at the top who the dispute is between... An error will be shown if; the thread creator forgets to enter any names and the "Optional Disputes" option is set to No... the thread creator enters an unrecognised name... or someone not in the disputed list tries to reply to the thread... Version History 4.1.4.1 - Added user group option. Stopped threads showing in searches when Private Disputes is enabled. Stopped sending PMs to users already on the disputes list when editing a thread. (2011/07/19) 4.1.4.0 - Added the disputed users to the advanced edit screen & removed the admin option (2011/07/05) 4.1.3.0 - Added optional disputes, global enable and prevented the admin option appearing in non-disputes forums (2011/05/01) 4.1.2.0 - Fixed an SQL error if the admin option was accessed in a forum that didn't have disputes turned on (2011/03/25) 4.0.8.3 - Added auto-suggest to the user names field (2010/11/01) 4.0.8.2 - Added Extra Privacy mode (2010/10/24) 4.0.8.1 - Added Private Dispute mode (2010/10/23) 4.0.8.0 - Initial release (2010/10/23) Credits Although I've written this product for vB 4 the original idea came from the Private Debates product written by beebi. The code to not send PMd to users already on the disputes list when edited a thread was contributed by CheeSie Download Now
Screenshots
Show Your Support
|
Comments |
#82
|
|||
|
|||
@CheeSie, I have modified the code with some of your suggestions, however, it might be worth me pointing out that with your suggestions came a few problems...
1) Private Disputes were broken if Extra Privacy wasn't enabled by the change to "LAM - No Permission Message (View)". A user was able to enter a thread they were not allowed to participate in instead of being shown the error message. 2) Optional Disputes were broken by the change to "LAM - Hide Thread Completely (Extra Privacy)" because it couldn't cope with threads that had no disputes values set. If you also had Global Disputes enabled you'd be in a right mess as all your threads would disappear from every forum if Extra Privacy was enabled! This is why the ="" and is NULL checks where in the original SQL. 3) Not all dispute users where correctly identified because IN (LAM_DisputeResolution) would only match against the first user in the list. You needed to use FIND_IN_SET instead. |
#83
|
||||
|
||||
The "IN" in the sql was what you were using xD
Either way there was another bug in my code that didn't let disputees reply if the forum permissions was set to cant view/reply to others.. But I guess you can fix that yourself xD |
#84
|
|||
|
|||
Just popping in to say thanks for the continued support of this great plugin I initially installed it about 6+ or so months ago, but disabled it due to some issues (mainly users being able to view dispute posts if they searched all of a disputed users posts), but i'm giving it another go
|
#85
|
|||
|
|||
This still does not work at my end. Regular members can view disputes even though they are not a party to it. Without the privacy issues working, I can not use it and so far no way of resolving disputes except have them take it private.
Quote:
|
#86
|
|||
|
|||
Quote:
|
#87
|
||||
|
||||
Hey mawby,
I love the mod, is there a way to keep users from defining another user and for me to hardcode the usergroup, and remove the option to select a usergroup? -dvsDave |
#88
|
|||
|
|||
Looks like a winner, but I can't get it showing up on my new board. Installed and configured, but not seeing anything different on my threads? (4.1.5.1)
|
#89
|
|||
|
|||
i seem to be having the same problem as dmm2020, members can view the dispute in the new forum posts and new forum threads side bar
|
#90
|
|||
|
|||
Works great on vB 4.1.7 default style. Marked installed and 5 star. Thanks!
|
#91
|
|||
|
|||
Running version 4.1.4.1 ...
Not sure why, but I can't seem to prevent other users (not involved in the dispute) from posting in the disputes forum in the thread created by another member? It's as if the mod is ignoring the option set (see attached) and letting everyone post in the thread using their own usergroup permissions. Am I missing something? Thanks .. Regards, Doug |
Thread Tools | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|