Creating relative links in Quickr (Domino)

Sometimes you may need to create a link to an internal page or document within a Quickr place. Although you can easily do this by using the smarticon of the rich text editor, these links contain the full qualified hostname, port and placename.

So these links will fail if one of these parameters will change. It will fail e.g. if you use a place as the master of a placetype. In all newly created places such links will still point to the original place and will no longer work.

[More:]

Although there I currently no easy way to create relative links within Quickr (Domino) there is a workaround, which might work at least for some of the use cases:

Assume you have a URL which links to a document which looks like this:

http://server.domain.com/LotusQuickr/placename/Main.nsf/h_Toc/
7CB1ED9DCD9FCEAB852567C3006E2DBE/?OpenDocument

To make this a relative link you can change this to the following URL:

../../h_Toc/7CB1ED9DCD9FCEAB852567C3006E2DBE/?OpenDocument

In case you have a link pointing to a sub-room like

http://server.domain.com/LotusQuickr/placename/PageLibraryC12574DB0041B263.nsf/
h_Toc/CE6A3D6B1F546C9405256708001671FF/?OpenDocument

you should change it to

../../../PageLibraryC12574DB0041B263.nsf/
h_Toc/CE6A3D6B1F546C9405256708001671FF/?OpenDocument

This will work as the name of the pagelibrary will not change if you create a new place.

So now as we know how to build the correct URL we can use this whenever we create a link to an internal page.

But there are still three things to keep in mind:

1. These relative links cannot be used with the smarticon in the rich text editor as they will automatically converted to full links. Instead you have to use the HTML view in the editor and manually insert the relative URL to the text.

2. Whenever you edit such a document the links automtically will be converted to full links again and need to be edited afterwards.

3. I did not find a solution yet to use link pages with relative links as they will automatically set “http://” before the relative URL which makes it unusable. So if anybody has a solution for that …

So to summarize: This is a workaround which might work for some use cases but not for all. There is an enhancement request created to address this in a future release.