It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
Has anybody successfully managed to exclude headings from the TOC that have different names? For example if I want to exclude the two following headers from my TOC
Issues
Management
what RegEx would I use?
Steffen, thank you, that worked. I agree with other people, the Confluence help for this is appalling and totally unhelpful. The help in the macro is absolutely useless and has been for years. Why this hasn't been fixed is beyond me.
I agree. Atlassian's documentation that refers people to Sun's RegEx docuemntation is woefully inadequate. I think all they would need to do to appease 95% of users who just want to exclude a handful of names from the TOC list is add a few examples:
(Issues|Management)
(Issues|Management|Examples|Revision History)
A few simple examples would explain how to use the exclusion feature for the vast majority of users.
Hey Luke!
I came across your post just now and thought I'd let you know that I added an example to the doc.
Let me know what you think,
Javier.
https://confluence.atlassian.com/doc/table-of-contents-macro-182682099.html
Just read through this topic again, and I'm not sure which example you're referring to. I don't see anything that explains the syntax (Issues|Management) used for excluding multiple headings.
Some general thoughts:
Although regular expressions can be quite complex, a few simple rules are probably enough to know how to use them in the table of contents macro.
What is most important to know, is this:
The combinatin of both is .* and that stands for basically every combination of numbers and letters, e.g. "a", "1", "abc", "123", "abc 123 xyz", but also "" (nothing at all = a letter or number that occurs zero times).
And so
Thank you so much for this amazing informations according 'include' and 'exclude' parameters in Table of Contents Macro -> Should be transferred right into documentation!
That helps a lot and offers the opportunity to find the best solution by your own.
@Atlassian: see the complaints below and fix the documentation which is years out of date. This should be a simple task to do. users shouldn't have to "See Sun's Regex documentation for examples of constructing regular expression strings." Even if they were developers they shouldn't have to, let alone the rest of us!
Worked perfect for me - thanks to @Steffen Heller
-> Maybe you can also help me with a problem belonging to this trouble here
Problem:
I can't use a specific word, there are several questions on the page which start with different words -> is there an opportunity to exclude h2 after the used (Recent).* excluding?
Thanks!
Complex question, To make it short, I don't think that what you want is possible as those regular expressions only refer to the headline text but not any kind of underlying source code.
Possible workaround?
Would it be possible to add a consistent prefix to the questions e.g. having all questions start with "Q:"?
PS: I am not an expert on that, just a normal user that was searching for a solution and posted it here (years ago ;-))
Thanks for your answer!
No expert? That's impossible ;) because you solved a problem many people had.
Workaround sounds good, but i'm afraid that starting with a certain kind of letter is impossible.
But I will try and post my results!
Made a workworkaround:
Not very elegant, but worked. So all questions (which have heading 3) will not be shown.
I tried exclude with a certain ending (in my case '?' -> because all questions should end with ?) by using .*? -> did not work
Wohoo - worked perfect - combined both and now it's perfect (as long as all questions end with ?)
Looks like this now:
{toc:exclude=
(Recent).*|.*\?}
Or just as text in the exclude macro: (Recent).*|.*\?
Thank you so much for your help @Steffen Heller - saved my day!
Hello Steffen,
just saw this post. Can I also exclude the title of the document?
Because the title is H1, and other headings are also H1, the document looks like this when exported as pdf:
1. Title of document
1.1 Bla
1.1.1 Blabla
1.1.2 Blablabla
1.2 Blu
1.2.1 Blublu
etc etc..
Because of the h1 in the title the whole document numbering is wrong. And I tried h2 and h3 then excluded h1 but then h3 numbering is not shown at all.
I am afraid I cannot fully follow your explanation. Specifically, I don't understand in what way the h1 in the title makes the numbering wrong.
Can you explain the following:
What do you mean by "title"?
The first heading in the page (= your "1. Title of document") or the page name?
And how do you export to PDF?
With Tools > Export to PDF or with Browse > Space Admin > PDF Export
And just to be sure:
Are you talking about the TOC macro or do make space exports and use the "normal" TOC that is a part of that?
Title= Page Name
I export from the page directly: Tools > Export to PDF
But I also tried exporting it from Space Operations > PDF Export > Custom Export.
I´m talking about the Toc Macro ;)
Hi Yousaf,
i tried to reproduce your problem. As you can see on the pic, page title is never a part of TOC.
How did you produce numbering in the page title?
How did you create the numbering in TOC:
Maybe this creates the problem - even if it doesn't explain the numbering and appearing for page title.
Another option could be a Confluence Theme running in background that influences list style and/or pdf export
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreHi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.