If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Hey all - I messed up the themes. You may have to reselect your theme in the lower left hand corner of the main page.

Ah, it's a bug between vBulletin 4 and Chrome. Unlikely to be fixed on HI's end unless Rajah/MTR undertake the likely very involved process of upgrading to vBulletin 5. I put a bug in with Chrome, but no idea if they'll fix it. The bugfix they did that I think broke it appears to have taken a few years to address.

A workaround other than "Go Advanced" appears to be to switch the editor to Source mode (far left button on the toolbar that looks like "A/A") and back again or just using Firefox or IE/Edge.

Interesting. That's what I thought. I've migrated over long ago and just became used to it.

Originally Posted by Hamsterkill

Ah, it's a bug between vBulletin 4 and Chrome. Unlikely to be fixed on HI's end unless Rajah/MTR undertake the likely very involved process of upgrading to vBulletin 5. I put a bug in with Chrome, but no idea if they'll fix it. The bugfix they did that I think broke it appears to have taken a few years to address.

A workaround other than "Go Advanced" appears to be to switch the editor to Source mode (far left button on the toolbar that looks like "A/A") and back again or just using Firefox or IE/Edge.

The A/A fix is the easiest for me. How do you report bugs in Chrome or even feature suggestions? I've submitted one a while back and noticed they implemented it so that's nice, but it was a couple years as well...

Amazon took a major dump for a good part of the day which affected a bunch of sites. I didn't think to check if HI was affected by it (was putting out fires at work) but I know that Jeff moved us to AWS a few months ago.

Hey guys, so I'll have to look into that Chrome issue, but if it's a bug with Chrome/vB that will only resolved with an upgrade to vB 5, I can't comment on that on right now.

The other issue on the 28th was likely for Firefox users only. Because Jeff put us on https://, I had to make a change to the Apache server on the new host to be able to render correctly in Firefox. It should have been resolved from the 28th onwards though...

Also, we are no longer on AWS...because the server was under Jeff's AWS account, I had to urgently move all my content over to a new host ASAP before potential issues happened with with his account, I'm not sure who owns it and how it will be handled moving forward. So now we're on a new host, that would have been the weekend of February 18-19.