I just ran into this issue.  It's the new farFU.cfc that seems to be
behind this.  It's running a test against http://cgi.server_name/pingFU
to determine if you have a rewrite rule in place.  This seems a bit
busted.  The application.cfc is returning a response when
http://cgi.server_name/?furl=/pingFU is true... I just set the test in
farFU to match this.  Maybe there's supposed to be a FU in the system
for pingFU that's not there when you upgrade?


Matthew Williams
Geodesic GraFX

On Jan 28, 4:53 pm, Chris Roth <[email protected]> wrote:
> I have 5.1 (upgrade from 4.11) on my development server. I am using
> the wiki referenced (Ionic ISAPI_REWRITE4).
>
> My legacyfriendlyURLS mydomain.com/go/myFU are working just fine,
> however like mentioned above the site is rendering the objectID in the
> links generated by Farcry (navigation, etc.) and if I try to view a FU
> from object admin, I get the message (notice it does display the
> legacy FU)
>
> You do not currently haveFriendlyURLs available. Ask your
> administrator to add the required webserver rewrite.
>
> /go/corporate
>
> Questions:
>
> 1. How do I get Farcry to recognize that I have (want) FUs enabled (is
> anyone using the Ionic DLL and if so, what should the ini look lke to
> get the new FU mechanism working without losing the legacy /go or
> interfereing with currently configured virtual directories /
> subfolders?
>
> 2. How do I ensure I do not LOSE any of the legacy /go/myFU urls. (ome
> are on printed materials and other are accessed from offline
> application)
>
> 3. Will a "rebuildfriendlyurls" result in the loss of legacyfriendlyurls?
>
> Thanks!!
--~--~---------~--~----~------------~-------~--~----~
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