Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-24126

toc macro's maxlevel wrong after 4.0 Upgrade

    XMLWordPrintable

Details

    • Bug
    • Resolution: Answered
    • Low
    • None
    • 4.0.3
    • None

    Description

      Since the 4.0 Upgrade, the toc macro seems to have lost its "maxlevel" attribute. The basic page template contains the following code:

      {toc:maxlevel=3}
      

      Under v4.0.3, the problem can be reproduced as follows:

      1. Edit a page with the toc macro above
        1. screenshot toc_edit attached shows that the toc macro block displays "maxlevel=3"

      1. Modify contents in the page, but NOT the macro
        1. for instance, add titles up to Level 6
      2. Save the page >> toc macro does not respect the maxlevel=3 attribute and displays all 6 title levels
        1. see screenshot toc_test attached

      1. if "edit" the macro, I can see before making any changes that maxlevel is set at 7 (default?), not at 3 (as was set before the 4.0 Upgrade)
        1. see screenshot toc_edit_level attached

      It stops occurring once the toc macro has been edited (or created) in the 4.0 Editor. It occurs only before the "upgraded" macro has been edited in the 4.0 Editor, in 4.0-Upgraded pages which originally contained the following Wiki code:

      {toc:maxlevel=3}
      

      Attachments

        1. toc_edit_level.jpg
          toc_edit_level.jpg
          84 kB
        2. toc_edit.jpg
          toc_edit.jpg
          19 kB
        3. toc_maxlevel_LC_display_v347.PNG
          toc_maxlevel_LC_display_v347.PNG
          11 kB
        4. toc_maxlevel_LC_wiki_v347.PNG
          toc_maxlevel_LC_wiki_v347.PNG
          40 kB
        5. toc_test.jpg
          toc_test.jpg
          16 kB
        6. toc_test.jpg
          toc_test.jpg
          24 kB

        Activity

          People

            Unassigned Unassigned
            cschedler Carlos Alberto Feijo Schedler [Atlassian]
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: