"Convert to versioned page" for all pages of a space?
Is it possible to add all pages of a space to versioning as via "Convert to versioned page"?
I do create a space by a space creator plugin and want to have all pages versioned after activating Scroll Versions for that space.
-
Hi Ralf,
This is currently not possible, per default all existing pages are unversioned if you activate Scroll Versions. Then over time, as you keep working on them you version the pages and change the content in a specific version.
We have an improvement in our JIRA system to allow bulk versioning of pages: https://k15t.jira.com/browse/VSN-2853
Please sign up at https://k15t.jira.com/secure/Signup!default.jspa to watch, comment on or vote for this issue. We'll then send a notification for every status update.The issue description also describes a workaround to import pages into a specific target version, maybe this might be an option for you?
Best,
Nils -
Hello Team, hello Nils,
I have a problem executing the workaround mentioned above:
- Used the guide to create a string to import the whole set of versioned and unversioned pages from the master space into a versioned space so I get a complete space with versioned pages (v5, in this case).
Used this string: http://helpdev.semantic-web.at/rest/scroll-versions/1.0/content-import/pages-to-version?sourceConfluencePageId=8258527&targetConfluencePageId=9543979&targetVersionName=5 - Entering the string, the process runs for while. Then an error occurs, like this:
The space 'PMIST' is already locked for publishing / importing. Please try again later. - Our admin with elevated permissions also just received this error message in between, process was still running apparently:
2017-07-27 14:10:51,376 ERROR [scheduler_Worker-9] [apache.pdfbox.filter.FlateFilter] decode FlateFilter: stop reading corrupt stream due to a DataFormatException
Therefore we have these questions:
- We need to know what the problem is, exactly?
- Where would an admin look for the special errors or messages in regard to this procedure?
Thanks!
BR
Nina - Used the guide to create a string to import the whole set of versioned and unversioned pages from the master space into a versioned space so I get a complete space with versioned pages (v5, in this case).
-
Hi Nina,
1. How many pages did you try to versioned?
2. To further analyze the problem it would be great if you could send us a Support ZIP to support@k15t.com. To create a support ZIP, please follow these instructions.
3. Has the process now finished? Can you see all those pages you were trying to import versioned?Cheers,
Roman. -
Hello Roman,
thanks for answering so quickly:
- Actually, the process doesn't finish as such, it stops in the middle with that error message I quoted: The space 'PMIST' is already locked for publishing / importing. Please try again later.
- So actually about one third of all pages becomes imported and versioned. Not all of them.
- We'll send you the zip file asap.
BR
Nina -
Bulk versioning of pages would be paramount to our intended use of Confluence and Scroll Versions. We are building a solution where pages are generated from our software source code. A new version bump would have to occur for all pages (even if they didn't change), synchronised with a new release of our software.
Without bulk versioning functionality we would have to resort to simply creating a new space for every software release, which gets messy at best and unmaintainable chaos at worst.
Unfortunately I do not have the required permissions to comment or vote on the JIRA issue linked by Nils earlier. Also, the workaround described by Nina, working or not, is unacceptable for us.
Please sign in to leave a comment.
Comments
5 comments