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

Allow the export of only the most recent page version in XML exports

    • 1
    • 2
    • 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.

      Currently the XML export option for space exports will export all revisions of a page. There are use cases where a user would only want the newest version of a page or pages in an export and wishes for the XML of the content instead of the rendered HTML (which exports only the current version). Adding the option to specify only the newest revision during an export would be useful.

            [CONFSERVER-22945] Allow the export of only the most recent page version in XML exports

            Thank you for raising this suggestion.
            We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.
            For more context, check out our Community blog on our updated workflow for Suggestions
            Cheers,

            Confluence Product Management

            Adam Barnes (Inactive) added a comment - Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our updated workflow for Suggestions Cheers, Confluence Product Management

            I think all 4 of these tickets are all related to the same request, can Atlassian combine them and merge the votes?
            https://jira.atlassian.com/browse/CONF-22945
            https://jira.atlassian.com/browse/CONF-27689
            https://jira.atlassian.com/browse/CONF-35666
            https://jira.atlassian.com/browse/CONF-32030

            Chris Johnson added a comment - I think all 4 of these tickets are all related to the same request, can Atlassian combine them and merge the votes? https://jira.atlassian.com/browse/CONF-22945 https://jira.atlassian.com/browse/CONF-27689 https://jira.atlassian.com/browse/CONF-35666 https://jira.atlassian.com/browse/CONF-32030

            I just realized that it is possible to do this with an intermediate step. I installed the Copy Space plugin, then used it to create a temporary copy of my space, making sure that "Use existing Authors and Dates" is not checked. That seems to copy only the current content to the new space.

            Then I can do an XML export from the new space and exclude all the page history.

            Hope that's helpful for you.

            Jeff Harris added a comment - I just realized that it is possible to do this with an intermediate step. I installed the Copy Space plugin, then used it to create a temporary copy of my space, making sure that "Use existing Authors and Dates" is not checked. That seems to copy only the current content to the new space. Then I can do an XML export from the new space and exclude all the page history. Hope that's helpful for you.

            I agree with Steven on this...although for different reasons. I'm trying to manage a localized documentation site with Confluence. It would be nice to be able to do a Space export to XML of the current content only to send to our translators. Once translated, we want to re-import the XML as a new Space.

            Right now, I'll probably have to build a tool that parses the XML export, extracts the current content, then lets me re-insert the translated content back into the original XML file to re-import it into Confluence. Kind of a pain.

            Jeff Harris added a comment - I agree with Steven on this...although for different reasons. I'm trying to manage a localized documentation site with Confluence. It would be nice to be able to do a Space export to XML of the current content only to send to our translators. Once translated, we want to re-import the XML as a new Space. Right now, I'll probably have to build a tool that parses the XML export, extracts the current content, then lets me re-insert the translated content back into the original XML file to re-import it into Confluence. Kind of a pain.

            Having XML export of the latest versions would be very useful. There are times where we need to do data-mining on our Confluence content, and being able to get the wiki output would be especially helpful.

            Now we have resorted to exporting HTML and processing that. However, it is much more difficult to process the HTML. Also, there is more variability because the HTML can change depending on the Confluence version and the theme.

            Steven Cogorno added a comment - Having XML export of the latest versions would be very useful. There are times where we need to do data-mining on our Confluence content, and being able to get the wiki output would be especially helpful. Now we have resorted to exporting HTML and processing that. However, it is much more difficult to process the HTML. Also, there is more variability because the HTML can change depending on the Confluence version and the theme.

              Unassigned Unassigned
              alaskowski Adam Laskowski (Inactive)
              Votes:
              10 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: