I suspect this isn't a FarCry issue, but a CSS issue...  It's almost
like the middle of the page is getting shoved under the header divs...
If I disable CSS it will jump to the section correctly.

*sigh*

On Oct 9, 7:48 pm, Scott Talsma <[EMAIL PROTECTED]> wrote:
> I have anchors working in FC3 on our class calendar page.  And it works
> w/both the FU plugin url as well as the objectid.
>
> http://www.echoeleven.com/index.cfm?objectid=48AFEC77-40CA-39AD-7A5DA...http://www.echoeleven.com/index.cfm?objectid=48AFEC77-40CA-39AD-7A5DA...
>
> http://www.echoeleven.com/go.cfm?path=/go/adobe-authorized-training/s...http://www.echoeleven.com/go.cfm?path=/go/adobe-authorized-training/s...
>
> In my experience, the problem is usually the HTML/browser when dealing
> w/these issues.  Unless of course CF is interpreting the # as part of
> the URL param value.  But then the database calls should be all messed
> up as well.
>
> AJ Mercer wrote:
> > Hmm, works in farcry4
> >http://myServer/index.cfm?objectid=4139E364-0A81-E6C2-873F228377FEAE2...
>
> > Is the anchor in the content or in the cf template?
>
> > what does the HTML for the anchor look like?
>
> > Mine looks like this
> > <h1>More information<a
> >  name="more" title="more"></a></
> > h1>
>
> > On 10/9/07, *schlub* <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>> wrote:
>
> >     No dice... goes to the index.cfm page instead :(
>
> >     Cheers,
> >     schlub
>
> >     On Oct 9, 4:55 pm, "AJ Mercer" <[EMAIL PROTECTED]
> >     <mailto:[EMAIL PROTECTED]>> wrote:
> >     > how about
> >     > "/index.cfm#GoHere?objectid=CF208BBB-145E-2880-2944700ED26658B8"
>
> > --
>
> > AJ Mercer
> > Web Log:http://webonix.net


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"farcry-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/farcry-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to