Invalid URL error when inserting images.

[mattltm]

Just tried turning off the firewall on the server and it made no difference. Still the same error.

Also ran curl from the shell using "curl -O http://www.m0lmk.co.uk/wp-content/uploads/2015/05/20150501_194338.jpg" and that worked with no issue with the firewall both on and off.

[Wayne Luke]

That dialog is CKeditor so that is Javascript but I don't know if it just passes and array to vBulletin or does more.

Do you have any addons installed that change the handling of posts?

[mattltm]

None. And I've seen the same behaviour on a plain install of 4.2.3 RC1

[Wayne Luke]

Do you have any addons or extensions in your browser to block scripts or ads?

[mattltm]

Nope.

I also get the same error using Chrome, Chrome Incognito, Firefox and IE.

[mattltm]

Any movement on this?

It's very annoying!

[Wayne Luke]

You can try the fix here: http://www.vbulletin.com/forum/forum...on-image-4-1-4

If that doesn't work, you will most likely need to upgrade to vBulletin 4.2.3 and PHP 5.5

[mattltm]

Tried all of the suggested methods in the thread and they make no difference. I don't want to use the legacy "Add image" popup as I want to store the images locally.

If you look back through the thread you will see that I have already tried a fresh, vanilla install of 4.2.3 RC1 with no success.

I'm running PHP V5.4.41 which shouldn't make any difference.

This has obviously been a bug since at least 2011 which make it 4 years with out a resolution!

There must be a fix for this!

[Wayne Luke]

I am sorry. If there is a resolution, I do not know of it. There was a bug with GD in PHP 5.5 but that is fixed in 4.2.3 and you're using 5.4.41. I can't recreate the issues on my servers running PHP 5.5.9 or higher though.

[mattltm]

So yes it's a bug and no there will not be a fix.

Neat.

[Wayne Luke]

vBulletin 4.X is End of Life. The only fixes currently being applied are for security and service (PHP, Facebook, MySQL) compatibility.

[mattltm]

End of life since this bug was discovered at least 4 years ago when it should have been fixed in the first place? I suspect the truth is that no one could be bothered to fix it as everyone was busy trying to get VB5 to a usable state and it was just swept under the carpet in the hope that we would all fall in love with VB5 and move on.

Never mind. I'll just feel my way around for a dirty hack (as the hack listed on JIRA for disabling the checkbox also does not work) and move on to the next unfixable problem.

Thanks for trying Wayne.