I have a process where I download wiki pages to a folder. Now I want to extend it to blog posts and custom content (specifically questions and answers). The page files are named after the page ID.
I wonder if blog post and custom content IDs can coexist with page IDs without being mangled (i.e. pages, blog posts and custom content share the same ID range).
EDIT 1
I would like to clarify myself. I use REST API to download pages into an HD folder. I download many at once and then split the downloaded JSON files into individual files where each file is named after the page ID.
Now I want to extend this process to blog posts and custom content and wonder if I can do it in the same folder as pages, i.e. I wonder if the page IDs can clash with blog post IDs with custom content IDs.
By "folder" you mean Confluence Folder ? or Folder on a Hard-drive ?
In the case of Confluence Folder, you cannot put Blogpost under a folder :/
In the case of HD Folder, when you are exporting the pages of BlogPosts, IDs content are not present in the generated files. The title and the export date and time will be used to name the file.
For the custom content, I think it will depend on which custom content.
Regards,
Hi, thank you for your answer. I have added clarification to my question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok thank you for the clarification :)
From my knowledge of content exporting; unfortunately for your case only built on DC and Server, there was no conflict between page and blogpost ID as they were managed in the same database table. I don't know if it is the same on the Cloud.
I made a test on my Cloud instance as follow :
1. Create a page #1
2. Create a blog post #1
3. Create a page #2
The IDs of those 3 content were growing, ID page #1 < ID blog post #1 < ID page #2
It seems to be the same in Cloud than on Premise.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Got it for the pages and blog posts. What about the custom content? In my case this would be the questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't know for the custom content :/ Sorry
You will to do the same test than the one I do with native content and your custom content.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately, I do not have permissions in our org to create a new space. Checking in the spaces I have access to will be problematic since they already have a lot of pages and blog posts and questions/answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have some example of Custom content ? Is it from private plugins or plugins from the marketplace ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is where I see it. I do not know if this comes with the Confluence Wiki or our IT has installed some kind of a Confluence plugin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes it is an additional plugin "Questions", but developed by Atlassian. It still remains as custom content.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I made a test after installing "Questions". IDs are well shared between native content and Custom content.
To grab a page you have the following URL : https://yoursite.atlassian.net/wiki/spaces/spaceKey/pages/IDpage
On custom content for example Question you have :
https://yoursite.atlassian.net/wiki/display/spaceKey/customcontent/IDquestion
And if you are using the same URL pattern to access to the question like a classic page :
https://yoursite.atlassian.net/wiki/spaces/spaceKey/customcontent/IDquestion
You will access to your question with a page rendering.
So IDs are unique amoung native contents and custom contents (at least for the content brought by the Questions app)
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Excellent, but just to make sure, because the language is a bit ambiguous,
What you have discovered is that IDs of pages do not clash with IDs of blog posts do not clash with IDs of questions.
Correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, they will not clash
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Kharitonov_ Mark check this thread and this answer from Atlassian Stuff: https://community.developer.atlassian.com/t/confluence-cloud-content-id-semantics/58085/3?u=modzelewskil
(...)
contentId
is along
in the database
(...) will have uniquecontentId
values. Content includes pages, blog posts, comments.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.