Configuring page URL format in each space

[Naftali Kopilevich]

I know that Confluence supports 2 types of page URLs. the one includes the the page name, and the other includes the page ID instead. there is information regarding this in this Location .

Confluence decides which URL format to use based on whether the page name has only alphanumeric characters or also special characters. This means, that it is possible for Confluence to generate page URLs with page ID instead of page name, but currently confluence's default behavior is to generate the URL with the page name.

Many users require the URLs to be based on page id, in order to allow duplicate page names in the same space. This is a very common requirement when using Confluence for extensive technical documentation.

I would ask why is there no configuration at the space level, for the user to specify whether this space will attempt to create URLs exclusively based on page id or on attempt to use page name. Such a configuration can solve the problem that many users have with the unique page names. Users that know their space will have duplicate page names, will configure the space to only create page URLs with page ID. Users that want unique page names in their space, will configure the space to create URLs with page name.

[Fabio Racobaldo _Herzum_]

Hi @Naftali Kopilevich and welcome,

I understand you request but, for my knowledge, there is not a specific setting at space or global level. I see an open request for server/dc instance https://jira.atlassian.com/browse/CONFSERVER-45898 and one for cloud that seems incorrectly closed https://jira.atlassian.com/browse/CONFCLOUD-45898

My suggestion is to raise a support request to the Atlassian team https://support.atlassian.com/contact/#/

Fabio

[Naftali Kopilevich]

Thanks Fabio.

I read previous conversations on the issue of unique page names and saw atlassian's reasons for not changing this.

I meant to suggest a workaround that might let the user decide which type of behavior he wants in each of his spaces. 

I didn't see such a suggestion before, but this issue has been asked from atlassian since 2005, so maybe it did come up in the past...