| Re: Rationale for how modules handle relative urls? |
| by Mithrandir on 2005/3/31 16:21:13 It is because PostNuke uses the "front controller" (all pages are loaded from a file in the root folder) where XOOPS modules load individual files. When you specify a relative URL, your browser (I think) will go from the active URL when calculating the new location. I think you can get it to count from the domain root by starting the link with a forward slash / |
| Rationale for how modules handle relative urls? |
| by dmcmeans on 2005/3/31 16:17:34 I cut my teeth on PostNuke, and its modules resolve relative urls starting from the root folder of the PostNuke install. So, I was a little surprised to see that XOOPS modules do it differently -- they seem to resolve starting from the specific module's folder. So, a link like <a href="myFiles/file.txt">my File</a> in a news article, would resolve to <root folder>/modules/news/myFiles/file.txt in Xoops and to <root folder>/myFiles/file.txt in PostNuke. Is this intended behavior? Does anyone know why XOOPS handles it this way? Is there a configuration setting to change this behavior? Thanks, David |