Link to the anchor

Follow

Pavel

October 25, 2018 11:49

Hi k15t!

We have space with versions (e.g. 03.46, 03.47 and 03.48)
1. In ver. 03.46 I create page with anchor and link to the anchor.

Storage Format:

<p><ac:link ac:anchor="TEST_ANCHOR"><ac:plain-text-link-body><![CDATA[Link to the anchor]]></ac:plain-text-link-body></ac:link>.</p>
<p><br /></p>
<p><ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="4976cf4b-742d-4adc-9a3b-ec821bd7e37a"><ac:parameter ac:name="">TEST_ANCHOR</ac:parameter></ac:structured-macro></p>
<p><br /></p>

2. Change ver. to 03.47. And edit page. Link will be changed automatically by Scroll Versions. Prefix will be added to the page name with Confluence title

Storage Format:

<p><ac:link ac:anchor="TEST_ANCHOR"><ri:content-entity ri:content-id="216629632" /><ac:plain-text-link-body><![CDATA[Link to the anchor]]></ac:plain-text-link-body></ac:link>.</p>
<p><br /></p>
<p><ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="4976cf4b-742d-4adc-9a3b-ec821bd7e37a"><ac:parameter ac:name="">TEST_ANCHOR</ac:parameter></ac:structured-macro></p>
<p><br /></p>

Tag added <ri:content-entity ri:content-id="216629623" />

This is bug!!!

Why? Cases^

1. If I copy the page with ver. to 03.47, the link will not be on the current page, but on another page (source).

2. If I make Scroll Versions Dropdown > Reschedule, 03.47 -> 03.46, will be a broken link:

0

• 

  Roman Serazhiev October 29, 2018 12:29

  Hi Pavel,

  with the way Scroll Versions is implemented currently, it's not technically easy to implement the ability to link to an anchor and be sure that links are working after the space was published. We have a feature request to have a better support for anchor links in versioned spaces: https://k15t.jira.com/browse/VSN-2080. Sign up for an account in our Jira to watch and vote for this issue.

  There are, however, a few workarounds I can propose. You could try linking to an anchor using the Advanced tab. You would have to provide the page title the way it would be in the published space. For example, I know that the link should point to Page A and anchor "anchor". I would edit the link on the versioned page in the master space and insert this text in Advanced tab of the linking dialogue: Page A#anchor. Like this:
  
  With the way Scroll Versions is implemented currently, it's not technically easy to implement the ability to link to an anchor and be sure that links are working across versions. 
  
  The workaround above would help when you publish to new or existing spaces. That way anchor links will point to the published page. The downside is that they won’t work in versioned (master) space. But at least your end-users who only get access to published content could use them. Do you publish the documentation to other spaces?

  Roman.

  0

  Comment actions Permalink
• 

  Pavel October 30, 2018 09:45

  Hi Roman!

  You ask: Do you publish the documentation to other spaces?

  Nо. We do not use publication to other spaces. We use

  DEACTIVATE THE PUBLIC VIEW

  https://help.k15t.com/scroll-versions/latest/deactivate-the-public-view-140542515.html

   

  0

  Comment actions Permalink
• 

  Roman Serazhiev October 31, 2018 09:22

  Pavel,

  if you don’t use publishing functionality at all (this is how I understand it), then there is no workaround I can offer. You would need to wait for https://k15t.jira.com/browse/VSN-2080.

  Roman.

  0

  Comment actions Permalink

Please sign in to leave a comment.