Actually, it's not wise to put debugging info at the beginning of FRAMESET HTML. One of the major browsers won't allow any output preceding the FRAMESET tag. You can, however, put in an HTML comment (only two dashed at each end).
Are you putting in standard headers and footers around everything via FuseBox? That will also stuff up your FRAMESET fuseaction. I suggest that you use CF_BodyContent and set a different header file for your FRAMESET fuseaction, and probably for your navigation pane fuseaction too.
To summarise the FuseBox/Frames thing: - Build your mainpane fuseaction; - Build your nav pane fuseaction; - Build your frameset fuseaction. The HTML produced should call your fusebox with mainpane and navpane fuseactions to populate the two panes; - Make sure that appropriate headers are included for each fuseaction.
Best of luck, Lee.
... | The problem is my frameset runs (I put in a debug >| > line >| > | at the top which shows), but none of my display >| > pages >| > | appear. The code for the frameset is below: .... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/fusebox@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
Fusebox
lee borkman