tracker issue : CF-3827677

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

CF10 is evaluating strings with comma's as complex types (Array), formerly they were just Strings in version 8

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Geoffrey Marsh / Geoffrey Marsh (ScarletOrangeman)

Created: 09/18/2014

Components: Language

Versions: 10.0

Failure Type: Crash

Found In Build/Fixed In Build: Final /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Win All

Vote Count: 0

Duplicate ID:	CF-3295296

Problem Description: Variables that used to be considered strings are now being interpreted as arrays.  Same code and database works fine in Coldfusion 8, but when we switch to the server running CF10, it gives us an error saying that the argument being sent across isn't a string.  Any if I change the argument type to "any" it'll pass that section but gives me an error saying you cannot evaluate complex values as simple values later on.

Steps to Reproduce:

Actual Result:

Expected Result:

Any Workarounds:

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

Watson Bug ID:	3827677

External Customer Info:
External Company:  
External Customer Name: ScarletOrangeman
External Customer Email:  
External Test Config:



Can you post some code? Is this about form fields with same name? Which update are you on?
Comment by Himavanth R.
10853 | September 19, 2014 03:22:00 AM GMT
Comment by External U.
10854 | September 23, 2014 03:36:28 PM GMT
I just wrote a workaround for the issue. It appears as though the application on CF8 treated the form output on multi-select form inputs as comma delineated strings, but when we moved it to the new CF10 server, it treated them as arrays. I wrote a quick javascript snippet that converted the form input from an array to a string and all works fine after that. The weird part is that multi-selects should *always* be interpreted as arrays, was my impression, so I'm not sure what was different about the previous environment.
Comment by External U.
10855 | October 08, 2014 09:49:07 AM GMT
There's a setting on CF10 for this, and I suspect you are victim of the same situation as described here:
Comment by External U.
10856 | October 08, 2014 02:02:31 PM GMT
This was fixed in Update 1. Bug #CF-3295296. Did you apply the updates?
Comment by Himavanth R.
10857 | October 09, 2014 03:22:50 AM GMT