discussion.fedoraproject.org page not fully operational #13126

New issue

Closed

opened 2026-02-08 08:42:42 +00:00 by jandemus · 6 comments

jandemus commented

2026-02-08 08:42:42 +00:00

Description of request

On the discussion.fedoraproject.org page the buttons on top (see attachment) are not working. When you are logged in, this also applies to the buttons for a "New topic" and "Open the latest draft menu" next to it.
This has started more than a day ago. Users say it doesn't work on the Brave, Chrome and Firefox browsers, others are not mentioned yet.
This is discussed in the thread: Problems with discussion fedoraproject.org website in Brave and Firefox
Thanks.

### Description of request On the discussion.fedoraproject.org page the buttons on top (see attachment) are not working. When you are logged in, this also applies to the buttons for a "New topic" and "Open the latest draft menu" next to it. This has started more than a day ago. Users say it doesn't work on the Brave, Chrome and Firefox browsers, others are not mentioned yet. This is discussed in the thread: [Problems with discussion fedoraproject.org website in Brave and Firefox](https://discussion.fedoraproject.org/t/problems-with-discussion-fedoraproject-org-website-in-brave-and-firefox/180746) Thanks.

discussion.fedoraproject.org.1.png

13 KiB

jandemus commented

2026-02-08 08:58:16 +00:00

Author

Some new info to the ticket:
I was able to log-in from Brave, in Firefox I have been logged in all the time, but other buttons don't work yet.

Some new info to the ticket: I was able to log-in from Brave, in Firefox I have been logged in all the time, but other buttons don't work yet.

jflory7 commented

2026-02-08 16:45:48 +00:00

Member

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.

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.

jandemus commented

2026-02-08 17:44:33 +00:00

Author

Thank you, hope you get some good news. As can be seen in the discussion thread there are several people who have the same issue.

py0xc3 commented

2026-02-09 15:45:04 +00:00

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.

We don't host, but we did several customizations that are maintained by us. We cannot say if the issue is caused by something from us or something from upstream Discourse or some interaction between both (there was definitely a software update of Discourse some days ago, as the appearance of the flag tickets has strongly changed). Afaik, the Discourse work on our side was done in the past by @mattdm , though I don't know if that is still applicable.

I'm not sure if another upstream ticket without data from our side is sufficient to clarify the case, but maybe you can trigger something through the contract that allows the Discourse team to access our instance(s) to verify :)

I don't think this is super critical, and I asked users in the Discourse topic to focus for now on identifying and testing mitigations for the meantime rather than filing stuff upstream without expressive data.

> 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. We don't host, but we did several customizations that are maintained by us. We cannot say if the issue is caused by something from us or something from upstream Discourse or some interaction between both (there was definitely a software update of Discourse some days ago, as the appearance of the flag tickets has strongly changed). Afaik, the Discourse work on our side was done in the past by @mattdm , though I don't know if that is still applicable. I'm not sure if another upstream ticket without data from our side is sufficient to clarify the case, but maybe you can trigger something through the contract that allows the Discourse team to access our instance(s) to verify :) Related: - https://discussion.fedoraproject.org/t/problems-with-discussion-fedoraproject-org-website-in-brave-and-firefox/180746/51 - https://meta.discourse.org/t/fedoras-discourse-instance-made-some-troubles-could-the-support-please-give-some-feedback/395546 I don't think this is super critical, and I asked users in the Discourse topic to focus for now on identifying and testing mitigations for the meantime rather than filing stuff upstream without expressive data.

jflory7 commented

2026-02-09 15:58:34 +00:00

Member

I escalated this to our Discourse enterprise support team. Hopefully I can get some feedback on this soon. Thanks for your patience while we figure this one out! 🙏

I escalated this to our Discourse enterprise support team. Hopefully I can get some feedback on this soon. Thanks for your patience while we figure this one out! 🙏 ![A screenshot of a Fedora Discussion forum thread reporting UI breakage on the website, featuring embedded links to user reports describing non-functional buttons across different browsers.](/attachments/7bfdc46b-f53e-4fe8-a605-a3c10a84b55a)

image.png

706 KiB

👍 1