Skip to main content
G
GuitsBoy
Inspiring
March 13, 2014
Question

Upgrade from CF8 to CF10 now CFC cant read from request scope

  • March 13, 2014
  • 1 reply
  • 5742 views

Please bear with me as I am primariliy a systems and network admin as opposed to a developer.

We are in the process of migrating our code from CF8 to CF10, and the inhouse developers are complaining about one error they cant figure out.  We have a page that uses cfgrid to call a CFC.   This CFC throws an error about a request variable being undefined, however I do se that it is defined in the debigging information of the parent page. 

Error invoking CFC at /toDynamic/display/admin

sitecampuses.cfc : Element FUSEBOXOSNAME is undefined
in REQUEST.

I know we are using an older version of fusebox, but it would be a monstrous task to upgrade it at this point.

Any suggestions?

    This topic has been closed for replies.

    1 reply

    G
    GuitsBoyAuthor
    Inspiring
    March 13, 2014

    It appears that the cfc is somehow calling fbx_Settings.cfm, however it is not calling index.cfm which sets request.fuseboxosname.

    Since we have no application.cfm file, how could the cfc call fbx_Settings.cfm?   I cant get my head around this.

    Carl Von Stetten
    Carl Von Stetten
    Legend
    March 18, 2014

    Is there an Application.cfm/.cfc file in a parent directory above where the CFC resides?  ColdFusion will traverse the directory tree upward to the webroot to find an Application.cfm/.cfc.  If there is one, you might try creating a minimal Application.cfm/.cfc in the same directory as your CFC to short-circuit that process and guarantee a clean execution of your CFC.

    -Carl V.

    Carl Von Stetten
    Carl Von Stetten
    Legend
    March 18, 2014

    Yes, we manually cleared template caching, and disabled any cache settings we could find.  I dont think it would be a cached issue, since it never worked in that manner before.

    The code was brought directly over from cf8 where it worked.  This is a new development server to test the codebase before we roll out to production. 

    It seems to me that that ajax binding is somehow calling index.cfm in an above directory, when it should only be calling the cfc alone.


    Can you post the full error message/stack trace?

    -Carl V.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices