Received: by 10.43.9.8 with SMTP id ou8mr7660820icb.4.1349557348262;
        Sat, 06 Oct 2012 14:02:28 -0700 (PDT)
X-BeenThere: pylons-discuss@googlegroups.com
Received: by 10.50.194.196 with SMTP id hy4ls11194igc.0.canary; Sat, 06 Oct
 2012 14:02:24 -0700 (PDT)
Received: by 10.43.105.135 with SMTP id dq7mr7659386icc.3.1349557344674;
        Sat, 06 Oct 2012 14:02:24 -0700 (PDT)
Received: by 10.43.105.135 with SMTP id dq7mr7659385icc.3.1349557344663;
        Sat, 06 Oct 2012 14:02:24 -0700 (PDT)
Return-Path: <jap...@gmail.com>
Received: from mail-ob0-f175.google.com (mail-ob0-f175.google.com [209.85.214.175])
        by gmr-mx.google.com with ESMTPS id s15si664367igi.1.2012.10.06.14.02.24
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sat, 06 Oct 2012 14:02:24 -0700 (PDT)
Received-SPF: pass (google.com: domain of jap...@gmail.com designates 209.85.214.175 as permitted sender) client-ip=209.85.214.175;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jap...@gmail.com designates 209.85.214.175 as permitted sender) smtp.mail=jap...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-ob0-f175.google.com with SMTP id eq6so2916565obc.34
        for <pylons-discuss@googlegroups.com>; Sat, 06 Oct 2012 14:02:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=rJ3meV1elFlcuUV8qF4o+y8o4QS7qr192MhoP+Hy7s4=;
        b=WRHL8Rlj2SZuSy02CfovfhN93F7doReuyugh2JGS66TG5LfwDwQV3HJiG/ZpSMi3Vi
         N9fpIh9LrZQdH2Y6sWN3HMCj3NC3Y0XRDG2tFg9LCLo4gOM9ovJvLgvt+fzhYsLZ74dJ
         M145UlPvNf0wo+lJRtB5TajddpkC5du2i8OqSOPErRy8K7ZDLnq0P2Xqb4wDkbl8lNUk
         xGp1Nb7pPhqerl3RbAyVRQ4OYv5z8z3DPV3/msRM3Yav+ureKJkFaJNP9Ec6id7/M5Hh
         WPYTX5w9wwGAPq02L0TohxShjuFOqwthb4jNVO9dWT+LbdMbNZMukiasidTTI/12Qh02
         0dvA==
MIME-Version: 1.0
Received: by 10.60.29.228 with SMTP id n4mr10138077oeh.27.1349557344332; Sat,
 06 Oct 2012 14:02:24 -0700 (PDT)
Received: by 10.60.43.202 with HTTP; Sat, 6 Oct 2012 14:02:24 -0700 (PDT)
Date: Sat, 6 Oct 2012 23:02:24 +0200
Message-ID: <CAGjxhsop6cPhXaqKgfLMARDXLgwE-RBp18XeJYO56zg9FcN...@mail.gmail.com>
Subject: Velruse & Traversal
From: Jasper van den Bosch <jap...@gmail.com>
To: pylons-discuss@googlegroups.com
Content-Type: multipart/alternative; boundary=e89a8ff250ee1cebd404cb6a4e0c

--e89a8ff250ee1cebd404cb6a4e0c
Content-Type: text/plain; charset=ISO-8859-1

I use Velruse as a pyramid 'plugin', and I run into a problem when the
'login result' template (or the 'master' template it inherits from) uses
e.g.:

request.resource_url(request.root)

Since the root is then a Velruse-related object, this fails and would not
make sense anyway. But I use this a lot to create links in my application's
site-wide menu. Have any of you run into this and how would you solve it?
One option of course would be to have the 'login_complete_view' redirect to
another page, but this seems a 'workaround'.

Thanks for your thoughts,

Jasper

--e89a8ff250ee1cebd404cb6a4e0c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div><br></div><div>I use Velruse as a pyramid &#39;plugin&#39;, and I run =
into a problem when the &#39;login result&#39; template (or the &#39;master=
&#39; template it inherits from) uses e.g.:</div><div><br></div><div>reques=
t.resource_url(request.root)</div>
<div><br></div><div>Since the root is then a Velruse-related object, this f=
ails and would not make sense anyway. But I use this a lot to create links =
in my application&#39;s site-wide menu. Have any of you run into this and h=
ow would you solve it? One option of course would be to have the &#39;login=
_complete_view&#39; redirect to another page, but this seems a &#39;workaro=
und&#39;.</div>
<div><br></div><div>Thanks for your thoughts,</div><div><br></div><div>Jasp=
er</div><br clear=3D"all"><div><br></div><br>

--e89a8ff250ee1cebd404cb6a4e0c--