tracker issue : CF-3312096

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


| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): James McCullough / James McCullough (James McCullough)

Created: 08/16/2012

Components: Language

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Final / 11.0

Priority/Frequency: Minor / Very few users will encounter

Locale/System: English / Windows 7 64-bit

Vote Count: 3

Problem Description: CFPARAM variables with a trailing space after the name will override the form submission with the default value of the param variable

Steps to Reproduce: Create a form with a variable with a name of "fooVar" and a value of 716. Post this form to a page with a param of "form.fooVar "  and a default of 0.  Please note the space in the param declaration of "form.fooVar ".

CFDUMP of the form scope will reveal a value of 0 for "fooVar".  This is the cfparam value. Remove the space in the CFPARAM call and resubmit.

The value will now be 716 as expected. 

Actual Result:

Expected Result:

Any Workarounds:

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

Watson Bug ID:	3312096

External Customer Info:
External Company:  
External Customer Name: jimmymac601
External Customer Email:  
External Test Config: My Hardware and Environment details:

Coldfusion 10 Developer, Windows 7 64-bit, Tomcat 7



This bug still exists in build 285380 and also affects ColdFusion 9.0.1. Here's the code that I tried. (I also tested this on against Railo. It returns the correct results.) <cfparam name=" test " default="xyz"> <cfparam name="test " default="123"> <cfparam name="test" default="abc"> <cfparam name="test2" default="abc"> <cfparam name="test2 " default="123"> <cfparam name=" test2 " default="xyz"> <h2>test</h2> <p>expecting "abc"?</p> <cfdump var="#test#"> <h2>test2</h2> <p>expecting "abc"?</p> <cfdump var="#test2#">
Comment by External U.
18515 | September 09, 2013 12:58:49 PM GMT
The CF10 reference indicates that CFParam requires a name of the parameter (variable) to test, but a ColdFusion variable cannot contain a space according to CF 10 Variable naming rules: There's no error thrown if an invalid variable name is used. (I found this out by accident after pasting a variable name that had a trailing space.) This issue impacts ColdFusion 9 too.
Vote by External U.
18528 | September 09, 2013 01:06:03 PM GMT
I can confirm what James says here. The bug ain't fixed in CF10. I'm running 10,0,11,285437, so should include the fix, based on your claim "Fixed In Build 283521" -- Adam
Comment by External U.
18516 | September 09, 2013 01:48:36 PM GMT
The build number does not include the version number it is fixed in. This fix would not be included in the update but in the next release.
Comment by Rupesh K.
18517 | September 11, 2013 05:46:17 AM GMT
So it's pretty pointless info to expose to the public then, innit? How about you expose a value that's actually useful? -- Adam
Comment by External U.
18518 | September 11, 2013 11:33:57 AM GMT
This fix will be available in the next major release.
Comment by Nimit S.
18519 | February 09, 2014 06:34:02 AM GMT
Has this been released yet? I know at least one person still seeing it in CF11 (see
Comment by External U.
18520 | October 21, 2015 07:25:35 AM GMT
This was fixed in CF 11. Could you please confirm that you are seeing it in CF 11? I will have someone look into the blog post.
Comment by Rupesh K.
18521 | October 27, 2015 02:47:25 AM GMT
This bug was reported for ColdFusion 10 only 3 months after it was official released (5/15/2012) and almost 5 years before EOL (5/16/2017). Will it be fixed in CF10? Was this one of the announced bugfixes for CF11? I don't see this bug mentioned on this official blog post: CF10 & 11 both had patches recently released. Why isn't this bugfix included in the CF10 patch?
Comment by External U.
18522 | October 27, 2015 07:53:19 AM GMT
Hi James, This fix was included with CF11 release build itself. Are you able to repro this issue with CF11? If yes, please share the build number. But this fix is not available with CF10 as of now.
Comment by Nimit S.
18523 | October 27, 2015 09:00:11 AM GMT
Sorry... I'm using CF10. It's the version that this bug was actually reported in 1.5 years before ColdFusion 11 was released. Is the CF10 fix for this radically different than CF11? After witnessing many bugs only get fixed in the newest releases of CF, I'm starting to believe it's intentional and an attempt to force developers to purchase newer licenses. QUESTION: Will it be fixed in CF10?
Comment by External U.
18524 | October 27, 2015 09:29:16 AM GMT
+1 for fixing in CF10, which was the version the bug was actually raised against.
Vote by External U.
18529 | October 27, 2015 09:44:44 AM GMT
We usually include fixes for those bugs in update which are critical and impact your application in production. This bug does not cut that criteria and would not be included in the update for CF 10.
Comment by Rupesh K.
18525 | October 27, 2015 08:29:10 PM GMT
You (Adobe) usually only fix bugs years after they are reported and then only include the bugfix in newer versions. Is this a business strategy? If not, please explain why bugs reported within months of a product release are ignored for years.
Comment by External U.
18526 | October 28, 2015 10:36:52 AM GMT
I'm running CF10 on certain applications, and would like to see bugs reported mere months after its release to be fixed in that version.
Vote by External U.
18530 | October 29, 2015 09:54:45 AM GMT
Agreed. Bugs need to be fixed - IN A TIMELY FASHION - in the version they were raised against. Enough of this "we'll just ignore stuff for a coupla years before looking at it" shonkiness
Comment by External U.
18527 | November 04, 2015 03:51:23 AM GMT