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

Allow administrators to force urls to viewpage urls + number rather than human readable titles.

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • 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.

      From https://answers.atlassian.com/questions/130665/always-show-confluence-url-in-page-id-format#comment-131813

      Hello there,

      Our customer would like to configure Confluence so it always shows page URL in following format;

      <Confluence Base URL>/pages/viewpage.action?pageid=<pageid>

      Currently, when it contains only ASCII letters, the URL looks like

      <Confluence Base URL>/display/<Space Key>/<Page Title>

      but they don't want it.

      Any way to achive this requirement? Please let me know.

      Regards,

      Daisuke Niwa

            [CONFSERVER-27966] Allow administrators to force urls to viewpage urls + number rather than human readable titles.

            +1 for adding this as an option!

            We really need this.

             

            Ozan Bayram added a comment - +1 for adding this as an option! We really need this.  

            There is another issue related to this isue: https://jira.atlassian.com/browse/CONFSERVER-45898, which is still under review and has some votes!

             

            Auke Miedema added a comment - There is another issue related to this isue: https://jira.atlassian.com/browse/CONFSERVER-45898 , which is still under review and has some votes!  

            Same, broken links due to page changes are making us look ridiculous to our customers.

            Jan De Bruyn added a comment - Same, broken links due to page changes are making us look ridiculous to our customers.

            Any idea why this issue is "resolved" as "won't fix" ?

            Is seems a pretty reasonable request to me. I see very little if any benefit in having the title in the URL, and I'd rather use pageId for all the pages, so that all the links to Confluence pages are permanent.

            Fortunately, even if your page uses the so-called "pretty URL", the pageId URL still works once you obtain it, so you can add a non-ASCII character in the title, save, copy the URL, and then change back the title. Clumsy at best.

             

            Olivier Gérardin added a comment - Any idea why this issue is "resolved" as "won't fix" ? Is seems a pretty reasonable request to me. I see very little if any benefit in having the title in the URL, and I'd rather use pageId for all the pages, so that all the links to Confluence pages are permanent. Fortunately, even if your page uses the so-called "pretty URL", the pageId URL still works once you obtain it, so you can add a non-ASCII character in the title, save, copy the URL, and then change back the title. Clumsy at best.  

            Jim Walsh added a comment -

            We need this administrative option as well.  Broken links are a nuisance to deal with.

            Jim Walsh added a comment - We need this administrative option as well.  Broken links are a nuisance to deal with.

            I too have a great need for this at my company, for link hygiene as well as security

            Deleted Account (Inactive) added a comment - I too have a great need for this at my company, for link hygiene as well as security

            Hi guys

            This is quite an issue for larger enterprises where there is a lot of content that is referenced in a lot of different places, can this please be revisited?

            Our use case is knowledge management articles for which we want static links for many users (300+)

            Thanks

            Maree

            Maree Milne added a comment - Hi guys This is quite an issue for larger enterprises where there is a lot of content that is referenced in a lot of different places, can this please be revisited? Our use case is knowledge management articles for which we want static links for many users (300+) Thanks Maree

            +1 for adding this as an option!
            John P reasoned it perfectly well, that is exactly our use case.

            Boris Holzer added a comment - +1 for adding this as an option! John P reasoned it perfectly well, that is exactly our use case.

            +1 for adding this as an option!

            Andrey Kiyanovsky added a comment - +1 for adding this as an option!

            +1 for adding this as an option!

            Can anyone confirm that this technique works under 5.6.6? I see a comment above that it is not functional in 5.6.5. I am on 5.6.6.

            David Luke added a comment - +1 for adding this as an option! Can anyone confirm that this technique works under 5.6.6? I see a comment above that it is not functional in 5.6.5. I am on 5.6.6.

              jmasson@atlassian.com John Masson
              testtwong Tim Wong (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              26 Start watching this issue

                Created:
                Updated:
                Resolved: