Title: Message
Terry,
 
in FB3 you cannot define circuits in any direction but down. You could define an app at the level one up from the three you are referring to and then control who gets into which app using Security. This isn't half-bad idea at all, really.  Esp for your Admin app, is it truly any different from the others other than just restrciting who can access it? (so it's a matter of permissions not of function)
 
defining a circuit that is upward of the root circuit is something you can do with Techspedition core file , release 20; it's a two line piece of code that will fix what you want and run the rest of your code the same as the official core file. But you should think a bit before committing into what is a non-official core file. I'd advise it for intermediate and advanced Fuseboxers who know what they are doing, at least until it gets adopted officially.
-----Original Message-----
From: Terry Hogan [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 03, 2002 3:46 PM
To: [EMAIL PROTECTED]
Subject: RE: stand-alone circuit

I'm having problems with a similar situation.
 
I have an Admin circuit that is shared by several publications--each which is it's own application.
 
The directory structure is:
Admin
Publication1
Publication2
etc,  (all on the same level)
 
The problem seems to be in defining the circuits;
 
In Publication/fbx_Circuits.cfm, I have:
Fusebox.Circuits.pub1 = "pub1" ;
Fusebox.Circuits.admin = "../admin" ;
 
But I get an error--"I could not find admin/fbx_Switch.cfm (or one of its components such as an included fuse) in the "admin" circuit...."
 
What am I missing?
 
Thanks,
 
Terry
 
 

*********** REPLY SEPARATOR ***********

On 6/3/02 at 2:44 PM John Quarto-vonTivadar wrote:
Tom,
you can call other circuits in a few different ways:
1) you can define the circuits within the same app, and call them internally. This is the most common way
2) you can call a circuit independently using CFMODULE if it has an index.cfm, a fbx_circuits file, etc, etc -- that is if it's set up to be an indepedent app
3) you can call a circuit as CFMODULE in another app if that circuit is set up as part of that app
 
This doesn't prevent you from having the same circuit used by several different apps but how that gets structured with FB3.0 can be tricky. And you kinda have to watch out when making any changes to it since now you have to account fo rmultiple apps using teh same code (it migth or might not make more sense to just duplicate the code, but it depends on what you're doing. If the code you're sharing is something like a login circuit, then I tend to duplicate the code and put it in each app that I want to use it for -- taht way I know it that that app can't get broken by my working on another app. If it is something like a database interaction circuit for two apps that are the same except perhaps using a different language for display, then I'd prefer to leave the code in one place and to share it.
 
By the way in the version 20 of FuseQ you'd be able to share circuits wherever they are on the disk. Maybe that would be useful for you to put, say, all your QRY files in a circuit outside the web root for an additional layer of security or for truly common code (like that login circuit I mentioned).
-----Original Message-----
From: Tom Schreck [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 03, 2002 1:49 PM
To: [EMAIL PROTECTED]
Subject: stand-alone circuit

I have a stand-alone circuit that I would like to be able to call circuits of another application.  Is this possible?  How would I set up the fbx_Circuits file to reference circuits in a different application?

 

Thanks -

 

Tom Schreck

817-252-4900

[EMAIL PROTECTED]

 

I have not failed.  I've found 10,000 ways that won't work.

 

- Thomas Edison

 

==^================================================================
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