Confluence page data erased when a new version is published

Comments

6 comments

  • Avatar
    Nils Bier

    Hi Lakshmi,

    Thanks for reaching out and your interest in Scroll Versions.
    It would be great if you could provide some further details about the steps your developer did.

    In which space did he edit the page? Are you publishing to a new (existing space), or within the same space? Is your developer working in a dedicated version?

    Please make sure to always apply changes in a specific version in your authoring space (the one you've activated Scroll Versions in) - you should not make any changes in target spaces (the space(s) you publish to with Scroll Versions). Otherwise the changes will be overwritten every time you re-publish a specific version to an existing space.

    Does that help? Please let me know if you have any further questions.

    Best,
    Nils

    0
    Comment actions Permalink
  • Avatar
    SUBRAMANIAN Packialakshmi (Edited )

    Nils Bier,

    Please see the Developer's Comments from the below:

    "Document- Aircraft to GCMS RPS ICD LV33-151218 in Confluence has a number of overlapping issues that need to be resolved as quickly as possible. I suspect the issues derive from the recent versioning functionality. There’s a serious disconnect between the Page History versioning and Scroll Versions.

    Within the Interface Control Documents space, the left-hand margin’s PAGE TREE listing for this ICD is now linked to a Scroll Version. This ICD page is different from the original in that it contains a ‘.’ preceding the doc’s title in the URL (.LV33-151218). My original page for this ICD contains NO ‘.’ and is no longer the destination from the PAGE TREE listing. We need to re-direct the PAGE TREE listing for this ICD to my non-Scroll Version page if possible.

    Viewing the Scroll Versions of this ICD (.LV33~), its Page History (Tools\ Page History) is missing my original edits. The original ICD (LV33~) contains 92 versions plus a version 93 marked as CURRENT. Version 93 is marked as a Scroll Version 1.2 and is missing my edits from the last two plus months. Version 92 contains the most recent edits, and I can restore it as the CURRENT version (which may also answer the re-direct note in the bullet point above).

    Let’s start with these two issues. Scroll Versions hasn’t yet been ‘rolled out’ with official direction, so I’m not using it to apply changes to my ICDs. Before rolling out this new functionality, we really need to understand how it impacts our current doc set, then develop a process and kick-off date"

    Developer is trying to publish within the same space (called ICD space) and working on dedicated version.

    I hope the detailed information gives you an idea.
    Can you please suggest me on this?

    Thanks,
    Lakshmi

    0
    Comment actions Permalink
  • Avatar
    Nils Bier

    Hi Lakshmi,

    Thanks for the further details.

    Scroll Versions saves every versioned page in the described pattern (."Pagetitle" v"Versionname") - see https://help.k15t.com/scroll-versions/latest/glossary-112919376.html#id-.Glossaryv3.1-Dot-pages.
    Those pages are not displayed in the page tree, as we're filtering them out, depending on which version is selected (if v1 is selected in the version picker, all pages in v1 are displayed, if v2 is selected, all v2 pages are displayed).

    Do you know how your developer accesses the page he's referring to? Is he browsing there with a bookmark, or any other external link?
    With Scroll Versions it's important to always work on the versioned pages using the page tree to browse to those pages, as otherwise content changes might get lost when you publish a version.

    To solve the problem you'd need to copy the content from your page history to the versioned page (the one with the ".") and continue to work in this versions context in order to not loose any content in future publishs.

    I hope that information helps. If you have further questions, please feel free to open a support request by emailing to support@k15t.com. We can then discuss your problems in a more privately (e.g. if we would need to have a space export to further investigate), or set up a web session to discuss your use case and requirements. We can also add your developer to this ticket, so he can directly update the status of this ticket.

    Best,
    Nils

    0
    Comment actions Permalink
  • Avatar
    SUBRAMANIAN Packialakshmi (Edited )

    Nils,

    Thank you for the response and answer. I understood the concept of Page Tree now.

    1) Still the meaning of "To solve the problem you'd need to copy the content from your page history to the versioned page (the one with the ".") and continue to work in this versions context in order to not loose any content in future publish" is unclear to me.

    2) What would happen if I delete scroll version and comala workflow from the space? how to delete scroll version from the page?- Can we remove the versioning functionality from the site without losing any data?

    3) confluence page should be in an approved state before publishing the version within the space ? (if comala workflow is integrated into Scroll version).

    Thanks,

    Lakshmi

     

     

     

     

     

     

     

     

     

     

     

     

    0
    Comment actions Permalink
  • Avatar
    Nils Bier

    Hi Lakshmi,

    With "To solve the problem you'd need to copy the content from your page history to the versioned page (the one with the ".") I meant that you would need to manually revert the page to the page revision you'd need to keep and then copy (with copy+paste) the content to a page that is managed with Scroll Versions, in order to not loose any content when doing a re-publish.

    I can't speak for Comala, but for Scroll Versions we recommend to first create a space backup, then unversion all pages, to not have any pages in a version (you can get an overview on all versioned pages in the "Content in Version" report available in the Scroll Versions Menu) and then delete all versions in the space.
    Once the last version is deleted, Scroll Versions is deactivated for this space and you can de-install it. Please have a look at the following page for further information: https://help.k15t.com/scroll-versions/latest/delete-version-113443056.html

    If you mark the checkbox "Only complete pages", only pages in the final Comala Workflow state will be published, see https://help.k15t.com/scroll-versions/latest/compatibility-with-comala-workflows-115869512.html and https://help.k15t.com/scroll-versions/latest/publish-a-version-110528291.html.

    Does that information helps? Of course we can also set up a web session if you have any further questions. Please reach out to support@k15t.com, to discuss further details.

    Best,
    Nils

    0
    Comment actions Permalink
  • Avatar
    SUBRAMANIAN Packialakshmi

    Thank you Nils. I raised support ticket for this issue.

     

     

     

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk