Yes, you are looking at the wrong wrench. The second screenshot you provided is of the post admin wrench, at the bottom of every post. There is another admin wrench in the topic menu at the very bottom, before suggested topics.
Oi! I had the wrong wrench. Now I got it, many apologies, all is good
I seem to be missing the anchor links next to the headings, which allowed me to link to a specific section directly, for instance in this topic, like described in the start post:
Is this me or did this functionality disappear?
They should be there? I’m currently on my phone, but I grabbed this one by long-pressing on the gap to the side of the heading:
Yes, that topic has those anchor links, but that’s a topic that does not have the DiscoTOC.
But this topic has a TOC and does not have anchors: Beginner's guide to using Discourse Themes and this one does not have anchors either DiscourseConnect - Official Single-Sign-On for Discourse (sso)
EDIT Hmm…this topic does have anchors: Discourse API Documentation
Ah, I can explain. The topic you linked has html headings (
<h4> and so on) and initially the TOC component had its own logic for adding heading anchors. However, since then, core added automatic anchors and recently I removed the custom anchor login in the theme component. However, core’s anchor feature only works for Markdown headings (using
So that’s the OP here has anchors, but the linked guide doesn’t.
We probably should update that guide to use Markdown instead of HTML @JammyDodger.
Ah! That explains things perfectly, thanks Penar!!
I was clearly not paying enough attention yesterday. I have now swopped in Markdown headers for the two example topics.
Nice component, the # links created for the headings are very neat too.
Is there a way to move the icon link as pictured in the screenshot?
Right now it hovers over the left, in between the user icon and heading text (see below)
A suggestion if I may.
By nature, posts with TOC will be long. When the Google crawler sees the page it doesn’t see the TOC nor those nifty links to different parts of the page. Perhaps on the crawler version we can have those links show up for each heading/sub-heading.
Hi there, I wonder if there is a way to bulk apply the TOC to topics? We just installed the TOC component recently and now having to manually apply it to old topics is a bit tedious
I’ll double-check, but I don’t think that’s currently possible? Though I do sympathise with the manual edits. How many have you got left to do?
I don’t think we have a whole lot of them at the moment, though it’d be great if the team could consider implementing this feature in a future release
It was such a great idea @albert_vu that it’s now been added:
Great so I guess that I’d need to update the theme-component from my end?
If you check, I’ll think you’ll find it’s already been done.
But for anyone else wanting the swish new functionality, you can update the theme component from its customise page:
Hmmm, just thought of a scenario where a user doesn’t want to have a TOC in their topic, is there a way to revert that?
I like the tag element of it, so you could have a specific tag for TOC, and then remove it again if one is not desired?
I love the idea of automation, almost everytime and everywhere.
I haven’t updated DiscoTOC yet, but if it can take away option to insert TOC from toolbar when TOC comes from category it would be really nice touch. Like cherry top of the cake
Or, do opposite thing what @albert_vu asked — there would be an option insert something like
!toc if you understand what I’m meaning.
For ordinary users it could be confusing, though.
I can live with that but TOC is quite unneeded when there is somethng like only one or two headers. Because when there is a TOC a long post must be scrolled to bottom to find out… what is it in discourse-lingo… well, possibility to scroll dates. But that is quite rare edge case I reckon.
What is the purpose of the
anchor icon setting?
I could not find it anywhere. Was it removed in REFACTOR: General component overhaul (#19) · discourse/DiscoTOC@20366c6 · GitHub ?
Awesome component! However I’ve found a bug in how it parses and renders TOC’s which contain escaped and certain characters.
For example it doesn’t render these headers correctly
### <a name="profilename">**[\<Profile Name\>]**</a>
### [\<Profile Name\>]
### \<encoder\>-general=\<general parameters\>