If the subfolder uses the FarCry application scope, you will need to remove
the application.cfm from that folder (I think it's possible to extend
application.cfc's, but that's too complicated for me :). If it just does
it's own thing you can add your own <cfapplication ... > tag.

Blair

On Thu, Jun 25, 2009 at 5:32 AM, SiteVision, Inc. Support <
[email protected]> wrote:

>
> I have upgraded a site from 4.09 to 5.1.  Finding a few bugs along the
> way, but that is a topic for a different post.  The site loads fine
> and works great except for one problem - we have a few pages in the
> fbapps folder that we link to directly instead of going "through"
> farcry to get to.  Whenever I click on a link to one of these files, I
> get the "You are trying to initialise a 4.0 application using a 5.0
> core. Would you like to setup and run the updater now?" page.
>
> How do I prevent this page from running?  The one-page description of
> the updater at
> http://docs.farcrycms.org/display/FCDEV50/Upgrading+From+Earlier+Versions
> says that the farcryInit tag (which is in the Application.cfm files)
> was "hijacked" to initiate the installer.  I can remove farcryInit
> from the Application.cfm in the webroot with no problems (because
> FarCry now uses Application.cfc without that tag), but if I try to
> remove the farcryInit tag from the Application.cfm in the fbapps
> folder, the page bombs with a "Variable APPLICATION is undefined. "
> error .  That may be something we can fiddle with, but for now, I want
> to know the answer to this question:
>
> Is there a way we can the updater from running after the site has been
> updated?
>
> Thank you,
>
> Tom
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message cos you are subscribed to "farcry-dev" Google group.
To post, email: [email protected]
To unsubscribe, email: [email protected]
For more options: http://groups.google.com/group/farcry-dev
--------------------------------
Follow us on Twitter: http://twitter.com/farcry
-~----------~----~----~----~------~----~------~--~---

Reply via email to