- Conditional Content and Variants
- Workflows and Publishing
- Advanced Content and Help
- Perform and Log Scroll Health Checks
- Restrict Scroll Versions activation by space
- Improve Page Tree Performance in Large Versioned Spaces
- Compatibility with Themes
- Security Advisories
- Minimum System Requirements
- Update Scroll Versions
- Get Scroll meta information
- Can I publish only specific pages?
- Can I use variables?
- Collaborative editing: how should I work with the editor's draft and publish functions?
- How can I bulk change the version of multiple pages?
- How can I change the versions of existing pages?
- How can I downgrade to a previous version of Scroll Versions?
- How can I lock version editing after publish?
- How can I make the Scroll Content Management Bar scrollable?
- How can I manage variant attributes for pages using REST
- How do I deactivate Scroll Versions in a space?
- How do I restrict searches to a specific version?
- How to change the number of available threads
- How to export a version with Scroll Exporters
- How to work with unversioned pages
- Why do I still see Scroll Versions UI elements after uninstalling the app
- What's the difference between Permalinks and Page Keys?
- Why am I getting a notification that "the task Publishing.Preview is currently queued"?
- Why are there pages grayed out in the page tree?
- Why are two pages created when converting an unversioned pages to a versioned page?
- Why does Page Property macro render an error?
- Why do I get the error "Page X will be restricted for Edit if Scroll Versions groups are removed in the target space and cannot be overwritten by the current user" when publishing a space?
- Why do I get the warning "Page XY contains a link to a page YX that cannot be published" when publishing a space?
- Why is a certain macro or app not working in versioned spaces?
- Why versioned pages are shown in the page tree?
- Limitations of use with Confluence 6
- Define Scroll Versions user settings
- Behavior of Inline Comments
- Delete a page and its descendants
- Fix the Macro Rendering Error
- 'Error Loading Children' is displayed in the page tree instead of the child pages
- Disable Scroll Versions Onboarding Notifications
- Importing Content to a Target Version
- Assigning renderable addresses to pages with unrenderable page titles
- Removing unversioned pages
- Split versioned spaces
- Disable the automatic flushing of the index queue at the end of a publish job
- Create a global multi-language glossary
- A banner appears in my spaces regarding the Dark Feature
- Solving the error "Change name 'PAGENAME' must match page naming pattern"
- How to unlock a space?
- Deactivate the Public View
- Reporting on spaces that use Scroll Versions or Translations functionality
- Switching off Scroll Versions or Scroll Translations functionality
How can I bulk change the version of multiple pages?
Scroll Versions does not officially support bulk version changing (although we do currently have an open request for this feature).
We actually do not recommend bulk changing the version of multiple pages, as in most scenarios, a combination of unversioned pages and fallback pages works perfectly well.
Let's quickly explore how versioning works and how why unversioned pages are fine in most cases:
Pages becomes versioned either when they are first edited in a version, or when converted to a versioned page using the Scroll Versions dropdown. For example, if a page has not been changed from version 1.0 to 3.0, but is then changed in 4.0, then versions 1.0, 2.0, and 3.0 will point to the same page (version 1.0) and version 4.0 will be created on a new page. There is no need to create additional pages for versions 2.0 and 3.0, as the content is the exact same as it is for version 1.0.
That is why Scroll Versions also uses the concept of a fallback (pages in later versions being the same as the page as an earlier version it has not been changed, for a full explanation see the term 'fallback' in the glossary), to not duplicate the content unless it is required. This is important in larger spaces, as creating new versions of hundreds of pages with the same content would be extremely inefficient.
How to execute a bulk change
However, if you still want to execute a bulk version change, you can do so by importing multiple existing Confluence pages to a target version.