MyBB Community Forums

All,
I recently wrapped MyBB into HTTPS on my locally owned site. I updated the board's URL settings in AdminCP, and just about everything seems fine with one exception. Whenever a user goes to their UserCP, edits their profile, and then submits, they get a complaint popping up - only under Firefox - regarding a POSTDATA problem. It asks if they'd like to re-submit, but all presses of "OK" just throw them back to the same error. If they cancel, and go back and reload the UserCP, their changes are there. So, something seems a bit off there. Thoughts? IE 7 doesn't do it.

Thanks!
Ichi

EDIT: Oh yes... I'm running the latest 1.2.13. I have a few mods installed that effect the UserCP, including the Skype plugin and my chat plugin. I'm doubtful that the plugins have anything to do with this however, as everything works fine under IE.

What is the exact error Firefox gives? Are you using Firefox 2 or 3?

Please post a link to your site so I can take a look.

BMR777

BMR,
Thanks for responding! Unfortunately, the site in question is on a sort of intranet, so it's hard to just share with others. However, here's a screencap of the exact error I get.



As stated above, this is a Firefox thing only; and my Firefox version is 2.0.0.14. Interesting, Firefox 3.0 does not have this issue. So, I suppose we can chalk this one up as "odd" and move on. It doesn't appear to be MyBB's problem.

That said, I did discover a "bug" of sorts in the UserCP. It looks like the URL blank auto-prepends 'http://' to your URL. If you already have the 'http://' in your URL, it leaves it alone. However, if you have an 'https://' in there (as I do), you get 'http://https://..." Should I stick this one in the bugs list?

Thanks again for taking the time to look at this.
- Ichi

Hmm, strange. I thought that bug had been fixed; maybe it hasn't shipped yet.

Sounds like you're getting stuck in an infinite loop; but I can't say why.

Either that or something's redirecting you back to the same page. Check the URLs you're accessing. That http://https:// one looks like a bug, but I'm not sure if it has already been reported (from MrDoom's post it seems like it has)

I thought it had but from a search I did, I can't find anything about it here. It may well need reporting.