Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 85028 invoked from network); 27 Nov 2003 19:04:54 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 27 Nov 2003 19:04:54 -0000 Received: (qmail 29438 invoked by uid 500); 27 Nov 2003 19:04:44 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 29173 invoked by uid 500); 27 Nov 2003 19:04:42 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 29160 invoked from network); 27 Nov 2003 19:04:41 -0000 Received: from unknown (HELO sati.virbus.de) (145.253.246.81) by daedalus.apache.org with SMTP; 27 Nov 2003 19:04:41 -0000 Received: from sati.virbus.de (localhost [127.0.0.1]) by localhost (SMTP Server) with ESMTP id 77DA5166ACA for ; Thu, 27 Nov 2003 20:04:45 +0100 (MET) Received: from virbus.de (a183069.studnetz.uni-leipzig.de [139.18.183.69]) by sati.virbus.de (SMTP Server) with ESMTP id 362A3166AB1 for ; Thu, 27 Nov 2003 20:04:45 +0100 (MET) Message-ID: <3FC64AD5.8030604@virbus.de> Date: Thu, 27 Nov 2003 20:04:53 +0100 From: Joerg Heinicke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: de-de, de, en-us, en-gb, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Linotype stopped working References: <3367.1069935698@www40.gmx.net> In-Reply-To: <3367.1069935698@www40.gmx.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On 27.11.2003 13:21, Michael Gerzabek wrote: > the problem comes from flow.js line 33. If you change line 33 from > > home = root + "samples/linotype/"; > > to > > home = root + "/samples/linotype/"; > > it will work again. > > But what does this mean to flow-layer? Does sendPageAndWait(..) work > as it did before? Yes, I know that this is a possible fix, but (1) (as you say) what is with relative links/redirects and (2) I don't want to fix server errors. We could even add a more robust test: if (!root ends with /) root = root + / But this fix shouldn't be added to flow scripts, but to the input module. Where are the server specialists? :-) Joerg