Profile Enhancements - Profile Reporter

Overview:

This product is designed to allow your users to easily report various aspects of the profiles of other users. In the product settings, you can set which aspects of user profiles are shown on the report form (you can select from a list of pre-defined reasons and then add your own custom reasons), define a list of usernames which are not allowed to report profiles, prevent entire usergroups from reporting profiles and set the destination forum for the generated reports (the default is the same destination forum for reported posts). This product is compatible with my "Report Thread Prefix Management" product as well.

Upon installation a column is added to your "user" table that stores the threadid of the report thread so that all reporting of a particular user's profile will all go to the same thread. After activating and configuring the product, users will see a new link on the profile pages of users (and the report icon) which they can use to report that profile.



If a user has previously reported a certain user's profile, then the icon button changes to red and there is a tooltip advising the user they have already reported that user's profile, and in case that is missed, an alert is shown if the "Report "Profile" link is click advising the user and giving them the opportunity to cancel the operation.



By default, a user may report the profile of another user from their profile page, however there is a product setting which allows you to give your users the ability to report profile from thread postbits.



When filling out the form, if a user clicks "Submit Report" without checking any of the checkboxes, then they will be alerted that a reason must be given for reporting the profile. If the user checks the "Other" checkbox, but does not enter any text into the text box meant for giving the reason (or any other additional comments), then they are alerted that a reason must be given when selecting the "Other" option.



Then, when the form is submitted, a redirect message thanks the user for reporting the profile and advises them that the staff will deal with the issue as soon as possible. They are then returned to the profile they reported.

The details of the report are then posted to a thread in the forum you have set as the destination forum for the reports.



All users who can view the destination forum for the generated reports will also see an icon to the right of the "Report Profile" link for profiles that have previously been reported that links to the report thread, and if you are using my "Report Thread Prefix Management" product, the status of the report is included in the tooltip for that icon.



Note: If you choose a destination forum other than the default for reported posts, and you are using my "Report Thread Prefix Management" product, then you will need to use the "Forum Manager" to allow the prefix set defined by that product to be used there.

Updates:

Version 1.1

• Additional CSS added for sites with dark styles.

A special word of thanks goes to Dave who noticed an SQL injection vulnerability and discretely called this to my attention, and offered advice on how to eliminate it.

Version 1.2

• Data used in db queries is sanitized to prevent SQL injection.

Version 1.3

• Removed unnecessary db query since needed data was already present.

Version 1.4

• Added the option to exclude usergroups from having their profiles reported.

Version 1.4.5

• Added the option to set a minimum post count before users may report profiles.

Version 1.4.6

• Fixed minor error for online location reporting.

Version 1.5

• Removed some CSS for colors so the StyleVars can take effect.

Version 1.6

• Fixed bug where null thread was created when a report is posted to an existing thread.

Version 2.0

• Fully phrased.
• Added option to allow users to report profiles from within the postbits.
• Link on profile done via custom template hook rather than javascript.
• Borders on form styled with form border stylevar.
• Settings check more efficient.

Note: Unlike in previous versions, where you selected the pre-defined reasons your users can choose from on the report form (and could add additional reasons), in version 2.0 you simply edit the product's phrase which contains a comma-delimited list of reasons. This allows you to completely customize as well as translate your reasons list.

Version 2.1:

• Phrased all text in generated report.
• Fixed issue where checked reasons weren't shown in the report.
• Fixed issue with postbit icon not displaying.

Version 2.2:

• Phrased page title.
• Added setting choice of icon location.

Note: A special thanks goes to Stratis for reporting these issues. :up:

Compatibility:

Tested and working on VB 4.2.x and should work on all 4.x versions of vBulletin.

Backup/Warning:

This product alters your database, however it is always good practice to keep regular backups and you should backup before installing ANY new product.

To Install:

1. Download and extract the attached .zip file.
2. Upload the files from the "upload" folder to your root folder on your server.
3. Follow AdminCP -> Plugins & Products -> Manage Products -> Add/Import Product.
4. Click on "Choose File" and browse to the product .xml file that was packaged in the .zip file.
5. Click "Import."
6. You MUST enable the product in the settings before it will function.
7. Configure the remaining settings to your liking. Each setting has a detailed explanation of its use.

Support for this product can be found here:

• MHB - Profile Reporter
• TAZ - Profile Reporter

[ocidas]

Very good Mod, Ty!

[MarkFL]

Originally Posted by ocidas

Very good Mod, Ty!

I found a small bug (wouldn't you know it?) and so I apologize, but please download it again. All you need to do is replace the .php files in your root directory.

[z3r0]

Thanks, I've wanted this functionality for so long.

[My Hattiesburg]

There you go picking on Cletus.

[MarkFL]

Update: version 1.1

• Additional CSS added for sites with dark styles.

[mapleleaffans]

Another great mod! Thank you Mark!

[MarkFL]

A special word of thanks goes to Dave who noticed an SQL injection vulnerability and discretely called this to my attention, and offered advice on how to eliminate it.

Update: version 1.2

• Data used in db queries is sanitized to prevent SQL injection.

[mapleleaffans]

Thank you for the update, Mark!

[zorcocuq]

Thanks for sharing.