Create pages with same title within the same space

[Thomas Schubert]

Atlassian Confluence 5.9.7

--

Our Confluence users want to write a documentation about several applications within their space 'TestSpace'. To each application 'App x'  they want to create the same set of subpages e.g.:

\TestSpace\

App 1\

'01 contacts'

'02 documentation'

'03 link to app'

'04 ...'

App 2\

'01 contacts'

'02 documentation'

'03 link to app'

'04 ...'

App n\

'01 contacts'

'02 documentation'

'03 link to app'

'04 ...'

On creating the 2nd page '01 contacts', confluence brings the following error:

Folgende Fehler sind aufgetreten:

• Im Bereich 'TestSpace' besteht bereits eine Seite mit der Überschrift '02 Contacts'

[en]:

Error: 

• in space 'TestSpace' a page with title '02 Contacts' alreqady exists.

What should they do to be able to create the wanted set of subpages?

[Thomas Schlegel]

Hi Thomas,

they can't do anything, it is not possible. There's a closed issue for that: https://jira.atlassian.com/browse/CONF-2524

They have to make the pages unique, maybe with a prefix "App 1 Contacts", "App 2 Contacts", ...

[EPS Software Engineering AG]

Hi Thomas,

Rodney and Thomas answered your question. Another solution would be placing each Application in a separate space.

What about using our Add-on Page Tree Creator to create the page tree quick and easy?

Try our Live Examples (no registration needed).

Marketplace link: Page Tree Creator.

Regards,
Stephan

[Rodney Hughes]

Yes, each page title MUST be unique as it rolls into the page URL

So just add a prefix

'App1 01 contacts'

'App1 02 documentation'

'App1 03 link to app'

'App1 04 ...'

'App2 01 contacts'

'App2 02 documentation'

'App2 03 link to app'

'App2 04 ...'

[Gildas Huart]

Hi,

Don't you find the solution a bit ugly ?

1st: it does not help to have clear content when making such trees :
App 1
- App 1 Contacts
- App 1 Documentation
- App 1 Link to app
App 2
- App 2 Contacts
- App 2 Documentation
- App 2 Link to app
App 3
- App 3 Contacts
- App 3 Documentation
- App 3 Link to app

2nd: i find sad that the container rules make the contributor change the content. In the opposite, should the container not adapt to the content ?

[Rodney Hughes]

As the saying goes "Beauty (or ugliness) is in the eye of the beholder"

We have some 250 Spaces in our system.  Each Space has a standardised initial structure of pages - one of those pages is titled <<Meetings>>

The child page(s) for each meeting have content such as "RSVP/attendee list" (eliminates use of 3rd part tools like Doodle), Agenda, Minutes of Meeting and file sharing.

So when a new meeting is set up the logical thing is to copy that "template" page(s) and just put either a unique meeting number identifier and/or a date and/or a city in the title.

consider when you are looking at a page without that identifier in the title, you can see the "breadcrumbs" links above the title of where you are, but a clue in the age title can't hurt :)

To me, adding an "App n" identifier to each page title is a "beautiful solution" ...:)