I'm actually using the "#request.self#?fuseaction=#xfa.something#" notation, i was just writing it in short hand by typing "..../index.cfm". That was confusing on my part, sorry.
I have looked into the problem a little more, and here is what i have found. It seems that QuerySim, or any custom tag that uses thistag.generatedcontent, will work fine if it's in a fuse included through fbx_switch.cfm, in any circuit. However, I have one template using QuerySim that i include through fbx_settings.cfm. I have found that, when included through fbx_settings.cfm, thistag.generatedcontent turns up empty, for ANY custom tag i try to use. I also found that this happens in ANY circuit. -----Original Message----- Date: Sat, 25 May 2002 13:30:35 -0400 From: "Hal Helms" <[EMAIL PROTECTED]> Subject: RE: QuerySim custom tag and Fusebox 3 Message-ID: <000101c20411$e157ad90$c0d45c42@BigHal> I use it in child circuits all the time without a problem. On a possibly related note, I'm wondering why are you using ../ notation to get back to the home circuit? -----Original Message----- From: heirophant mm [mailto:[EMAIL PROTECTED]] Sent: Saturday, May 25, 2002 1:02 PM To: CF-Talk Subject: QuerySim custom tag and Fusebox 3 Hi everyone, I'm using the QuerySim custom tag (find it at www.halhelms.com) to assist in developing a Fusebox 3 site. When I use it in a template that I am viewing directly rather than through the Fusebox ( as in "..../index.cfm?fuseaction=circuit.fuse"), it works fine. Also, QuerySim works fine when calling it through the Fusebox, if it is in the home circuit. However, when QuerySim is called in a template used by a child circuit, something wierd happens. I have found that the value of thistag.generatedcontent, which would hold the query contents i pass, is wiped out. Therefore, QuerySim has nothing to make a query out of. I know that the proper place to be using QuerySim is when you're testing individual fuses, especially before you have the "real" query fuses written, so you can say that i'm using QuerySim improperly anyway by using it within the fusebox itself. (in my defense, i have an acceptable reason to be doing this in this case and its only temporary, but i wont try to explain). Anyway, I thought it was strange that the value thistag.generatedcontent of a custom tag would be wiped out in that way. I have thoroughly tested this and found that, indeed, it only happens when calling it within the Fusebox, and only in a child circuit. I am afraid that this reveals some sort of subtle problem with Fusebox itself! But I am probably (and hopefully) wrong... Mike Mertsock Alfred University Web Team ________________________________________________________ Outgrown your current e-mail service? Get a 25MB Inbox, POP3 Access, No Ads and No Taglines with LYCOS MAIL PLUS. http://login.mail.lycos.com/brandPage.shtml?pageId=plus FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
