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

      At the moment I can create pages with names like "To be continued..." or "Stars - Little Galaxy Burps", however I cant create a page titled "Help! I'm a fish!" due to restricted characters in Page Title.

      I understand that some extended characters (^, !, | etc) are used for other purposes but I can see there being two ways out of this:

      1. Escaping - "Help! I\'m a fish!"
      2. Implementation of Alternative Titles, so I could set the page title to "aquamarine.fish.helpme" and the alternative title set to something else. You would continue to link to "aquamarine.fish.helpme" but on the page itself (in the breadcrumb trail, in the page display, in the hierarchical view, in the children list etc) it would show the alternative title. [aquamarine.fish.helpme] would show "Help! I'm a fish!" as the link, perhaps this could be an option which could be configured in the administration area ... "Use displayed title where entered?" or something like that.

      I think there is an issue around for #2. This could be entirely optional (it would default to showing the page title as the alternative / display title) and the page title could continue to be used with the current characters allowed. This would also make it compatable with previous system data. The tables could be extended to fit on upgrade.

      The related issue is CONF-885

      Note - this may be a duplicate, but I searched around and couldnt find any issues ... Maybe Im looking in the wrong place.

            [CONFSERVER-984] Extended Characters to be allowed in Page Title

            BillA added a comment -

            fixed on Confluence 4.1. Try the release candidate to test it yourself.

            BillA added a comment - fixed on Confluence 4.1. Try the release candidate to test it yourself.

            BillA added a comment -

            BillA added a comment - See 4.1-rc1 for the fix http://confluence.atlassian.com/pages/viewpage.action?pageId=269981290

            CareFlight added a comment -

            So now 4.0 is out and CONF-9458 (which appears to duplicate this issue) is trivial to fix can you reassess this?

            Another factor in this is that pages in confluence are hierarchical but the namespace is flat (itself a somewhat odd distinction), so extra characters are useful to make page titles unique.

            CareFlight added a comment - So now 4.0 is out and CONF-9458 (which appears to duplicate this issue) is trivial to fix can you reassess this? Another factor in this is that pages in confluence are hierarchical but the namespace is flat (itself a somewhat odd distinction), so extra characters are useful to make page titles unique.

            Matt Ryall added a comment -

            The change to the storage format which is coming in Confluence 4.0 means we're much closer to being able to achieve it than we were two years ago.

            This feature is still something we'd like to implement, but we don't have any plans to fix it in the near future.

            Matt Ryall added a comment - The change to the storage format which is coming in Confluence 4.0 means we're much closer to being able to achieve it than we were two years ago. This feature is still something we'd like to implement, but we don't have any plans to fix it in the near future.

            Laurent Lacôte added a comment - - edited

            Hi Atlassian team,
            I'd like to know the updated status of this issue. On our documentation website, we have a few spaces in French, steadily growing in content, and using special characters (accents, ?, etc...) in titles prevent them from being "aliased" in URL.

            exemple :
            title: "What is Petals ESB?"
            url: "http://doc.petalslink.com/pages/viewpage.action?pageId=1803735"

            I'd like to have "http://doc.petalslink.com/display/petalsesb/what-is-petals-esb"

            (Running on 3.1 / Linux Ubuntu 9.04 VM)

            Will this be fixed in next Confluence version? Or would there be a workaround?

            Thanks for your answer.

            Best regards,

            Laurent Lacôte

            Laurent Lacôte added a comment - - edited Hi Atlassian team, I'd like to know the updated status of this issue. On our documentation website, we have a few spaces in French, steadily growing in content, and using special characters (accents, ?, etc...) in titles prevent them from being "aliased" in URL. exemple : title: "What is Petals ESB?" url: "http://doc.petalslink.com/pages/viewpage.action?pageId=1803735" I'd like to have "http://doc.petalslink.com/display/petalsesb/what-is-petals-esb" (Running on 3.1 / Linux Ubuntu 9.04 VM) Will this be fixed in next Confluence version? Or would there be a workaround? Thanks for your answer. Best regards, Laurent Lacôte

            I would definitely like this feature. As a commenter on another issue said, it's driving me batty. Maybe I'll eventually remember not to use certain characters that I really want to use (/, :, and ?).

            I wonder if it's possible to sidestep the problem, technically, entirely – maybe we just need to start storing two versions of page titles - one is the human-readable/full-punctuation form, and the other is our internal/calculated/cleaned format? Or something more inventive/creative/etc.?

            I'm not trying to minimize the technical hurdles that would need to be overcome - this would just be a really cool feature – one of those, 'make the interface disappear' things.

            To me, a page title is crucial because it conveys a lot of information - it's how we find things on the wiki. It should be given search preference, and we need to be able to scan it in search results and find meaning, and that meaning is sometimes best relayed when we're able to use special punctuation characters, etc.

            A page title is also just text on a page - just like every other piece of regular text content on a wiki page - it just happens to up at the top of the page and shows up prominently in search results. How we choose to link to that text is up to us. We can just 'clean' the URL, but keep the regular full-wacky-character title for display.

            Peter Smith (Atlassian) added a comment - I would definitely like this feature. As a commenter on another issue said, it's driving me batty. Maybe I'll eventually remember not to use certain characters that I really want to use (/, :, and ?). I wonder if it's possible to sidestep the problem, technically, entirely – maybe we just need to start storing two versions of page titles - one is the human-readable/full-punctuation form, and the other is our internal/calculated/cleaned format? Or something more inventive/creative/etc.? I'm not trying to minimize the technical hurdles that would need to be overcome - this would just be a really cool feature – one of those, 'make the interface disappear' things. To me, a page title is crucial because it conveys a lot of information - it's how we find things on the wiki. It should be given search preference, and we need to be able to scan it in search results and find meaning, and that meaning is sometimes best relayed when we're able to use special punctuation characters, etc. A page title is also just text on a page - just like every other piece of regular text content on a wiki page - it just happens to up at the top of the page and shows up prominently in search results. How we choose to link to that text is up to us. We can just 'clean' the URL, but keep the regular full-wacky-character title for display.

            As of Confluence 1.5, the following additional characters will be permitted in page titles:

            ! & ( ) * ~ $ _

            See CONF-4238 for more information on what characters are still not permitted and why.

            This issue will remain open to cover the possibility of having a more complex escape syntax, or having distinct "linking titles" for pages that have potentially conflicting characters in their titles.

            Charles Miller (Inactive) added a comment - As of Confluence 1.5, the following additional characters will be permitted in page titles: ! & ( ) * ~ $ _ See CONF-4238 for more information on what characters are still not permitted and why. This issue will remain open to cover the possibility of having a more complex escape syntax, or having distinct "linking titles" for pages that have potentially conflicting characters in their titles.

            We need to go through each reserved character and justify why it is reserved.

            If it's a Confluence markup character, does it still conflict with the new renderer?
            If it's a reserved URL character, can we just use the pageId style of URL?

            If it's not reserved for a good reason, remove the restriction.

            Charles Miller (Inactive) added a comment - We need to go through each reserved character and justify why it is reserved. If it's a Confluence markup character, does it still conflict with the new renderer? If it's a reserved URL character, can we just use the pageId style of URL? If it's not reserved for a good reason, remove the restriction.

            + character is allowed in page titles, but is not displayed in the UI. In URLs, '' represents both '' and ' '.

            Dzmitry Zhemchuhou added a comment - + character is allowed in page titles, but is not displayed in the UI. In URLs, ' ' represents both ' ' and ' '.

            BenjaminA added a comment -

            We need to support ampersands in page titles and page links too. Currently ampersands in new page links do not work.

            e.g. if you enter this on to a page [example & example] it will not create a link to a new page called [example & example] but rather just render it as non hyperlinked text.

            BenjaminA added a comment - We need to support ampersands in page titles and page links too. Currently ampersands in new page links do not work. e.g. if you enter this on to a page [example & example] it will not create a link to a new page called [example & example] but rather just render it as non hyperlinked text.

              Unassigned Unassigned
              dhardiker Dan Hardiker
              Votes:
              20 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: