Version: 1.0.1, by Boofo
Developer Last Online: Jun 2012
Category: Miscellaneous Hacks -
Version: 3.7.x
Rating:
Released: 01-29-2008
Last Update: 01-29-2008
Installs: 137
Uses Plugins
No support by the author.
Here it is! The [you] hack ported over to vB 3.7 beta 4.
I have ported this over to vBulletin 3.7 beta 4, but it should work on all 3.7 versions. It now works board-wide (posts and thread titles), in the archive, and also in the quick post in the profile. If there are any areas you find that this doesn't work in, let me know and I will add the code for that area.
Thanks goes out to KirbyDE for making the first version for 3.5 possible. Without him, I'd STILL be trying to figure out the best way to do this for vB 3.5. Thanks, buddy!
Description:
This will replace the [you] variable (board-wide) with the viewing user's username.
Installation:
1 product xml
(No file edits)
Upload the product xml and you're all set!
Enjoy!
NOTE: If you do not click install, you do not need support.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
The forumid settings won't work for this hack as users will still be able to enter the code. You would just end up with a lot of posts with the [you] showing it in instead of being parsed. That is why I added the vBulletin setting to change the word you choose to use. Just choose a word that only you and the staff would know. Once the user tries to use it and it doesn't work, that will have the same affect as any forumid settings would. There is no way to stop them from using the code in their posts. Changing the word at the Admin level stops any words from being parsed but what you have chosen. Does that make any sense?
Does this work correctly with the NOPARSE BB-Code?
I read a few pages back about this... Have you fixed the parsing after the AJAX responses (quick-edit & quick-reply)? Moving the plugins to more specific hooks will fix this (i.e. postbit_display_complete for showthread / archive / external / announcements / PMs, visitor_message_display_complete for Visitor Messages, among others). While moving the locations can result in more plugins, the code will only be executed when it is needed rather than on every page.
I have my own mods that had similar issues and were fixed by using a different hook location. Specifically the bug was not parsing after AJAX. I would have listed all the locations you need to include events and such, but I'm sleepy right now.
Your replacement would have to be made on the $var['message'] rather than $output (where $var is the correct name - $post, $message, etc - it would be $eventinfo['event'] for calendars I think)
Well, get some sleep and please PM me when you are rested as I would like to hear more of your ideas for this. It is in a bad need of updating, anyway.
Says last update was 30 Jan. I guess the updated version you talked about last month is still not uploaded, or did the last updated part in this thread not update when you updated it?