Signature Image Size Limiter

[high]Installation Instructions[/high]

Step 1: Upload the .xml file to the Product Manager
Step 2: Alter the plugin code variables to reflect your signature image limits in height and width
Step 2: Click [high]INSTALL[/high]

[high]Credits[/high]
Zero Tolerance - For helping with the regex and troubleshooting my annoying problems

[high]Updates[/high]
1.0.1 - Nothing major, just removed some code that is not needed

To remove this without re-uploading the plugin, find in your plugin code:

PHP Code:

print_r($imginfo); 


and remove it - I put this in there for testing purposes and forgot to remove it

1.0.2 - This is just a bug fix update

Find in the plugin code:

PHP Code:

$this->registry->options['allowdynimg'] 


replace with:

PHP Code:

$vbulletin->options['allowdynimg'] 


As always, no need to upload the new plugin if you apply the fix directly to your plugin code

Chris

[FleaBag]

Thanks Satan, always needed one of these!

[Aerith_Freak]

Originally Posted by hellsatan

Whichever way you do it, it will cause longer loading times - Of course, like with the signature image checker here, nothing is stopping the user using a smaller image to bypass the check, then renaming a larger image to the same filename and extension as the one they used to bypass the check...

The only way to ensure it is to either have them upload them as attachments, or check it on every page-load :ermm:

Satan

Well if it is done during the posting process, say when the new post information is added to the database, if it checks it then - placing [url]path[*/url] if the image is too large and [img]path[*/img] if it is within the limits - even if they changed the file on the remote server, the post would still have the url tags in it. Then you could just repeat the same process for edit post should they try and get past it that way.

:ermm:

[Brinnie]

Originally Posted by hellsatan

Um? Pardon?

Satan

Yet, once again, I was responding to the wrong thread.

Anyways, thanks for the update. I'm sure the whole world could use this.

[Brinnie]

Originally Posted by Aerith_Freak

Yeah I figured it might do that. I guess another soloution would to be when the message is posted it checks the image, and either places it in the img tag or if it is too big it places it in url tags, but I guess that would, in the long run on big forums cause massive load?

Now here's the real sollutions... To everything:

• 1. You configure it to only allow images from a specific directory on your server, like:
  • A) Your vBadvanced gallery.
  • B) Or someone makes the long anticipated user upload signature pic hack.
  • C) FTP

I don't know how reasonable this is, but one way or another, the idea is to stop the user from updating his signature on the server end. Am I right? Because after his sig is set, he can go to photobucket and replace his mymugshot.jpg with a bigger mymugshot.jpg

• 2. Limit the # of images.
  • (1) is safe number. Anything else and you're asking for it.

that is all.

[dbembibre]

Installed work ok, only one thing, i find the phrases group in "frontend error messages"

[Snake]

Great hack! Installs.

[Chris M]

Originally Posted by dbembibre

Installed work ok, only one thing, i find the phrases group in "frontend error messages"

If you have upgraded from vB 3.0.x it appears that the Name of the Error Messages is not reset from "Front-end Error Messages" that was used in vB3.0.x to "Error Messages" that is used in 3.5

They are both the same thing though

Satan

[Oblivion Knight]

Much love to KirbyDE for helping me out with my request..

This is the resulting plugin:

if ($vbulletin->options['allowsignatures'])
{
	$maxsigwidth = 400;
	$maxsigheight = 150;

	function check_sig_size($sig)
	{
		global $maxsigwidth, $maxsigheight, $errors, $vbulletin;
		$sig = str_replace(array('  ', '\\"'), array('', '"'), $sig);

		// check valid signature image size
		if ($imginfo = getimagesize($sig))
		{
			if ($imginfo[0] > $maxsigwidth or $imginfo[1] > $maxsigheight)
			{
				$vbulletin->GPC['preview'] = 'true';
				$errors[] = fetch_error('signaturetoobig', $maxsigwidth, $maxsigheight);
			}
		}
	}

	$url = preg_replace('#\[img\]\s*(https?://([^<>*"' . iif(!$vbulletin->options['allowdynimg'], '?&') . ']+|[a-z0-9/\\._\- !]+))\[/img\]#iUe', "check_sig_size('\\1')", $signature);
}

The phrase then becomes something similar to:

Your signature can not have images larger than {1}w x {2}h in pixels.

[Boofo]

Originally Posted by Oblivion Knight

Much love to KirbyDE for helping me out with my request..

This is the resulting plugin:

if ($vbulletin->options['allowsignatures'])
{
	$maxsigwidth = 400;
	$maxsigheight = 150;
 
	function check_sig_size($sig)
	{
		global $maxsigwidth, $maxsigheight, $errors, $vbulletin;
		$sig = str_replace(array(' ', '\\"'), array('', '"'), $sig);
 
		// check valid signature image size
		if ($imginfo = getimagesize($sig))
		{
			if ($imginfo[0] > $maxsigwidth or $imginfo[1] > $maxsigheight)
			{
				$vbulletin->GPC['preview'] = 'true';
				$errors[] = fetch_error('signaturetoobig', $maxsigwidth, $maxsigheight);
			}
		}
	}
 
	$url = preg_replace('#\[img\]\s*(https?://([^<>*"' . iif(!$vbulletin->options['allowdynimg'], '?&') . ']+|[a-z0-9/\\._\- !]+))\[/img\]#iUe', "check_sig_size('\\1')", $signature);
}

The phrase then becomes something similar to:

Is that the entire hack in this xml then?

[Oblivion Knight]

Originally Posted by Boofo

Is that the entire hack in this xml then?

Yes, you can install the plugin via hellsatan's .xml file and then replace the code with the above.