tracker issue : CF-3924797

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

URL scope can't be emptied by calling structClear

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): / ext-user (Immanuel Noel)

Created: 01/21/2015

Components: Language

Versions: 11.0

Failure Type:

Found In Build/Fixed In Build: 292980 /

Priority/Frequency: Major / Most users will encounter

Locale/System: English / Mac 10 All,Win XP All

Vote Count: 1

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on August 24, 2019 using build 2016.0.01.298513
Related Bugs:
CF-3845979 - Similar to
CF-3845979 - Similar to

URL scope can't be emptied by calling structClear
This bug is an offset of the bug 3845979.

Steps to Reproduce:
1) Run the code below and make sure the form scope is empty initially.
2) Click the "Test" button.
3) See the result.

<cfif structKeyExists(url, "product")>
  <cfdump var="#url#" label="url scope">
  structClear called and it returned: <cfoutput>#structClear(url)#</cfoutput>

<cfdump var="#url#" label="url scope">
structIsEmpty called. Is the form scope empty? <cfoutput>#structIsEmpty(url)#</cfoutput>

<form action="" method="get">
  <input type="text" name="product" value="ColdFusion 11">
  <input type="submit" name="submit" value="Test">

After calling "structClear" and the function returned "YES," the heading of cfdump didn't display "empty," and when calling "structIsEmpty," it returned "NO."

The heading of cfdump should display "empty," and "structIsEmpty" should return "YES."


----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3924797

External Customer Info:
External Company:  
External Customer Name:  
External Customer Email:



+1 - Thanks Immanuel for filing this!
Vote by External U.
8872 | January 22, 2015 03:54:20 AM GMT
verified and closing the bug
Comment by Mukesh K.
8871 | June 17, 2015 03:47:17 AM GMT
Hi Adobe, I've verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513). Thanks!, -Aaron
Comment by Aaron N.
31187 | August 24, 2019 09:53:32 AM GMT