Skip to main content
A
Anonymous
September 25, 2014
Answered

The getBuiltInScopes method was not found

  • September 25, 2014
  • 3 replies
  • 6840 views

  I have an application that has worked for quite a while. I have made no changes to the code since the last time I used it. Basically, the code creates a zip file with input for an involved report. I used it in March of this year it worked fine. I've been assured by the gov't sysadmins and DBAs that nothing has changed, but I still get the attached error. Any ideas?    I have just heard from a friend who knows CF, that it could be a version issue.  I am currently running 8 and I believe he is running 10.   If this is an issue, is the solution somewhere on this site?   I do minimal CF and am at a loss.   The function that is throwing the error is when a button is clicked, a javascript routine is run which combines all the files requred for the zip file.   Yesterday, another application started throwing the error.  I haven't been through the code yet, but it is another button being clicked, and I'm sure, another javascript error.

This topic has been closed for replies.
Correct answer

getBultInScopes() is a ColdFusion 8  procedure...   getCFScopes() is the current call.   My problem was, there was a special debug module that had the call and I could find it nowhere else.  Finally refreshed my Application.cfc from Production and found a call to getBuiltInScopes() there that wasn't in the module I had.   Commented that section out and the error disappeared.  Thank you all for your assistance.

3 replies

A
Anonymous
Correct answer
October 7, 2014

getBultInScopes() is a ColdFusion 8  procedure...   getCFScopes() is the current call.   My problem was, there was a special debug module that had the call and I could find it nowhere else.  Finally refreshed my Application.cfc from Production and found a call to getBuiltInScopes() there that wasn't in the module I had.   Commented that section out and the error disappeared.  Thank you all for your assistance.

A
Anonymous
September 30, 2014

Since I have discovered (for my own knowledge) getBuiltInScopes() vs getCFScopes()...   is there anything else like that out there?   The application I inherited, was written with ColdFusion 8 and the Production server is now up to CF10.    A bunch of errors, similar to this, have popped up recently without me doing anything to the code.  I am assuming the SysAdmin on the production system did an update or patch and some of this older stuff is not compatible...   I really need to solve this error and any other related.   Thank you.

BKBK
Community Expert
BKBKCommunity Expert
Community Expert
October 1, 2014

Your concerns are justified. The issue may turn out to have consequences. The error stops Coldfusion processing the page further. However, the user who pressed on the button to approve or disapprove apparently did so for a reason.

Bring any errors you may have to the forum. We shall be glad to discuss them with you. Good luck.

A
Anonymous
October 1, 2014

Indeed.  They use this to approve or disapprove a request.  Now they have a work stoppage and I have no idea how to fix it.    The reboot after the commenting the code out in the ONLY place the getBuiltInScopes is listed in the entire application, did nothing.  I still get the same error.   How can the getBuiltInScopes error still show up if I changed it to getCFScopes and then finally, commented it out?  This is truly maddening.

BKBK
Community Expert
BKBKCommunity Expert
Community Expert
September 26, 2014

The functionality getPageContext().getBuiltInScopes() was only implied. Adobe has removed it. Search your code for the function and replace it with getPageContext().getCFScopes().

A
Anonymous
September 26, 2014

Yes,, I found that yesterday and did just that.  I promoted it to Production and am still getting the same error.   In my search, I only found one place where the getBuiltInScopes shows up... 

BKBK
Community Expert
BKBKCommunity Expert
Community Expert
September 26, 2014

Check the stack trace that comes with the error message. It should point you to the location of the error.

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