Title: Message
That was just a typo when I wrote up the email - it was the attributes.fuseaction vs fusebox.fuseaction issue (did I just admit to that?) :)
-----Original Message-----
From: Kathryn [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 13 June 2002 11:50 PM
To: [EMAIL PROTECTED]
Subject: RE: nested circuits problem

is it event/eventURL or events/eventURL?

Your post referred to both

Kathryn Butterly
Web Developer
Washington Mutual Finance
813 632-4490
[EMAIL PROTECTED]


-----Original Message-----
From: Kay Smoljak [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 13, 2002 9:45 AM
To: [EMAIL PROTECTED]
Subject: nested circuits problem


Here's a strange problem - I've done this a thousand times (OK, maybe
that's an exaggeration) and it's always worked before.

I have a circuit defined in fbx_circuits as eventURL =
"home/event/eventURL". I have a full switch file in there, but when I
call anything in that circuit (ie "index.cfm/fuseaction/eventURL.list")
it *always* displays the default case (which outputs a dump of the
fusebox structure at the moment).

I can't understand it, there *is* a "list" case, as well as whole heap
of others yet no matter what I call they always display the default
case. The dump of the fusebox structure in the default case tells me the
following:
CIRCUIT eventURL
CURRENTPATH events/eventURL/ 
FUSEACTION list 
HOMECIRCUIT HOME 
ISCUSTOMTAG FALSE 
ISHOMECIRCUIT FALSE 
ISTARGETCIRCUIT TRUE 
ROOTPATH ../../ 
SUPPRESSERRORS true 
TARGETCIRCUIT eventURL 
THISCIRCUIT eventURL 
THISLAYOUTPATH

...as well as my entire circuits structure, which all semms normal
(includes "EVENTURL home/events/eventURL").

So can anyone see anything stupid that i've done, or think of anything
that might cause this?

Argh,
Kay.

==^================================================================
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]

T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================

Reply via email to