Hi, I need to create two pages with the same name in two different locations in the same space. The problem I have come across is that I can not create a page with the same name in one space. When I attempt that, I get "A page already exists with the title 'foo' in this space. Please use a different title for this page." This is how we want to structure the space: Product 1 * Intro * Pricelist * How to use * License info * Support * Document templates Product 2 * Intro * Pricelist * How to use * License info * Support * Document templates I found a lot of people with this problem, a company equal to Atlassian should not have a dumb vision for structure of directory tree. Any ideas on how i can set this up in one space? Note - We are using Confluence 6.10.1

Its problably too late but I would reccomend the following structure 1. Product XPTO * 1.1 Intro * 1.2 Pricelist * 1.3 How to use * 1.4 License info * 1.5 Support * 1.6 Document templates 2. Product XPTOX * 2.1 Intro * 2.2 Pricelist * 2.3 How to use * 2.4 License info * 2.5 Support * 3.6 Document templates So you still have unique page names and its still friendly. Hope it helps.

Then I definitly don't share the philosophy. To me it's counter intuitive. Anyways, as I said, we'll go with this.Thanks for taking the time Nic :)

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to create two pages with the same name in different locations in same space?

CesarCEARA

Hi,

I need to create two pages with the same name in two different locations in the same space.

The problem I have come across is that I can not create a page with the same name in one space.

When I attempt that, I get

"A page already exists with the title 'foo' in this space. Please use a different title for this page."

This is how we want to structure the space:

Product 1

Intro
Pricelist
How to use
License info
Support
Document templates

Product 2

Intro
Pricelist
How to use
License info
Support
Document templates

I found a lot of people with this problem, a company equal to Atlassian should not have a dumb vision for structure of directory tree.

Any ideas on how i can set this up in one space?

Note - We are using Confluence 6.10.1

Accepted answers

All comments

Nic Brough -Adaptavist-

You can't. Page names must be unique within a space.

Atlassian made this decision a long time ago and have no intention of changing it, as the majority of their users prefer or even need unique page names.

Fabienne Gerhard

Hi @CesarCEARA - of course @Nic Brough -Adaptavist- is right.

However it is possible using an addon - have a look on Scroll Versions, one of the features is duplicating page names.

But I have to say - for better usage I would recommend to find another solution. Why not using product name at the beginning of the page title, or put most of the informations on one page. Using ToC macro it's easy to navigate.

Bill Bailey

Yes, this is how I solved this issue, prepending a product number/name in front of the child pages.

Then when exporting to PDF (using Scroll), I just override the page title to the more generic version.

Fabienne Gerhard

Did you use Scroll PDF? How did you make it?

Bill Bailey

Yes, exactly. But version 3.x. Can't move to the new 4.x version (all power user features stripped).

Spyros Mylonas

Dear all,

@CesarCEARA case is very common so I find it strange that this option is not supported by confluence.

I am currently migrating from Nuclino to Confluence (still in trial mode) and I ran into this issue.

Now I need to re-evaluate my decision to move to Confluence.

Thanks.

Bob Sampson

Would like to see the data backing up the "majority of their users prefer or even need unique page name". I have design system website content on Confluence, and I have 15 "Overview" pages and have to use stupid emojis to have different names.

#1 - Every page in your Confluence has a unique 10 digit number, meaning you can have 10 billion pages in each space.

#2 - Looking at the Url of each of my overview pages with emojis, they all end in /Overview, so the actual page name is in a database somewhere.

This vibes of tech debt they don't want to spend time on.

Nic Brough -Adaptavist-

Ok, so to answer the points first

#1 - those are not friendly names, like "Overview" is

#2 - yes, with emoji-that-doesn't-help-Overview as a name

It's not "tech debt", it's "we designed it this way". Most wikis don't have duplicate page names, in fact Confluence is weaker on this than most because it allows you to use the same name for pages in many spaces. (Compare with the world's most used wiki - Mediawiki. There's only one page in Wikipedia called Overview, whereas Confluence will let you do ABC:Overview, DEF:Overview and so-on)

Elson Soares

Its problably too late but I would reccomend the following structure

1. Product XPTO

1.1 Intro
1.2 Pricelist
1.3 How to use
1.4 License info
1.5 Support
1.6 Document templates

2. Product XPTOX

2.1 Intro
2.2 Pricelist
2.3 How to use
2.4 License info
2.5 Support
3.6 Document templates

So you still have unique page names and its still friendly.

Hope it helps.

Pilou

It is a nice way to go. but unfortunately it will still get heavier as there are more and more category layers as in our case, that is not even exhaustive as tools is also containing the documentation for the tools themselves, for example, and departement categories are themselves parented to more generic categories.

MOTION DEPARTMENT

Animation

worflow
tools
technical documentation

Rig

worflow
tools
technical documentation

ASSET DEPARTMENT

Modeling

worflow
tools
technical documentation

Texture

worflow
tools
technical documentation

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

server

confluence-server