Hi David,
 
The infinite loop is almost certainly because the recursion never bottoms out.  That is most likely because the layout is calling itself again and again.  You need to put in something that will make the recursion "bottom out".  The usual practice seems to be that you use an attribute like "stoplayout", "suppresslayout" or "showlayout" to control whether the layout is shown or not.
 
Then your cfmodule call looks like this:
<cfmodule
 template="#fusebox.rootpath##request.self#"
 fuseaction="help.nav"
 urltoken="#request.urltoken#"
 showlayout="false"
>
 
Whatcha reckon?
I recommend you have a look at my Basic Portal sample app on Bjork.net.  It does exactly the kind of thing you are after. ;-)
LeeBB

 

----- Original Message -----

 

Thanks Lee/Stephen,  I took out the query string and it didn't throw the
error however it seemed to become locked in an infinite loop and never
displays anything.

In a normal situation I would just put the nav bar into the layout file
directly but this was just tinkering to try and see when I might need to
use cfmodule but it seems to be more trouble than it is worth for the sort
of projects I am currently working on.

Thanks anyway.

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