Such a phrase is not being used by this Hack.

done now had a duplicate phrase called the same thing

Checking the image size for attachment from the 3.5.2 still doesn't work on the beta site.
see also :
this post and this.


getimagesize() fails for attachments.
It doesn't return anything (or more specific it won't pass the ($imginfo = getimagesize($sig) ) if condition.
It doesn't fail for attachments of the live site though (used on the beta site).
parsing of the URLs is fine, so $sig contains the correct URL for the images/attachments.

Both sites are on the same server, on different subdomains.
Has anyone any clues whether this can be a vbulletin issue (wrong settings somewhere) or a server setup problem?

sounds like you're in my boat, your host turns off the allow_url_fopen function for security reasons and supports cURL instead.

vBulletin has said they plan on integrating cURL in the future and Andreas has said this issue doesn't effect him so he doesn't plan on supporting cURL.

Here's a message about it from my webhost. (dreamhost)

so does this not work with existing sigs, only when modifying?

That's nonsense ;)
Future PHP versions will not support the current behaviour of allow_url_fopen due to its misunderstanding by most webhosts.

well the blog provided some good examples of how its a security risk, add how cURL has some better functions.

here's the last post

Thanks but that is not the problem.

allow_url_fopen is turned on, since it works with checking attachments from a VB 3.0.x install (=the current live site) but not for checking attachments for the 3.5.2 install where the sig image limiter is running on (= the current beta site).
Both installs use the same server on different subdomains.
Unless there is a switch/option somewhere in Apache/PHP/MySql that I missed both sites run on the same configuration.

I'm running 3.5.0 and am having trouble with people who were outside the limits *before* the hack was installed. in which case they aren't able to edit their signatures in such a way to be within the limits. my font limit is 14, they've got 16 in their sig, they aren't allowed to change the font size, instead getting a message 'your font is too large'.

is the hack incompatible with 3.5.0?

bitfield.xml dont' work