-
1. Re: Did The 7.02 Upgrade Change the Rules for Variables
It tried in on a CF6.1 server and it didn't work as you first stated it. I tested it on a CF7.02 as well, which failed. It would only work if I enclosed in quote and pound signed it. I don't have a way to test it on a 7.0 server though. Someone else may be able to.
Odd that it worked before, as normally VARs should be encased in #'s. -
2. Re: Did The 7.02 Upgrade Change the Rules for Variables
7.02 as you describe (displays "mylist") Linux & Windows
6.1 as you describe (displays "mylist")
Sorry don't have a 7.01 version handy without firing up the VPN.
The CF 5 server isn't on today...so I can't test that one either.
hth
--
Tim Carley
www.recfusion.com
info@NOSPAMINGrecfusion.com -
3. Re: Did The 7.02 Upgrade Change the Rules for Variables
Just tested 7.01 on unix...same as the others...displays "mylist"
Maybe you were dreaming... ;-)
hth
--
Tim Carley
www.recfusion.com
info@NOSPAMINGrecfusion.com -
4. Re: Did The 7.02 Upgrade Change the Rules for Variables
Thanks to those who tested the code and replied. Obviously I didn't remember correctly. Two excuses - I rarely cfloop through lists (I'm a cfscript type of guy) and our upgrade was very recent. -
5. Re: Did The 7.02 Upgrade Change the Rules for Variables
as far as I can recall, if you're looping over a dynamic list you've -always- needed to do <cfloop list="#myList#" ... >
without the pound signs (but with quotes), CF sees the string as a literal string and a single element list ("myList").
i'm in the habit of always quoting attribute values, so i've always done it as "#myList#". i can't comment on just doing list=myList or list=#myList#, but even if those worked, i'd suggest not relying on that and getting into the habit of placing quotes around your attribute values.