Note that there are some explanatory texts on larger screens.

plurals
  1. POLinks not going back a directory?
    primarykey
    data
    text
    <p>this is probably a silly question and I have the answer myself but I want to know if I am doing anything wrong. I have a website, let's call it <code>www.mysite.com</code>. Within this site, I have some FAQs but the person that built the site saved the FAQ pages under a directory on the site named "FAQs". </p> <p>As an example an FAQ page would be located at: </p> <p><code>www.mysite.com/pages/en/faqs/faq-page1.html</code>. </p> <p>Note the <code>pages/en/</code> directory. Ideally I would like all the pages to be saved under <code>www.mysite.com/index.html</code> etc but I can't change this.</p> <p>Anyway, when I am on any of these FAQ pages, and I try to link back to say the home page <code>index.html</code> the navigation won't go to the page. So for example, when I am on:</p> <p><code>www.mysite.com/pages/en/faqs/faq-page1.html</code> </p> <p>and I try to link back to the home page </p> <p><code>www.mysite.com/pages/en/index.html</code> (which is where the index page is saved) the nav won't work. Instead it will try to go to <code>www.mysite.com/pages/en/faqs/index.html</code>. </p> <p>Now I am assuming this happens because I am in the "faq" directory, but how do I go back to the root directory when linking? The code for the link is simply <code>&lt;a href="index.html"&gt;Home&lt;/a&gt;</code>. I could of course just put in the full link <code>www.mysite.com/pages/en/index.html</code>, which would solve this but is there another way around this? Sorry for such a long post and I may have been able to explain this better but I can't :S</p> <p>Thanks in advance.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload