That's a tough one - but there is a simple way around it using what I call
wrapper pages:
A wrapper page is a tiny file which takes it's name and breaks it up to get
the fuseaction and then include index.cfm.
I use them to make statistics easier so it is based on file name (the
standard way :-).
This should solve your problem as each fuse you need to have anchors in
would have a different file name.

For example a wrapper file would be:
<!--- Name: Generic Wrapper page
Description: Takes filename and based on it calls the index file with
correct language and action
Parameters: 
Local Variables:
written: 15/07/1999 NB
--->
<CFSET variables.TemplateName = GetFileFromPath(GetCurrentTemplatePath())>
<CFSET request.DisplayLanguage = listFirst(variables.TemplateName, "_")>
<CFSET attributes.FuseAction = listGetAt(variables.TemplateName, 2, "_.")>
<CFINCLUDE template="../index.cfm" >

In our case we also need language so if the name of the wrapper is
EN_Login.cfm
It's equivalent to:
Index.cfm?fuseaction=Login&DisplayLanguage=EN

Just copy the file and each time give it a new name - the name is the
functionality...

By the way I keep the templates in one subdirectory down from the index.cfm
(that's why the include has ../index.cfm)

Regards,
Noam

        ----------
        From:  JME Maxwell [SMTP:[EMAIL PROTECTED]]
        Sent:  Monday, 21 August 2000 6:34
        To:  '[EMAIL PROTECTED]'
        Subject:  RE: Anchor Problem

        Both your indexes should be in different directories.

        You can either supply a relative path or an absolute path.

        -----Original Message-----
        From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
        Sent: Monday, August 21, 2000 12:16 AM
        To: [EMAIL PROTECTED]
        Subject: Anchor Problem


        Hi Folks,

        Hopefully, there's an obvious solution that i am missing: The
problem is
        that I want to target an anchor on a page that occurs with a
different
        fuseaction.

        So for instance on page A I have a link that points to a bookmark on
page B:

        <a href="index.cfm#this_bookmark/fuseaction/this_fuseaction"">Jump
to this
        place</a>

        This would work fine except for the fact that both pages point to
        Index.cfm--therefore when I click the link nothing happens...the
browser
        thinks its already on the right page, just that the link cannot be
found.

        Any ideas for solutions?

        
----------------------------------------------------------------------------
        --
        To Unsubscribe visit
        
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
        send a message to [EMAIL PROTECTED] with
'unsubscribe' in
        the body.
        
----------------------------------------------------------------------------
--
        To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to