search : scopes

select a category, or use search below
(searches all categories and all time range)

displaying top 100 results

2613697 CF-3183868 Paul N. The properties in the variable scope were not serialized. Only the properties in the THIS scope were serialized. Now after taking all this properties, checking in the variables scope also. If some property is not available in the THIS scope, then they are taken from
Comment on Another example of scoping issues with inconsistent bahviour by External U.
Comment on Make Owner scope explicit so that we can scope the variables correctly? by External U.
Comment on Make Owner scope explicit so that we can scope the variables correctly? by External U.
Comment on Make Owner scope explicit so that we can scope the variables correctly? by External U.
Comment on Make Owner scope explicit so that we can scope the variables correctly? by External U.
Comment on [ANeff] Bug for: cannot assign null to variables in some scopes from CFC by Vijay M.
Comment on Locally scoped variables with null values may see scope bleed by Dan S.
Heavy Handed, but effective. Passing entire scopes into CFTHREAD.
Comment on Another example of scoping issues with inconsistent bahviour by External U.
2611698 CF-3600334 External U. The arguments scope and local scope are two separate scopes. There's no reason why a developer shouldn't be able to have local.foo and arguments.foo.
Comment on Bug introduced in ColdFusion 9 still plagues us today - session scope gets trashed by Rupesh K.
Comment on Bug 84833:(Watson Migration Closure)[ANeff] Bug for: Clearing local scope odd behavior (ignore #84831)Please disregard #84831 by Aaron N.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 79029:(Watson Migration Closure)Doing a StructCopy() on the arguments scope doesn't return a copy of the arguments scope - it simply returns the arguments scope by External U.
Comment on Bug 79029:(Watson Migration Closure)Doing a StructCopy() on the arguments scope doesn't return a copy of the arguments scope - it simply returns the arguments scope by External U.
Comment on Bug 79029:(Watson Migration Closure)Doing a StructCopy() on the arguments scope doesn't return a copy of the arguments scope - it simply returns the arguments scope by External U.
2673190 CF-4146924 Himavanth R. The change of behaviour is a fix rather than a regression. IsDefined and so IsNull should honor the scope lookup and based on precedence. Previous versions were not doing the lookup and that was partially fixed as part of bug # CF-3556075 SearchImplicitScopes
Comment on Bug introduced in ColdFusion 9 still plagues us today - session scope gets trashed by S V.
Comment on Heavy Handed, but effective. Passing entire scopes into CFTHREAD. by David Byers
Make Owner scope explicit so that we can scope the variables correctly?
Comment on form scope can't be emptied by calling structClear by External U.
Comment on Closures and outer arguments have no scope by Aaron N.
Comment on CGI Scope geting reset by websocket handler by External U.
Comment on Make Owner scope explicit so that we can scope the variables correctly? by External U.
Comment on Make Owner scope explicit so that we can scope the variables correctly? by External U.
Comment on Make Owner scope explicit so that we can scope the variables correctly? by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 83654:Summary: CFCATCH struct seems to be put in the VARIABLES scope, not the VAR scopeConsider the code in the repro case by External U.
Comment on Bug 74323:In CF9, a LOCAL-scope variable can overwrite an ARGUMENT-scope variable having the same name by External U.
Comment on Locally scoped variables with null values may see scope bleed by James M.
Comment on Locally scoped variables with null values may see scope bleed by Dan S.
Comment on Locally scoped variables with null values may see scope bleed by Dan S.
Bug 82450:(Watson Migration Closure)[ANeff] ER for: Scope="true|false" + functionLocalScope()1) "useLocalScope" (boolean) attribute to cfcomponent & cffunction2) functionLocalScope() (suggested by Elliott
Comment on Implicitly declare array fails when var scoped by Matthew C.
Comment on form scope can't be emptied by calling structClear by Himavanth R.
Comment on properties should not be exposed in the this scope by External U.
Comment on properties should not be exposed in the this scope by External U.
Comment on Scope-handling with increment operator is glitch by External U.
Comment on Another example of scoping issues with inconsistent bahviour by External U.
Comment on Bug 84833:(Watson Migration Closure)[ANeff] Bug for: Clearing local scope odd behavior (ignore #84831)Please disregard #84831 by Adobe D.
Comment on Closures and outer arguments have no scope by Aaron N.
Comment on Closures and outer arguments have no scope by Aaron N.
Comment on Bug introduced in ColdFusion 9 still plagues us today - session scope gets trashed by Aaron N.
Comment on Bug introduced in ColdFusion 9 still plagues us today - session scope gets trashed by Aaron N.
Comment on Var scope continues to be in effect even after local-scoped variable becomes null by Vijay M.
2610089 CF-3731425 Rupesh K. This is how variables are resolved and ColdFusion always would look at the implicit scopes like URL scope to resolve it. In your case, your variable is defined in the variable scope and that gets the preference over the implicit scopes like CGI, URL, FORM, Cookie etc
Bug 79029:(Watson Migration Closure)Doing a StructCopy() on the arguments scope doesn't return a copy of the arguments scope - it simply returns the arguments scope
[ANeff] ER for: Disableable scope shadowing
Comment on same as bug 4176297 but losing session scope also by Kailash B.
4261416 CF-4202194 Aaron N. Hi all, Just to be clear, `final myVar = foo` should create `foo` in the default scope. Currently, that is always the `variables` scope. Inside UDFs, the bleeding issue should be fixed via a mechanism to assign all unscoped variables (such as `final my
Scope precedence in ColdFusion 10
Request scope still being reset by WSPublish function.
Closures and outer arguments have no scope
Tracker Issue Scoped connection
Scoped connection
Comment on Bug introduced in ColdFusion 9 still plagues us today - session scope gets trashed by External U.
Comment on Locally scoped variables with null values may see scope bleed by Vijay M.
2596964 CF-3302639 Language : CF Component steve ryan Extending CFC with implicit getters and setters Problem Description: If you create a component with implicit getters and setters and extend that component in another component, the implicit getters are extended in the variables scope. However
Bug 73015:(Watson Migration Closure)Railo has a "Cascading Scope" feature that I would very much love built into CF Server
Comment on same as bug 4176297 but losing session scope also by Kailash B.
Comment on Setting non-scoped variable in a udf in CF2016 behaves differently from CF11 by External U.
Comment on File is an undocumented global scope by External U.
Comment on form scope can't be emptied by calling structClear by Immanuel N.
Comment on form scope can't be emptied by calling structClear by Immanuel N.
Comment on form scope can't be emptied by calling structClear by External U.
2609785 CF-3773095 Vamseekrishna N. This would introduce lot of confusion as currently there is clear distinction between the scope of variables defined using var inside a function and variables defined outside a function which go into the variables scope.
2610089 CF-3731425 Awdhesh K. In later version, an option in CF admin will be added to define the order of scopes search where in BIF can take priority over url/form scopes.
Comment on this.serialization.preservecaseforstructkey doesn't work in application, session or request scopes by Awdhesh K.
2611054 CF-3647489 External U. No Rupesh it is along the lines of the original bug which you closed as Not wirth the effort. There is a serious issue when it comes to scopes. As per the original bug, I have since provided more samples even from your own documentation on how to use scopes inside