Link to another space with version, variant and language

Comments

11 comments

  • Avatar
    Nils Bier

    Hi Barry,

    Thanks for reaching out.
    You're correct, this information is currently stored in the user context. You can already link to a specific language by adding the language parameter to the URL (see https://www.k15t.com/display/TRSL/Linking+to+a+translated+page+from+outside+confluence). Furthermore we have an open improvement request to be able to link to specific variants as well (see https://k15t.jira.com/browse/VSN-912).
    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.

    What you can do already is to publish your content in the wanted version, variant and language to a specific space. This space then has its own URL and contains only the information you selected on publish (e.g. version 1, variant A, language EN). You can then do the same with another combination and would therefore end up with specific links to a specific "set" of information.

    Would that help?

    Best,
    Nils

  • Avatar
    Barry Preston

    Hi Nils,

    Thanks for the response - I will certainly consider the Version/Variant/Language specific spaces.

    One question - you note that languages can be passed as a part of the URL, and that a similar ability for variant is in process. However you don't mention version? Can this currently be embedded in the URL, is there an improvement request outstanding for it or is it not planned?

    Regards,

    Barry

  • Avatar
    Nils Bier

    Hi Barry,

    For versions this is theoretically already possible, as each versioned page is saved as specific Confluence page (with its own URL, see https://help.k15t.com/scroll-versions/latest/glossary-112919376.html#id-.Glossaryv3.1-Dot-pages), however we do not recommend to link to those pages directly (without using the "Browse link" functionality in Scroll Versions, see https://help.k15t.com/scroll-versions/latest/link-to-pages-in-a-versioned-space-110528244.html), as those links might break if you publish a space (as the linked pages can't be accessed by your readers theoretically).

    Does that help?

    Best,
    Nils

  • Avatar
    Roland Wiesinger

    Hi,

    we are currently testing the Scroll Versions Add On and we are facing similar issues.

    We have a seperate space for each System (eg System A, System B, System C) and these interact with each other.
    Each system has different versions (1, 2, 3) where 1 is the currently published version and 2 and 3 are future versions, that are being edited.

    When I link from System A - Version 2 to System B, the link dynamically changes depending what version I edited the last time in System B.

    So let's say I edit a page in System B Version 3, the link from System A Version 2 points to System B in Version 3.
    And if I occasionally switch to System B Version 1, then the link from System A Version 2 points to System B in Version 1.

    This is essentially making the use of versions via different spaces useless.
    Is there any way to work around this?

    Thanks
    Roland

  • Avatar
    Nils Bier (Edited )

    Hi Roland,

    Thanks for reaching out.

    How do you plan to make the information available? If you're linking between multiple spaces with different versions, your readers need to have access to all those spaces (and versions), as the links will not work otherwise.

    It would be great if you could further describe your setup and use case (please feel free to open a private support ticket by emailing to support@k15t.com).

    Best,
    Nils

  • Avatar
    Christian Sprenger

    I reckon we have the same problem, or at least very similar.

     

    We use Space 1, Space 2 and Space 3 for documentation where on Space 4 we set it together to Documents, means we have on Space 4 includes from pages of Spaces 1-3.

    Now, when I am on Space 1 on a Page with Version 1 and I opened on Space 2 a Page with Version 2 it will do me a document with the documentation of

    * Space 1 Version 1
    * Space 2 Version 2

    whereas my document on Space 4 is selected Version 2

    IMHO there should be a *Global Version* which is the same on all Spaces (where I enable that).
    When I'm now on Space 4 in a document Version 3 it will show (and most important: Export (another issue: Advanced Export!)) me a document with Includes of Space 1 Version 3, Space 2 Version 3 etc.

  • Avatar
    Nils Bier

    Hi Christian,

    Thanks for the insights - with one of the next versions we'll start working on content reuse and with this also improve the functionality of our Scroll Includeplus macro (see https://k15t.jira.com/browse/VSN-766- 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.) to allow reuse from other spaces. A current idea how to implement this, is to allow to define specific versions of other versioned spaces, to be included (e.g. from space A, v1.0 always include v2.0 from space B, which should meet exactly your requirements, if I understood you correctly.

    Cheers,
    Nils

  • Avatar
    Christian Sprenger (Edited )

    Hello Nils,

    thank you very much for your repsonse, highly appreciated!

    In the meantime I sent a mail to support in addition.

     

    The "Problem" is: I don't want to specify a LInk to a certain version, it should always take the version which has been selected, regardless in which Space I am.

    Because the Document does not change often, it's mostly the content (the "Includes" from other Spaces) which changes, so I don't want to redo all Documents to adjust the Link.

     

    *Edit* 

    And we have the Confluce-"Include" in our documents, so it would be loads of effort to change all our documents to your Include+

    As well that we cannot use the "_Include"-Page-thing, details mentioned in my mail

  • Avatar
    Nils Bier

    Hi Christian,

    Speaking about include vs includeplus, as stated in the comment here: https://help.k15t.com/scroll-versions/latest/intro-to-content-re-use-117903896.html :

    Once Scroll Versions is activated in a space, you should use the includeplus macro instead of the normal include macro, however there's no "migration task" that automatically rewrites all existing include macros to includeplus macros. This task is done lazy: once you edit a page with an include macro, this macro will be transformed into a includeplus macro.
    If you have a page with a normal include macro including a versioned page, Scroll Versions will take care that the right version of the included page will be displayed.

    That said, after you activate Scroll Versions, there's nothing you need to change manually on existing pages.

    Let's further discuss your requirements in the support ticket you've created.

    Cheers,
    Nils

  • Avatar
    Christian Sprenger

    Dears,

    is there an update when the Scrolls support connecting Spaces?

    After the last update we have a problem with include (not include+. I know, we'd use include+ but currently we can not because the content to be included is on a different space), where I hope it can be solved with your plugins.

    Thanks for checking and updating the post :)

    BR
    Christian

  • Avatar
    Roman Serazhiev

    Hi Christian.

    We are working on Connected Spaces feature right now. This is on our roadmap as the next big feature of Scroll Versions. There is not exact date for now, but we are aiming to release it this Spring.

    Cheers,
    Roman.

Please sign in to leave a comment.

Powered by Zendesk