When I hit the “New topic” button it does not immediately bring up the new topic form. Instead, the form is displayed after I select one of the threads in the forum. It still appears that it is creating a new topic, but in the background. Once you open any existing topic, the new topic you were trying to create appears (completely correct; i.e. for the forum you intended to post in, even if the topic you entered is in a different forum). This is only happening on one site (https://discussions.scouting.org/), so I presume it’s something they have configured incorrectly. I’ve brought this issue up there, to no avail.

The admins have added a CSS customization that looks like this: body:not([class*="category-council-"]):not(.staff).closed-topic .reply, body:not([class*="category-council-"]):not(.staff).closed-topic #topic-footer-buttons .create, body:not([class*="category-council-"]):not(.staff).closed-topic .timeline-container .create, body:not([class*="category-council-"]):not(.staff).closed-topic #reply-control { display: none !important; } This appears to be ok at initial glance, but then I can see body.closed-topic is applied to the topic list… which really doesn’t make sense. This class isn’t in Discourse by default, so tracking down another customization that adds that… const container = Discourse.__container__; const controller = container.lookup("controller:topic"); const currentUser = api.getCurrentUser(); api.onPageChange(() => { if (!currentUser || currentUser.admin || currentUser.moderator || currentUser.trust_level != 4 ) { return; } else { let model = controller.get("model"); document.querySelector("body").classList.add("closed-topic"); if (model) { if (!model.closed) { document.querySelector("body").classList.remove("closed-topic"); } } } }); So here, if you’re logged in, not an admin, not a moderator, and are trust level 4… then it adds the closed-topic class to the page body. This class is only removed if model.closed is false, which means… if it’s not a closed topic (or even if it’s not a topic at all) the closed-topic class will be applied. This line: document.querySelector("body").classList.add("closed-topic"); should probably be within if (model) because otherwise it’s applied even when there’s no model present (e.g., when you’re not within a topic)… It seems the intention was to prevent trust level 4 users from replying to closed topics, but it’s applied too broadly.

This is not reproducible in safe mode. There is a custom theme / css that is causing this issue.

[image] Kris: It seems the intention was to prevent trust level 4 users from replying to closed topics, but it’s applied too broadly. Heheh I wonder if I’m the reason for that change. I discovered that bug and exploited it liberally. I never grasped the reason to require people to start a new thread when you’ve got additional information to add to an old one.

“New topic” button working incorrectly

Product Support

Calion (Jim Syler) July 4, 2023, 7:03pm 8

Thanks much, this is what I was looking for.

Topic		Replies	Views
New topic button not showing, latest version Product Support	6	717	March 5, 2024
New user can't find the Create Topic button? UX	4	862	May 12, 2020
Cannot create new topics (already disabled plugins) Bug	2	1925	December 10, 2016
Bug? Users don't see "Create Topic" button Product Support	2	393	June 30, 2022
New user replying after topic is closed Bug	4	194	February 9, 2025

“New topic” button working incorrectly

Related topics