I also have the same issue’s running the latest versions of Chrome and Firefox.For me the issue started yesterday.If I keep trying to log in it will work after several times.To add on the top only the Fedora Discussion button works nothing on the right side with Chrome.With Firefox the buttons on the right work just can’t login.
I have filed a ticket, it can be seen at forge.fedoraproject.org/infra/tickets/issues/13126.
Hope somebody will pick it up soon.
3 Likes
Same issue on Zen Browser (which is built on Firefox.) One workaround I’ve found is, if you refresh the page, the buttons work.
Not here. I have extensions in both browsers which refresh the page every so many minutes and it stay the same.
Refreshing does not work for me in Firefox.
Seems it is dependent on more than just refreshind. Tried when I first entered the website, refresh didn’t make a difference. Then revisited this page, icons still weren’t working, then I refreshed page again and the buttons are working now.
Weird issue indeed.
This is the first answer I received on the bugreport written by @jflory7:
This won't be something Fedora Infrastructure will be able to support with, since Fedora Discussion is not run or hosted inside our own infrastructure. This is hosted externally by Discourse.
I'm not able to reproduce on Firefox on my end. On Monday, I can help escalate this issue to the Discourse support team for further debugging.
2 Likes
Had any of you that see this issue tried creating a new profile to see if the problem is then fixed?
Yes, in Vivaldi, and it does persist. If I access forum topics via a link (e.g. from those at Fedora Start) then the login button usually works on that webpage, but not on the main page at https://discussion.fedoraproject.org
Hi,
I experienced yesterday that my notification button is broken (so the button that contains my avatar and shows recent notifications when I click it: button on the top right of the page).
It still shows that there are new notifications if there are some (e.g., orange flag indicating there are flags that need processing), but I cannot click it (no response if I do). I already restarted, etc. But always same outcome. I have disabled all Firefox plugins, reloaded page, and re-tried, same outcome.
I have the default Firefox build of Fedora’s default repo (firefox-147.0.2-1.fc43.src.rpm → x86_64 → up to date as of today).
Can anyone verify with the same Firefox (dnf info --installed firefox ) build if they have the same problem? I just want to verify at first if this is a local or a wider phenomenon. Feedback from people using other browsers is welcome too.
(supplement: I merged this into the existing topic; thanks P G)
1 Like
Yeah, the same for me and for several of us, across different browsers. For me it’s intermittent - it’s not always broken.
1 Like
@kevin It seems this is an issue on Discourse’s side (I see it occurs in Chrome, Brave, Firefox): maybe there was a Discourse update in the recent 2-3 days (?). Do we maybe need to file a bug upstream / report this against our enterprise contract? (I assume only you and @mattdm can do that? I assume a bug report might also need some data from our Discourse instance and its configuration others have no access to.)
Supplement: it’s intermittent on my side too, and I can impact it by setting the Firefox security settings from strict back to standard, reload, then set it back from standard to strict, reload again, and then it still works, at least for some time → so it then remains working with strict even after several reloads and in new tabs)
Is Discourse the same service used by, let’s say, Bazzite? If so, I have checked and Bazzite’s discourse page does not exhibit this erroneous behavior and works correctly.
I had a terrible issue with poping up errors last week on a debian installation. The error was complaining something about the theme in Discourse.
Can someone try to change the theme in the settings (I use the dark one, colors I use the default) and give feedback if this changes something? (On my F42 WS I can not confirm the issues reported here)
Just to inform, even if the discourse instance is hosted by them selves, If we from our side make changes, we do brake it, then we are responsible for that.
Maybe you realized that the format of the text based content </> is smaller now ? It looks better in my opinion but such changes would be nice when they get announced.
If the Infrastructure makes changes, they announce it before doing them.
I’m on ‘light’ theme with the problem active.
try the dark one and let color as default, then change to light and let the default to see if it changes something.
What you also could test is, to remove the cached data for discussion.fp.o. Remember that this mght kills your saved password and you would have to enter it new.
2 Likes
This helped me.
2 Likes
Even if two communities use Discourse, there are many variables that can explain why an issue occurs on one and not the other: we use the Discourse service from the company maintaining Discourse, we don’t host ourselves. Others host themselves. Without further information, the issue can have origins/relations to operating system, OS configuration, but also the configuration of the very discourse instance itself, or related/dependent services (DB or so). A lot is possible, and a lot data might need to be considered within evaluating the issue/origin. That’s why I think the bug should be reported by someone with unrestricted access to our Discourse service, related services and their configurations.
Nope. Did not work.
I removed cookies and site data in Firefox for fedoraproject.org and discussion.
I had to log back in, but the problem there is the log in button didn’t work!
So I opened another link in a new tab, and then the log in button worked there.
1 Like
I am using Chrome atm and still have the same issue.I read this topic and clicked reply and it showed the login which worked.
Just to add I am logged in but still have no access to the top 3 buttons on the right.
Disabled and renabled adblocker now they are working.