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

Copying a page to a new space should not prepend 'Copy Of' to the copied page

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 3.0
    • 2.10.2
    • None

      Currently a page copy to a new space results in the string "copy of" being pre-pended to the page title.

      Removing the pre-pended text before clicking Save results in the error "The title <page title> already exists in space <originating space>" whereas the page is not intended for the originating space!

      The copy function should be updated to allow copying to a new space in a single step without having to edit the title.

          Form Name

            [CONFSERVER-8273] Copying a page to a new space should not prepend 'Copy Of' to the copied page

            This has been fixed as issue CONF-14883.

            Mark Hrynczak (Inactive) added a comment - This has been fixed as issue CONF-14883 .

            David added a comment - - edited

            This issue also affects the create page action. It is very similar to the noted issue in the copy action, in that if you attempt to create a page in a space different from the one you started in the check for the page name is applied against the original space instead of the target space. As a consequence it is possible to create duplicate pages in the target space using create page as well.

            To reproduce:
            1) Start in a space other than the planned target
            2) Select Add Page
            3) Enter a page title that isn't in the current space (could be a duplicate name in the other space)
            4) Save

            It makes some sense for these two to be connected since the copy page action is derived from the create page action.

            Generated using Confluence 2.7.3

            David added a comment - - edited This issue also affects the create page action. It is very similar to the noted issue in the copy action, in that if you attempt to create a page in a space different from the one you started in the check for the page name is applied against the original space instead of the target space. As a consequence it is possible to create duplicate pages in the target space using create page as well. To reproduce: 1) Start in a space other than the planned target 2) Select Add Page 3) Enter a page title that isn't in the current space (could be a duplicate name in the other space) 4) Save It makes some sense for these two to be connected since the copy page action is derived from the create page action. Generated using Confluence 2.7.3

            Jason Kabel added a comment - - edited

            I would like to clarify David's point: This bug allows multiple pages with the same name to be created in the target space. At this point, only one of the pages is accessible.

            To reproduce:
            1) Create a page with a certain name
            2) Create a page in another space with the same name
            3) Copy one to the same space as the other, ensuring that the page names match

            At this point, both pages will exist in the target space, with the same title. Both will show up in children listings. However, only one page will be accessible (links redirect to only one of the pages)

            We are using Confluence 2.7.3

            Jason Kabel added a comment - - edited I would like to clarify David's point: This bug allows multiple pages with the same name to be created in the target space. At this point, only one of the pages is accessible. To reproduce: 1) Create a page with a certain name 2) Create a page in another space with the same name 3) Copy one to the same space as the other, ensuring that the page names match At this point, both pages will exist in the target space, with the same title. Both will show up in children listings. However, only one page will be accessible (links redirect to only one of the pages) We are using Confluence 2.7.3

            I agree this should be re-classified as a bug (and fixed).

            Jason Kabel added a comment - I agree this should be re-classified as a bug (and fixed).

            David added a comment - - edited

            We noticed an issue where three pages with the same name showed up under a single parent and this bug appears to be the likely cause. I had managed to replicate the situation using the method described here.

            I find it strange that the copy functionality isn't using the same check that edit (allows move) or create does since those do appear to check the target space vs the just the local one.

            David added a comment - - edited We noticed an issue where three pages with the same name showed up under a single parent and this bug appears to be the likely cause. I had managed to replicate the situation using the method described here. I find it strange that the copy functionality isn't using the same check that edit (allows move) or create does since those do appear to check the target space vs the just the local one.

            I think that the fact that the titles them selves needs to be unique within a spec is actuaqlly the culprit here and rather than working around it in the copy procedure this behaviour should be changed.

            I mean for example: "TODO" is not really unlikely to be a possible title on several places within the same space.

            Maybe i am missing something fundamental basics concerning wikis here but you have to admit that it can lead to rather strange effects.

            As a note this is really the first thing that really does not work for me, i really like Confluence so this is not a bashing.

            Henrik Johansson added a comment - I think that the fact that the titles them selves needs to be unique within a spec is actuaqlly the culprit here and rather than working around it in the copy procedure this behaviour should be changed. I mean for example: "TODO" is not really unlikely to be a possible title on several places within the same space. Maybe i am missing something fundamental basics concerning wikis here but you have to admit that it can lead to rather strange effects. As a note this is really the first thing that really does not work for me, i really like Confluence so this is not a bashing.

            I just ran into this today as well...

            I'd say that this should be classified as a bug and not an improvement. I'd have to agree with Shawn's comments regarding Confluence checking the target instead of the source space.

            Please fix. Thanks!

            Deleted Account (Inactive) added a comment - I just ran into this today as well... I'd say that this should be classified as a bug and not an improvement. I'd have to agree with Shawn's comments regarding Confluence checking the target instead of the source space. Please fix. Thanks!

            I just ran into this issue, and it is incredibly annoying. Each page must be given a different name when copying, then I have to go edit the page and rename it to what it is supposed to be. This should be a very easy fix, just check the target space instead of the source space!

            Shawn Stepper added a comment - I just ran into this issue, and it is incredibly annoying. Each page must be given a different name when copying, then I have to go edit the page and rename it to what it is supposed to be. This should be a very easy fix, just check the target space instead of the source space!

            Bob Swift added a comment -

            Particularly annoying when trying to set up a new space with a bunch of pages that are very similar to pages in an existing space.

            Bob Swift added a comment - Particularly annoying when trying to set up a new space with a bunch of pages that are very similar to pages in an existing space.

              Unassigned Unassigned
              8e4776a8c82a Nick Waanders
              Affected customers:
              12 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: