Is there a way to get the topic ID as a variable within a topic? Use case, we have categories for support and bug tracking tickets. I’d like to set them up with templates like so. This: > Do **not** remove this line: Support request #$(topicid) Looks like this: Do not remove this line: Support request #246 Open to other ways to get the info. Just not sure how to do this.

I don’t understand any of that. I’m not a coder. The code I posted does this: [topic-id] How would I do that with your code?

[Bild] tknospdr: But I want to search. It’s easier. Go to site, then append /t/id to the URL at the top of the window VS go to site and type ID into the search field that’s right in the center of the page. If I’m not wrong, inputting topic:id into the searchbar will show the topic in the results. E.g. searching topic:374168 this brings up posts from this topic only. [Bild] pfaffman: you’d need a plugin and it could add ticket123 to the raw text (I think search looks at raw?). The topic id doesn’t exist before you create the topc, so you can’t insert it when you create it I wonder… would a TC that sends an ajax request to update the topic’s raw suffice?

[Bild] NateDhaliwal: E.g. searching topic:374168 this brings up posts from this topic only. That only works for this topic, try a different random one. Try searching for “one two four two four zero” that’s the tag banners topic ID.

You mean topic:124240? The filler word (‘hello’) was just an example. In the case of Tag Banners, ‘hi’ works. Maybe if you have a common word across support tickets, or just a common word in general, you can try that? Just suggesting a workaround :slight_smile: .

[Bild] tknospdr: Problem is that this code is now outdated and I don’t know how to fix it. Did you try the code in Topic ID as a variable? - #7 by awesomerobot Also, if what you want to do is “search” for a topic id, then you could probably make a component that accepted a topic ID and then just jumped to that topic.

[Bild] NateDhaliwal: Maybe if you have a common word across support tickets, or just a common word in general, you can try that? Just suggesting a workaround A common word is the opposite of what I want. I don’t want my search results to have EVERY ticket, I want a way to search for a specific ticket. That’s why topic ID would be ideal. They are automatically generated and unique. [Bild] pfaffman: Did you try the code in Topic ID as a variable? - #7 by awesomerobot No, I think the code I’m using was also awesomerobot’s originally, but I can’t seem to find it’s source anymore. I prefer the placement of what I’m currently using better than that block under the text. Well, I can’t do that. Maybe you can. I have a certain set of skills. Coding isn't among them.

[Bild] tknospdr: Well, I can’t do that. Maybe you can. I have a certain set of skills. Coding isn't among them. Then perhaps you should move this topic to #marketplace or #feature.

[Bild] tknospdr: A common word is the opposite of what I want. I don’t want my search results to have EVERY ticket, I want a way to search for a specific ticket. That’s why topic ID would be ideal. They are automatically generated and unique. You misunderstand me. I meant having a common word including the topic:id parameter, so that only results from that topic show up. The common word removes the need to change words like ‘hi’ and ‘hello’.

@tknospdr @pfaffman I cobbled together a quick component that allows you to input the topic id and jump to it. Create a new component, and add this to the JS tab under the Edit CSS/HTML button[1]: import { apiInitializer } from "discourse/lib/api"; import Component from '@glimmer/component'; import { action } from "@ember/object"; import Form from "discourse/components/form"; import DiscourseURL from "discourse/lib/url"; export default apiInitializer((api) => { api.renderBeforeWrapperOutlet("full-page-search-filters", class GoToTopic extends Component { @action handleSubmit(data) { DiscourseURL.routeTo(`/t/${data.id}`); } } ); }); This adds an input to the Search page: [image] The Submit button is to go to the topic[2]; it does not affect search results. Hope this helps! My first time using FormKit, it’s really cool! ↩︎ I couldn’t change the button text, as that would require locales… which would need a whole TC repo, which might be overkill :person_shrugging:. ↩︎

Thanks @NateDhaliwal, I appreciate the effort. I created the component, pasted the code under the JS tab. Made sure it was active on my theme, but no love. This is what my search page looks like: [search]

Topic ID als Variable?

Entwickler

awesomerobot (Kris) 1. Oktober 2025 um 14:22 33

Ich konnte mich nicht früher darum kümmern, aber ich bin froh, dass Sie es herausgefunden haben! Das sieht nach einer vernünftigen Lösung aus.

Thema		Antworten	Aufrufe
Searching for the topic/post by ID? Feature	42	8842	9. August 2025
Get topic id when the topic show page loads Development	21	2784	24. Juni 2020
Topic Template Placeholder Text theme component Theme component	60	7694	21. August 2026
Search API parameters Development	15	3608	13. Juli 2017
Howto show the topic id in Metadata of initial Post Development	13	3280	17. März 2021

Topic ID als Variable?

Verwandte Themen