Header Links Limitation in Frameless: URL only works on same level

Exactly what Amebr says: If you have a relative URL, that relative URL like Features.htm in the sample project only works on one level. As soon as you have other levels of books, logically as a topic in your Book has a URL = PROJECT/BOOK NAME/file.... the relative path "Features.htm" makes a URL PROJECT/BOOK NAME/Features.htm and therefore cannot find it because Features.htm is at PROJECT/Features.htm.

So the limitation is that you should be able to point to a file and it works out the relative URL once built... otherwise, it can't work with a relative URL. 

In my case, I can use an absolute path, so, issue is solved for me... but it's true that this causes problems for systems that would be delivered to customer servers where you can't predict an absolute path.

The other solution is redirect I did this and it worked:

Features.htm

Index.htm

Book 1/ topic1.htm

Book 1/topic 2.htm

Book 1/Features.htm (empty redirect to ../Features.htm)

Book 2/topic3.htm

Book 2/Features.htm (empty redirect to ../Features.htm)

but those empty redirect htms would need to be added in all levels of books and after build. So, it's a faff.

Currently I have it just as a starter so only in my file structure. on C drive... The final project will be published only internally.  Do absolute paths work in that field? if so, I can easily just have it read what the absolute path would be once it's up... that would certainly be no problem. I will test absolute path now.

How do you enter a relative path in this case? This is what I meant about me maybe missing something. The relativity is different whether you are on a Topic page within a book or in a page at root say with the following:

Index.htm

Features.htm

About.htm

Book 1

> topic1.htm

Book 2

> topic2.htm

If I want the header link to point to features.htm, it does so from About.htm with just Features.htm

if I want to point to it from topic1.htm, I need the link to go up one folder and then point to Features.htm.

For this case therefore it's different to About.htm as it's ../Features.htm.

I tried this:

And so if I'm in a topic one folder down from the "root" where Features.htm is... it's all good because it works to take the folder away:

>>>>>

That's all good... but now, if I am in "Our destinations", which isn't in a folder, so it's on the same level at Features.htm and I click features:

>>>>> the relative path is going to take a folder off and land outside of the project folder a folder up from the "root" where the index is:

And what if you have more than one level of folder within books?

I don't know much about relative paths, but the relative path is going to be different if you have different book levels and, therefore, only work in one instance... is there a way to write the relative path to be variable that I am completely unaware of?