MyBB Community Forums

Full Version: Avatar URL Error ? Unsure how to fix.
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello!

I've installed a fresh MyBB, and was attempting to change my default avatar to one I'm using on my other Forum; all my settings appear to be the same, but I could be missing something. Any assistance would be greatly appreciated Smile

Every time I hit save, however, I get the following message:

[Image: 1b1424dddf0420bb87756315b865c4c2.png]

The URL is "https://sig.grumpybumpers.com/host/Indivara.gif" - for those that don't know this site, it creates a 'Rotating' avatar, so if you go to the link directly it'll give you alternate imgur images.

However, if you refresh this thread, you'll see the image below change:

[Image: Indivara.gif]
The URL you entered is not a valid picture file, but a backend redirection, a script.
Furthermore you're calling a GIF file and receiving another PNG.

You need to put a full quilified URL to a picture file!
There is no way to use this rotating script as avatar - maybe with some hard-code modifications in source code!?

[ExiTuS]

EDIT:
What happens when you don't use the form to set an avatar but insert the URL direct to the database instead:
DB: mybb_users.avatar = "URL"
I did not check the source code for avatars yet, but that's worth a try.

[ExiTuS]
If you're using curl with PHP, here's the investigation:

The request upon https://sig.grumpybumpers.com/host/Indivara.gif by MyBB is as follows:
GET https://sig.grumpybumpers.com/host/Indivara.gif
---> HTTP 302 with "Location: https://imgur.com/XXXXXXX"
GET https://imgur.com/XXXXXXX
---> HTTP 301 with "location: https://i.imgur.com/XXXXXXX"

MyBB fetching a remote file, if using curl, will only redirect HTTP 301/302 request by recognizing exactly Location: in a header.

I don't know if there's a standard on using a Location: or a location: or other forms. RFC 7230 says it's case-insensitive, but RFC 7231 uses Location:.

Seems MyBB's a little bit strict on that. I think you may want to create an issue to address this problem in GitHub: https://github.com/mybb/mybb/issues/new .
Thank you for the replies, but... that doesn't make any sense?

As I said, my website in my signature uses the exact same URL to create the rotating signature, and I - as well as multiple users across multiple accounts - use them for our characters. Eg, if you view this thread: Link, you will find that the majority of the Avatars will change upon reload, and they are all using grumpybumpers URLs to do so.

This is why I am confused? I cannot figure out what setting is different, that allows it to work on my main site, but not the one I'm building now.
(2019-08-28, 06:50 AM)ThistleProse Wrote: [ -> ]Thank you for the replies, but... that doesn't make any sense?

As I said, my website in my signature uses the exact same URL to create the rotating signature, and I - as well as multiple users across multiple accounts - use them for our characters. Eg, if you view this thread: Link, you will find that the majority of the Avatars will change upon reload, and they are all using grumpybumpers URLs to do so.

This is why I am confused? I cannot figure out what setting is different, that allows it to work on my main site, but not the one I'm building now.
Seems they're using a different way or a plugin to operate with user's avatars, if they haven't touched original MyBB files. Not sure.

For now, you'd like to change a core MyBB file ./inc/function.php:
  • Search for this line preg_match('/Location:(.*?)(?:\n|$)/', $header, $matches); (should be in fetch_remote_file() function).
  • Change this line into preg_match('/Location:(.*?)(?:\n|$)/i', $header, $matches); (set the regexp case-insensitive with a modifier i).

I'm not sure if it will leave any security problem, and you also want to post your question in Suggestions and Feedback forum: https://community.mybb.com/forum-199.html
or open an issue in MyBB's GitHub: https://github.com/mybb/mybb/issues/new to address your issue.
Would be fixed in the next 1.8 release.