Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Linking to attachments applies its version to the URL

When linking to an attachment that is stored within a different page, the URL that is generated contains the version number of the current highest version. If there are made new versions of the file, the previously created link (absolute url) will still link to the old version.

Example of current behaviour, using the "Insert Link" screen:


If instead the link mechanism would use the relative url to the attachment, it wouldn't matter how many versions there are. It would always open the most recent one.

An intermediate workaround is to copy the relative url to the attachment from the Attachments page (right-click and "Copy Link Address"). This will always point to the most recent version.

Example of wanted behaviour:


There should never be absolute paths used for versions of attachments, as you will easily download an outdated version of it.

Is it possible to configure this somehow, or are we stuck with the workaround?

1 answer

1 accepted

0 votes
Answer accepted

While it does look like it is pointing to a specific version that link is generated dynamically each time you load the page. If you look at the storage format it should look something like this ...

	<ri:attachment ri:filename="Attachment.pdf">
		<ri:page ri:content-title="Other Page"/>

As you can see the storage format doesn't point to a specific version. When the page renders it will create the url on the fly and point it to the latest version. If you update the attachment you should see the url change. If it is not changing then probably the link is not set up correctly in the storage format and is pointed directly to a specific URL like this ...

<a href="http://wiki/download/attachments/???/Attachment.pdf?version=3&amp;modificationDate=1376425249443&amp;api=v2">Stuff</a>

This would happen if you select "Web link" when you are creating the link. But if you use "Search" instead then it should be created correctly.

I have tested this out and it is truly linking to old versions of the document and not the newest version. I 'd like to provide a link that always goes to the newest version and not to that snapshot in time version.

The features that made Confluence a nice tool are gone in the Cloud version! The Cloud version is not useful to me so I will not use it and I would highly recommend everyone to double check before moving to it.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

Confluence Mythbusters: Does Atlassian even use Confluence?

Hi, Confluence collaborators! As part of #Confluence-Collaboratory month, we’ve created a very special Mythsbusters segment, where we're dive into an interesting myth and uncover the truth behind i...

1,399 views 7 29
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you