On Sep 8, 9:49 am, RobG <[EMAIL PROTECTED]> wrote:
> Okay, new update.  I did a fresh installation on my "other" server that
> I mentioned in my last post.  Again, it's Win Server 2003, IIS and CF8.
>
> This time I was able to reproduce the problem... I created a tree with
> Quick Site Builder.  Everything was good.  I could see the "Show
> Friendly URLs link".  So I Rebuilt them all, and now they don't work
> again, same problem... instead of whatever.com/go/something, it's
> whatever.com/go/something/something, but the nav menu on the public side
> only shows one "something" instead of two like in Admin.
>
> I'm thinking of trying to dig around and find the code that handles the
> two sections of the site and see what's different, but before I go to
> the trouble, I'd rather ask here since it'll probably be much less work. :)
>
> Any ideas on how to make this  work right?  If I don't figure out a
> solution SOON, I'm gonna have to ditch FarCry and find something else.
> Now that I've debuted the site to the client, they're expecting it to
> work.  Grrr.  Wish I'd found this problem sooner, so I could have
> delayed my meeting...

Can you try updating the pages.  ie. perhaps the quick site builder is
the problem and its not correctly creating the FU.  If you edit and
approve a specific page where the FU is failing does it return?

The only way we can really help is if you can provide specific step by
step instructions for how you get to the point that the FU's no longer
work.  As it is we have *a lot* of clients running 4.0 and friendly
URLs without the problems you describe.

-- geoff
http://www.daemon.com.au/


--~--~---------~--~----~------------~-------~--~----~
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