As I'd raised a few of the issues Adobe claims to have fixed in these recent ColdFusion updaters, I figure I should probably do some testing for them.
With the offending line being the isAdminUser() call.
On the update 5 pre release this now works fine, yielding true.
I wrote a whole blog article around this one (indeed, the other one was found during writing of the same article): "ColdFusion bug challenge: how quickly can one find a bug in ColdFusion 11?". Basically there's some bad error trapping in CFAdmin, should one try to set-up new CFAdmin users before setting the " Separate user name and password authentication" setting. The full repro is in that blog article: I'll not repeat it here.
Firstly I verified the issue still existed in ColdFusion 11 update 4: yes.
... and indeed I an no longer reproduce it. Fixed.
This was a bloody annoying one. If one had made modifications to the web server connector config files, they weren't backed-up if one had to reinstall the connector (which, let's face it, is almost every time there's an update it seems). Not only did it not back-up the changed files, it also wiped any of one's own back-ups one might have made because the process blows away the entire directory.
I'm not prepared to do the requisite messing around to test this, so I'll leave this as an unknown.
Excellent! An actual language issue. I covered this one in a blog article too: "Bugs in iterator functions in both Railo and ColdFusion".
Obviously the intended result is "23,43,53". In discussions over this ticket, Rupesh suggested they'd just use the first delimiter character in the result list, as this matches listSort()'s behaviour. Fair enough.
Good work ColdFusion Team: 3/3 fixed.
This one was some weirdness we encountered with - well, as it says above - mixed-in methods accessing the super scope. I write it up in this article: "Super and mix-ins don't mix very well". The full repro involves a bunch of files, so just refer back to that article.
The basePrivateMethod method was not found.
Which is what we'd expect. On update 5, however, it works fine.
And a perfect score for the ColdFusion Team so far: 5/5 bugs fixed.
The callbacks for these methods need to be analogous to the other array iteration methods: not simply receiving the element value, but also receiving the index and a reference to the whole array.
6/6 bugs fixed in update 5 ColdFusion Team: good work.
I've just noticed I didn't actually raise any of the tickets fixed in the ColdFusion 10 update 16 pre-release, so there's nothing for me to check there. If you did raise any of the issues that got fixed, make sure to test 'em eh?
Good work Adobe ColdFusion Team on these. There's another coupla ones I'm gonna look at separately as they sound interesting, but I'm pleased at your 100% strike rate on these issues I raised. Keep it up.