Try it this way href="./../../00_menu_vitoria_xingu.html"
that should work. The file is in the third folder up, therefore the ./
extra on the path that points to the location itself.
Here is an explanation. about the path of the archives.
See this short excerpt of an answer in another question
If the path begins with ../
or ./
then they will be removed from the prefix:
../a/b/c
→ a/b/c
If the path begins with /./
, /../
they will be exchanged for /
/./a/b/c
→ /a/b/c
Break up with /.
, /./
, /..
will remove the /.
and /..
:
/a/b/c/..
→ /a/b/c/
and /a/b/c/.
→ /a/b/c/
Break up with /./
and /../
will remove an item:
/a/b/c/../
→ /a/b/
If /../
is in the middle will remove the prefix (similar to explanation 4):
/a/b/../c/
→ /a/c/
If ./
be in the middle will have the same behavior as explanation 2:
/a/b/./c/
→ /a/b/c/
Some extra details on Path to access html folders ,css,php etc
Of course the reading of RFC 3986 is something a little difficult, even for those who already have some experience, some of the examples made with tests, to summarize the ..
would be to move up a folder level (if not in the prefix) and the ./
would be to point out the site itself.
Credit to: Guilherme Nascimento /users/3635/guilherme-nascimento
OBS: The option with the ~ Searches the file straight from the root folder, in your case the J, I tried to find a reference of pq did not work, but unfortunately I did not find. Then disregard this rss option
Try href=". /.. /.. /00_menu_vitoria_xingu.html" or href="~/00_menu_vitoria_xingu.html" sometimes resolve...
– hugocsl
ok I’ll test! Thank you.
– dib
@hugocsl worked. Thanks! But can you explain the logic of why /.. /.. / didn’t work? . / means it should stop in the root folder is this?
– dib
dib posted more explanations in the answer to your question below. If it helped you consider mark it as accepted :)
✔
– hugocsl