You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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:
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
2. Product XPTOX
So you still have unique page names and its still friendly.
Hope it helps.
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.
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.
@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.
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.
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)
To pile on, if you want pretty URLs, then you have to have unique names. If were OK with all URLs being "...pageID=122334" Then you could do what you want. It just isn;t practicle -- you need unique URLs, and you want to be able to change the page hierachy without breaking the URL (why you can't have "/toppage/childpage/overview"
And then when it comes to search, if you have 25 pages with the title of "Overview", it makes it hard to find the results you want.
I would have to go with Cesar on this one too.
As a user, I don't care about having nice urls, that's not how people will navigate the wiki. They will scroll into the menu categories.
With that being said, I don't know why confluence couldn't not offer the possibility to edit the label of the page that the user will see when the ID of the page, whether it's a random number or a string remains untouched.
It would be like asking for someone who code in python to add the full namespace of the command in the command name itself. it doesn't really make sense.
It is what it is and we'll live with it, but that definitly something I would like to go around.
I'm just using your collegue own word :)
And if you read me again, I have no issue with uniqueness :)
I'm talking about how data is displayed in the UI. Which is, well, the most important matter when it come to creating interfaces.
If you tell me that applying a label on a page that have no other role than just visual is not possible and that it's the case in every wiki in the world, thn I would say that it's unfortunate.
Again I will live with that as others already do, the tone of you post is unecessary.
That's alright no worries :)
I understand the need of uniqueness. What I don't understand is why it has to limit the way it's been displayed ?
there is plenty of data system, that have internal data used to make the tool work and public data that are shown to the user in the way the user see fit.
Most 3d software nodal systems work this way, nodes are registered and the name of the node can be changed at will.
google suite work this way, you can register an event and change the name of the event, and plenty more.
I would really like your input on why exactly this uniqueness necessarily forces confluence, and other wikis for that matters, not to have this functionnality.
well as the exemple of Cesar shows, there is.
is better than
I may miss something in wiki philosophy, but I don't see how the second exemple can be better, specially if you add more sub categories.
But you understand that the label is not the ID of the entity ? its only purpose it to show data to the user. It is not involved in the tool mechanics.
It's the whole purpose of having metadata embedded in an entity.
Having entities that share the same label doesn't mean they share the same ID (whether it's a string or a number)