>You're sure that's the SPML that's generating your links? I use the >exact same code in topic.spml here.
The topic.spml file, aside from some aesthetic adjustments, is exactly the same as what came with TF Server. I've been experimenting with some additional spml code in the topic.spml file with mixed results. Here's what I've added to the exisiting code to try and elminate the problem of the directory name being added twice to the end of the URL in conferences (in a folder called "Programs") more than one level deep:
<!-- #if LOCATION CONTAINS "Program" -->
<!-- #if DIRNAME --> <a href="<!-- #echo PARENT_LOCATION -->"> Back to <!-- #echo DIRNAME --></a> <br> <!-- #else --> <a href="<!-- #echo PARENT_LOCATION -->"> Back to <!-- #echo PARENT_LOCATION --> </a> <br> <!-- #endif --><P>
<!-- #else -->
<!-- #if DIRNAME --> <a href="<!-- #echo PARENT_LOCATION --><!-- #echo DIRNAME -->/"> Back to <!-- #echo DIRNAME --> </a> <br> <!-- #else --> <a href="<!-- #echo PARENT_LOCATION -->"> Back to <!-- #echo PARENT_LOCATION --> </a> <br> <!-- #endif --><P><P>
<!-- #endif -->
(I realize there is some redundancy here). The results have been sporatic at best. The code actually solves the problem of our deeply-embeded conferences returning a working "back" link, but accessing other conferences in other folders will actually crash the server (with a type 2 error). Needless to say, I am not running this code currently. I'd like to upload a simpletext screen shot of our directory structure so that these issues might make more sense, and also possibly give you an account on our server so you can see what is happening for yourself if you think that would help. Where can I upload a file so you'll get it?
