-----Original Message----- From: Jason Spisak [mailto:jason@mtear.com]
I commented out that line, and it still has the backslash in front of the catalogued url.
Michel, is that right?
Aren't they supposed to not have the leading slash? If it has a leading slash, then when you click on the link in the Catalog management interface, you get and error. (it is looking for a server @ http://my_object/url/object, rather that http://localhost:8080/my_object/url/object.
Which one is correct in in your design?
The latter, obviously. Not putting the slash in confuses your browser into thinking it's a bad relative URL. The culprit is in lib/python/Products/catalogView.dtml Here is the checkin message: ---------------------------- revision 1.10 date: 1999/12/28 23:59:10; author: amos; state: Exp; lines: +1 -1 Fixed links to catalogged objects. ---------------------------- Here is the diff: *** /tmp/catalogView.dtml.~1.9~1NAywY Tue Jan 11 11:24:02 2000 --- /tmp/catalogView.dtml1NA_6e Tue Jan 11 11:24:02 2000 *************** *** 48,54 **** </TD> <td valign="top"><dtml-var meta_type></td> <td valign="top" align="left"> ! <a href="/<dtml-var "getpath(data_record_id_)">/manage_workspace"><dtml-var "getpath(data_record_id_)"> <dtml-if title> (<dtml-var title>)</dtml-if></a> </td> </tr> --- 48,54 ---- </TD> <td valign="top"><dtml-var meta_type></td> <td valign="top" align="left"> ! <a href="<dtml-var "getpath(data_record_id_)">/manage_workspace"><dtml-var "getpath(data_record_id_)"> <dtml-if title> (<dtml-var title>)</dtml-if></a> </td> </tr> As you can see what probably happened was that not slash before the <dtml-var getpath...> probably broke the catalog's ability to show good links in certain circumstances, which fixed one problem but manifested yours. The quick fix is to remove the / in the <a> tag in this file. But we MUST think more about this path stuff, Catalog was the first app to use it extensivly and our lack of a path framework shows. -Michel