"Absolute links" vesus "Relative links"
| Project: | Path Filter |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
thank you for this nice module, but please change the wording in the module help text. i'm realy confused and have done a code review to understand what you are writing about. The text in the module is wrong and it looks to me like a missunderstanding between relative and absolute paths.
Absolute Path:
This is a path that can be the FULL Path with domain name and directory('s) e.g. http://www.example.com/node/12 or a absolute path - relative to the webserver root /node/12. But the last is not a relative path - it's a absolute path, while it brings you back to the webservers root, wherever deep you are in a directory structure!
Relative Path:
This is a path notation relative to the *current* directory. For e.g. the current file you are is loading has the URL http://www.example.com/subdir/abc/index.php and you like to create a relative link inside this HTML Code to http://www.example.com/otherdir/def/index.php then you create a relative path named "../../otherdir/def/index.php". Other relaive path examples: "node/12", "../img/test.gif", etc.
One Article as a references:
http://webdesign.about.com/od/beginningtutorials/a/aa040502a.htm
#1
For your module you should distinguish between:
1. absolute URL (http://www.example.com/node/12)
2. absolut Path (/node/12)
3. relative Paths (../../node/12) something you don't have/create
#2
This doesnt sound like a "bug"... is the (good) point that the documentation needs to be clearer, or that some code changes would improve the module? Or s something actually malfunctioning? Setting it as a task for now.
#3
more an explanation/documentation thing...
#4
The documentation has been updated in the D6 branch... needs backporting.
#5
Backported to D5
#6
Automatically closed -- issue fixed for 2 weeks with no activity.
#7
Hi,
that is a very interesting task. Further step... if you have a multilanguage webpage. Authomatic setting for languages allow you to have two (or more...) frontpage roots: www.example.com/en/, www.example.com/it/
Then you can set correctly all the multilanguage menus and pages related correctly (see http://drupal.org/node/275705 that is a very clear tutorial about this topic).
Now, my problem is...
When I go to en/ "home" page and click on a link (an absolute path: That's my page!) I can correcly go there: www.example.com/en/page
If I switch on that page translation I correctly go on there (www.example.com/it/pagina ). BUT, if I go from www.example.com/en/home to my page (remember: absolute path), I find myself... in www.example.com/it/pagina ! :-(
Can someone help me?
Thanks
#8
I'm not sure I understand your issue, but I don't think it is linked to this old ticket. Please open a new ticket and try and describe your problem a little more.