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

Editing a page that has TOC and saving without changing anything, it makes a new version.

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      Steps to reproduce:

      1. Create a page.
      2. Add some content and TOC
      3. Check the page version.
      4. Edit the page and don't do nothing.
      5. Check the page version, (Is expected no new version)
      6. Add a panel and inside of the panel add the TOC
      7. Save
      8. Check the page version, it should have a new version.
      9. Click on Edit the page, and don't edit anything
      10. Save
      11. Check the page version. _(It's not expected a new version, but it shows a new version).

      The same problem happen with code block.

            [CONFSERVER-40220] Editing a page that has TOC and saving without changing anything, it makes a new version.

            Thank you for taking the time to raise, comment or vote on this Bug. We regret to inform you that due to a limited number of reports and based on our current backlog of higher impact issues that we are closing this issue as Timed Out.

            If this issue is still impacting you on a recent version please feel free to comment with the affected version. Any further details you may be able to provide regarding reproduction or impact of this issue may help us better address this issue.

            Thanks again.
            Cheers,

            Confluence Product Management

            Adam Barnes (Inactive) added a comment - Thank you for taking the time to raise, comment or vote on this Bug. We regret to inform you that due to a limited number of reports and based on our current backlog of higher impact issues that we are closing this issue as Timed Out. If this issue is still impacting you on a recent version please feel free to comment with the affected version. Any further details you may be able to provide regarding reproduction or impact of this issue may help us better address this issue. Thanks again. Cheers, Confluence Product Management

            Pete Jaffe added a comment - - edited

            I originally submitted this as a support ticket, and it was acknowledged as a bug and spun out here.

            I noticed this as a result of a daemon process we run that publishes a wiki page based on introspecting part of our systems. When the system actually changes, the daemon will push content to Confluence that reflects the new configuration, a new page version is created, and Confluence sends out page edit notifications, etc. Prior to 5.8, this all worked perfectly, and we wouldn't get "false page edits" when the content the daemon was pushing wasn't any different.

            As of 5.8, the first thing that caused us to start getting constant new versions of the page was the introduction of the "Macro identification" feature described at https://developer.atlassian.com/confdev/development-resources/preparing-for-confluence-5-8.

            Once I introduced constant "Macro identification" values into the content template, I had expected things to have stabilized. However, I saw the Macro identification for a panel remained constant across daemon runs, but the Macro identification for the embedded TOC was constantly changing (despite us passing an explicit value).

            I then reproduced this by manually editing the page through the Confluence UI and saving without any changes. I then tried combinations of panel and toc, and isolated this particular nesting issue.

            For now, we've removed the containing panel as a workaround. While this isn't a very high priority bug, it would be great to get it fixed.

            Pete Jaffe added a comment - - edited I originally submitted this as a support ticket, and it was acknowledged as a bug and spun out here. I noticed this as a result of a daemon process we run that publishes a wiki page based on introspecting part of our systems. When the system actually changes, the daemon will push content to Confluence that reflects the new configuration, a new page version is created, and Confluence sends out page edit notifications, etc. Prior to 5.8, this all worked perfectly, and we wouldn't get "false page edits" when the content the daemon was pushing wasn't any different. As of 5.8, the first thing that caused us to start getting constant new versions of the page was the introduction of the "Macro identification" feature described at https://developer.atlassian.com/confdev/development-resources/preparing-for-confluence-5-8 . Once I introduced constant "Macro identification" values into the content template, I had expected things to have stabilized. However, I saw the Macro identification for a panel remained constant across daemon runs, but the Macro identification for the embedded TOC was constantly changing (despite us passing an explicit value). I then reproduced this by manually editing the page through the Confluence UI and saving without any changes. I then tried combinations of panel and toc, and isolated this particular nesting issue. For now, we've removed the containing panel as a workaround. While this isn't a very high priority bug, it would be great to get it fixed.

              Unassigned Unassigned
              wzanchet William Zanchet (Inactive)
              Affected customers:
              3 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: