Sorry for late reply - have been away.<br><br>Cant get this to work! I hope I can avoid to use an absolute URL path. What i want is, as you say, to let the server generate as much of the URL as possible. To be more spesific, the zpt whith the calling href (located in "folderA") calls a script with a construct like this:
<br><a tal:attributes="href string:folderB/scriptobject?Parameter=$variable">Text</a><br>The effect of this is that Zope generates a link to the URL <a href="http://myserver/application/folderA/folderB/scriptobject?.">
http://myserver/application/folderA/folderB/scriptobject?.</a>.. and after this link is used to call the script in folderB, the script calls a zpt in folderA again. Now, all links in this zpt gets /folderB added in their path! If you have some more tips about this, or could point me to some examples or documentation that could explain to me how this is supposed to work, it would be great!
<br><br>Regards<br>Ole<br><pre>>Instead of writing links like this::<br>><br>> <a href="folderB/object">object</a><br>><br>>write them like this::<br>><br>> <a tal:attributes="href folderB/object/absolute_url_path">object</a>
<br>><br>>I know it's more typing but it will solve all your problems. I always<br>>let the server have a part in generating URLs and I never suffer from<br>>problems like this.</pre><br>