H3 not displaying with Finsweet Attributes

Hello guys, I hope you’re doing well. I have a little problem with Finsweet Attributes “Table of content”.
Indeed, on those pages ( Top 10 des influenceurs décoration en France ) we should have the H3 showing (it’s supposed to be the name of the influencers so Google and AI bots could rank us better).
Even, if I followed exactly the structure recommended by Finsweet, it won’t appear.

Does anyone knows why? Here’s the read-only link: Webflow - Site Kolsquare

1 Like

Hey @Nicolas_Menager1 ,

Since you have 2 rich text elements, you might want to denote it via attributes like contents-2, link-2 as mentioned in the v1 documentation.

In case, you don’t want TOC to populate anything from the first rich text element that you have linked to ‘subheading’ field from the CMS, you can remove the fs-toc-element="contents" attribute from it and publish to see if that works.

That being said, if you want to have multiple rich text elements to be considered for the TOC, I have seen people facing issues with ‘contents-2’ & ‘links-2’ approach as well, where some elements are not populated in the TOC.

So, you might want to use Finsweet’s updated v2 solution for the Table of Contents, where you have the option to specify instance attribute fs-toc-instance for both the rich text element and each link element.

Essentially, what you can do is for the second rich text element that you have on the page, add another custom attribute as fs-toc-instance="2" and have another copy of toc-link-wrapper element where you specify the fs-toc-instance="2" attribute for each toc element as well.

I tested this approach with v2 attributes cloneable and it works for multiple rich text elements with one table of content visually. In case, you have all the headings in the rich text element setup as required, v2 should work for your use-case as well.

Hope this gives you some idea.

2 Likes

Thank you so much :wink: You rock! First of all, I was doubting cause I’m not using 2 different rich text elements. That’s for my blog not this and everything works fine! But then I spotted that the subheading had the fs-toc-element=”contents”! So I removed it and now everything works perfectly

1 Like