Hello IFC, as you can see, I’m having an issue with my Discourse activity page, whenever I open it comes up in really strange formatting, has anyone else ever had this issue and how do you fix it? I’m using the webpage on a desktop running in the Microsoft Edge browser, any help would be appreciated.
Have you tried looking at the activity page on a different browser? Different device, such as mobile?
Yea, It works fine on my mobile device and in Google Chrome, the thing is I don’t know how this started, and I would prefer to keep using Microsoft Edge as my go-to browser.
Did you try signing out and back in?
Yep, still the same issue.
I can confirm that I also have the same issue running on Microsoft Edge. The issue isn’t on Google Chrome, but as you prefer to use Microsoft Edge, not much I can suggest.
Since this issue is happening with more than one person, I would recommend making a post on the discourse forum. They are probably better equipped to understand and fix this.
Have you guys tried clearing the browsing cache?
Yep, the issue still persists.
Are you using https://community.infiniteflight.com and not http://community.infiniteflight.com?
Hey!
I’ll check this out. But i need to know what operating system is being used, as well as browser + browser version.
Thanks, I’m using Windows 10 Home version 1803, and my browser is Microsoft Edge 42.17134.1.0
Thanks!
I’ve reported this to Discourse now.
May i suggest using a different browser in the mean time? (or forever, for your own sake…)
That wouldn’t happen to be any sort of beta version right? I know they have a beta for the new chromium one, but I’m not an edge expert…
Chrome is a good option! I’ve been using it for a couple of months now, and have had zero troubles with it. It is just as fast and intuitive as Microsoft Edge. I would definitely give it a try.
I’ve been using Chrome for… probably 15 years now. Lol. (Just realized it was released in 2008, but same same)
@George_Anastasis - nope. I never get that error. Do the usual stuff (cache, restart etc).
@KPIT - nope, not a Chromium related issue. I tried on an older version and still experienced it.
Oops, that reply was meant to be directed to @Aceorbit, but glad to see another dedicated Chrome user.