Exclude/ignore custom Headlines?

  • Hey.

    I was wondering, if it′s possible to exclude or ignore custom Headlines from TOC+. I saw the option to exclude with words, but they are too many and different for my use since they are loaded dynamically by a plugin.
    In my case, additional content is added to the page content via shortcode. Unfortunately, this content has an unsightly heading structure, which cannot currently be changed and thus breaks the actual structure and is displayed in the TOC+.
    Ideally, you can exclude the desired heading via custom class or ID-list. Are there any possible expansion plans in this direction od do you have another idea for this?

    Thanks
    Maik

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support J Burns

    (@subiewrx)

    Hi @bmaik,

    Thanks for reaching out!

    Just to confirm, you would like an exclusion/ignore option based on shortcodes, custom class or ID-list?

    If that’s the case, I would be happy to add this to our internal feature request list. If there are any other specific details, please feel free to share them with me so I can include them in the request.

    Thanks!

    Thread Starter Maik Bernstein

    (@bmaik)

    Hi @subiewrx,

    Yes, exactly that.

    In my case, additional content is loaded dynamically, which means that in addition to the static content, the resolved shortcode content breaks the TOC structure.

    It would be perfect if you could exclude individual classes or IDs and these are also inherited downwards so that all child elements are also excluded. Here is a small example:

    # static H1
    - static-p-content

    ## static H2
    - static-p-content

    [shortcode with dynamic content] <-- to exclude via class/ID
    - [ # dynamic H1 (breaks TOC) ] <-- to exclude via inheritance
    - [ - static-p-content ]
    - [ ... ]

    ## static H2
    - static-p-content
    ...

    I hope this helps and it would be great if this feature request would be included in this great plugin in the future. ??

    Maik

    —
    edit: closing ticket

    • This reply was modified 3 weeks, 2 days ago by Maik Bernstein. Reason: closing ticket
    Plugin Support J Burns

    (@subiewrx)

    Hi @bmaik,

    Thanks for the follow up and including the additional details.

    I have included that information in the feature request along with your support inquiry.

    If the development team implements this feature in a future release, you’ll be directly notified.

    Thanks again for your feedback on how we can improve the plugin!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.