Version: 2.2, by Vitaly
Developer Last Online: Jul 2014
Category: Administrative and Maintenance Tools -
Version: 3.8.x
Rating:
Released: 02-06-2009
Last Update: 01-21-2010
Installs: 143
DB Changes Uses Plugins Auto-Templates
Re-useable Code Additional Files
No support by the author.
Features:
Log all PM and Emails, sent via forum forms.
Keep logs in separate table with automatic rotation of old records.
Add new menu items in topics and profiles for fast access.
Have nice dynamic menus in search results for cross-searches
Managed access for administrators (except superadmins)
How to install
Upload files to your server
Import product xml
Go to ACP
Select required settings in ?Vbulletin options → Private Message Log?
Set access ?Can view PM logs? to necessary members in ?Usergroups → Administator Permissions?. Super administrators can be skipped.
Notes:
This mod uses full scan for text searches, that can affect SQL-server load at really big boards. Fulltext indexes are not used intentionally, because whose can't produce sharp results and not compatible with innodb. I suppose, that if you really need this mod, you know exactly, what are you doing and what are you going to search. In my practice, ONLY exact matches were useful.
One of tradeoff to reduce SQL-server load ? make log size shorter (1-2 months instead of 6). When vB 4.0 provides refactored search framework, search method can be rewritten.
If you install this mod on your server, i recommend to clarify forum rules, and add text, that your project doesn't provide the ways of confidential communication ? only public and non public.
PS. This mod is independent. Since could't find one, that satisfy my requirements to functionality and usability, the new one was done from scratch. Code is reuseable. If you can do things better - i'll be glad to install your branch and spend my efforts to another things
2.2
- Redesigned database to improve search/paging in some cases
- Should fix conflicts with other mods, that where reported in this threads
- Sources repo is now @ github
... (not public)
1.9
- Ups... another broken link (from message list to user profiles)
- Fixed access for non superadmins, who had "Read PM Log" privilegies.
1.8
- fixed broken link in ACP popup menu
- workaround to show smiles and bbcodes
Please, read previous posts prior to ask questions.
Being that it was an error on a different line in your code,-then the other persons post- I would think to just ask you instead of jumping to conclusions and messing it up even more then it already is. If someone's error code doesn't match mine exactly- I'm not just gonna go fiddling around- especially when the first result of your mod when no one at all being able to open a thread- me jumping to conclusions (just because) could've killed the whole site- all from one assumption. So being that the errors are different from one another, should I still do what was previously suggested for someone different?
Please, read previous posts prior to ask questions.
Please, actually fix your problems instead of getting pissy with people who shouldn't have to code for you. It's amazing how many "developers" will try to pull this "read previous posts" instead of fixing their own errors
[high]* wolfstream uninstalls product because it doesn't work properly[/high]