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

Use a page's content ID as the filename when exporting as HTML

XMLWordPrintable

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      When we export a page as HTML, if there is a unicode/high-bit character in the page title, there will be problems writing it to disk and being linked to properly. Instead, we should refer (and name) the pages using their content ID instead.

            [CONFSERVER-4862] Use a page's content ID as the filename when exporting as HTML

            Peter Camilleri [Atlassian] added a comment -

            See CR-ADVMACROS-43 for tech review

            Peter Camilleri [Atlassian] added a comment - See CR-ADVMACROS-43 for tech review

            AdrienA (Inactive) added a comment -

            The page ID is used for links, but it refers to the original server. We should refer to the local page on the disk.

            AdrienA (Inactive) added a comment - The page ID is used for links, but it refers to the original server. We should refer to the local page on the disk.

            RyanA added a comment -

            regression in Confluence 4.0

            RyanA added a comment - regression in Confluence 4.0

            Agnes Ro added a comment -

            Fixed.
            If the page title is not "safe", then the page id is used for the html filename in the export.

            Agnes Ro added a comment - Fixed. If the page title is not "safe", then the page id is used for the html filename in the export.

            Normand Brousseau added a comment -

            Referring the pages with their IDs would indeed solve the problem; however, when we use the 'Create link' feature of the RTF editor, the default used as a link name is the page name, and not the page or content ID. Furthermore, such default allow link names to be updated whenever the destination page name is modified, which makes for significant AND dynamic link names. How could we possibly use IDs for links without losing the advantages of built-in defaults and GUI features?

            Normand Brousseau added a comment - Referring the pages with their IDs would indeed solve the problem; however, when we use the 'Create link' feature of the RTF editor, the default used as a link name is the page name, and not the page or content ID. Furthermore, such default allow link names to be updated whenever the destination page name is modified, which makes for significant AND dynamic link names. How could we possibly use IDs for links without losing the advantages of built-in defaults and GUI features?

            Hernan Cunico added a comment -

            This issue relates to CONF-4958

            Hernan Cunico added a comment - This issue relates to CONF-4958

              pcamilleri Peter Camilleri [Atlassian]
              8d92d19feb5e Jeremy Higgs
              Votes:
              6 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: