Version: 4.2.0.1, by Paul M
Developer Last Online: Nov 2023
Category: Administrative and Maintenance Tools -
Version: 4.2.x
Rating:
Released: 01-01-2010
Last Update: 01-03-2015
Installs: 686
DB Changes Uses Plugins Auto-Templates
Code Changes Translations
No support by the author.
--------------------------------------------------------------------------------
This modification has been withdrawn.
vBulletin 4.0.x and 4.1.x are no longer supported.
For vBulletin 4.2.x please use the built in reverse proxy detection.
--------------------------------------------------------------------------------
This hack makes the forum always use the members real ip if a proxy is detected, meaning that all existing ip functions should continue to work, basically ignoring the proxy server (other than recording it's presence).
For example ;
* The real ip is displayed in the who's online page.
* The real and proxy server ip's are accesible for each post, the button is red for members using a proxy server.
* The real ip is searchable in the admin/mod cp (but not the proxy ip).
* The real ip can be banned by admins.
Note: This hack relies on the proxy server passing the correct http variables to allow detection.
If they are not passed then detection will not work. By definition, annonymous proxies do not pass on these variables.
If a proxy is detected, then a red ip icon is displayed instead of the standard one.
To install, download and unzip the files and follow the instructions in the text file.
This modification involves changes to the class_core.php file - if you upgrade your vbulletin, you must reapply those changes.
If you forget these edits, the modification will continue to work for forum posts only (v4.0.4 +).
History:
v4.0.1 : 02-Jan-2010 : Initial release for vb 4.0.0 Gold. v4.0.2 : 04-Jan-2010 : Added check for invalid alt ip address. v4.0.3 : 13-Jan-2010 : Minor change to cope better when people forget the class_core file edits. v4.0.4 : 15-Jan-2010 : Further changes to process forum posts when people forget the class_core file edits. v4.0.5 : 20-Feb-2010 : Internal update, not released. v4.0.6 : 27-Feb-2010 : Style code updates for vB 4.0.2. v4.0.7 : 30-Oct-2010 : Style code updated to work when css stored as files.
v4.1.0 : 04-Dec-2010 : Updated for vBulletin 4.1.x
v4.1.7.0 : 16-Oct-2011 : Updated for vBulletin 4.1.7. v4.1.8.0 : 18-Nov-2011 : Updated for vBulletin 4.1.8.
v4.2.0.0 : 24-May-2012 : Updated for vBulletin 4.2.0. v4.2.0.1 : 02-Jan-2015 : Updated for Cloudflare Changes.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
/** * Fetches the IP address of the current visitor * * @return string */ function fetch_ip() { return $_SERVER['REMOTE_ADDR']; }
/** * Fetches an alternate IP address of the current visitor, attempting to detect proxies etc. * * @return string */ function fetch_alt_ip() { $alt_ip = $_SERVER['REMOTE_ADDR'];
if (isset($_SERVER['HTTP_X_FORWARDED_FOR'])) { $altip = $_SERVER['HTTP_X_FORWARDED_FOR']; } else if (isset($_SERVER['HTTP_CLIENT_IP'])) { $altip = $_SERVER['HTTP_CLIENT_IP']; } else if (isset($_SERVER['HTTP_FROM'])) { $altip = $_SERVER['HTTP_FROM']; } else { $altip = false; }
if ($altip AND $this->filter_ip($altip)) { $alt_ip = $altip; }
Question, I am upgrading my 3.8 forum to 4.2. the forum has quite a few posts (15mil) and modifying the post table on the uninstall of the old mod and then the install of the new version is quite a headache and server intensive.
I was looking at the code and it appears to me the only difference is that the old proxyip field was varchar(20) whereas the new one calls for varchar(15). I'm guessing modifying the product code to not drop this column wouldn't cause a problem right? Those extra 5 characters shouldn't be an issue in my opinion but my database skills are not super high.
So basically before uninstalling the old mod change the code to not drop the column and then modify the new plugin xml to not add the column. Note, I'm not asking for instruction of how to do that I can handle that part, just curious if you think this will break anything or cause problems.
However - if you just install the new one, without uninstalling the old one, the new one will remove the old product without running the uninstall code anyway.
However - if you just install the new one, without uninstalling the old one, the new one will remove the old product without running the uninstall code anyway.
Same effect, less effort.
Yes, you are right. That does sound much easier. Thanks!