Showing posts with label Adobe. Show all posts
Showing posts with label Adobe. Show all posts

Monday, 2 March 2015

That's it: no more ColdFusion_12 or CFClient

You might or might not have twigged that I was running the @CFClient and @coldfusion_12 Twitter accounts. They were parody / pisstake / satirical account gently prodding the general business approach of the Adobe ColdFusion Team.

Well, anyway, someone filed an official complaint about them, so Twitter has closed them both down.

Friday, 27 February 2015

Friday, 20 February 2015

Adobe ColdFusion Team getting their act together?

On the heels of ColdFusion update 4 coming out yesterday, I see that there is now ColdFusion 10 Update 16 prerelease build available (37 fixes), as well as ColdFusion 11 Update 5 prerelease build now available (119? fixes). Good work.

Note that these updates are still only pre-release quality, so only fit for testing. Do not put the into production.

Wednesday, 17 December 2014

Hands up: who has issues accessing the ColdFusion bugbase?

There is a continuing issue with access to the Adobe ColdFusion bugbase: when clicking on a link (like this one:, many many people get one of two things:

  1. redirected to a login page (that URL requires no login, so that is invalid);
  2. put into a perpetual redirect loop between ticket and login page.

I think other people have different symptoms too. And a select few actually get to see the bug. 75% of the time, I cannot get to the bug page unless I use an incognito page. Sometimes if I clear my cookies I can get in without an incognito window, but often I still can't.

Adobe are looking at this (our man Kapil is the star there), but they cannot replicate it. This gobsmacks me, TBH, as so many people seem to have issues.

Do me a favour will you? Go click on that bug URL above, and post back what you get? Do you go straight to the ticket (lucky bugger), do you have to login? Do you get into a redirect loop? Something else? If you could let me know your OS, browser (/version) etc, that might help. If you can't get in initially, but blow awway your Adobe cookies, does that help? Anything relevant, really. If you're happy to liaise with Kapil directly, please let him know on Twitter: @KaroraKapil.

Cheers for your help.


PS: oh and vote for that bug, will you? Cheers.

Monday, 15 December 2014

Say "no" to Adobe and their bloody stupid generic CFScript syntax

Firstly, sorry this blog has been a bit of a non-event recently. There's various reasons for this - none of them interesting - but I'll get back on form soon. -ish.

Now. Frickin' Adobe.

Friday, 5 December 2014

Adobe's most valuable employee

No messing around: it's Anit:

TBH, I have not even checked which ticket Anit is following up on here, I'm just focusing on this bit:


And Anit doesn't. No matter what gets thrown at him. He works to help his (ColdFusion) community. No excuses, no "closed/cantbearsed". Anit just cracks on and gives us the answers.

Almost everyone else on his team could draw a page from Anit's book when it comes to client support.

Anit: thanks dude,


Saturday, 22 November 2014

The Adobe ColdFusion Team are doing a bloody good job at the moment

I know I am the first (and loudest, and most repetitive...) to whinge about Adobe's ColdFusion lads (/ladesses), but... fair's fair... there's very bloody little to complain about at the moment.

Thursday, 13 November 2014

ColdFusion 2016: instead of <cfbell> and <cfwhistle>...

I was asked to comment on Microsoft's announcement that the entire .Net Framework is going open source (".NET Core is Open Source"), and what we - the CFML community - should think about that in the context of ColdFusion.

Friday, 7 November 2014

ColdFusion: Adobe kinda trumped me to this

An article I've been drafting in my head is a suggestion for Adobe as to how they can make the ColdFusion release cycle less painful for their clients. They've actually done part of what I was thinking of advising today, by releasing the latest updater for ColdFusion 11 to beta for us to test ("ColdFusion 11: a decent bugfix update has been released to beta"). But I'll write down what I was thinking anyhow.

Monday, 27 October 2014

FFS, Adobe. Stop being such bloody amateurs

Now this irks me (in case you had not noticed).

Here's a couple new bugs that have gone into the Adobe ColdFusion Bug Tracker:

Tuesday, 14 October 2014

ColdFusion: new security patches for 9.0, 9.0.1, 9.0.2, 10.x, 11.x

Patches just came out for all versions of ColdFusion from 9.0 upwards. Details in their security document: "ColdFusion Help / ColdFusion Security hot fix APSB14-23".

I've not checked the content of it, but I will say that if at this late stage of ColdFusion 9's like (it's EOL on Dec 31 this year) they're releasing individual patches for all of 9.0, 9.0.1, 9.0.2, then I am guessing it's fairly serious. So get your test machines updated as soon as possible and regression-test your apps, then look to move it to live as soon as it seems stable.

And in the mean time, we're still waiting for a more useful bug-patch for both CF10 and CF11. Wonder when to expect thosethat? They'reIt's been promised as coming out "soon" since about August, I think..?

I've just notice that the ColdFusion 10 one is actually a fairly substantial patch, fixing 60-odd issues! So that's quite good. Details in "ColdFusion Help / Bugs fixed in ColdFusion 10 Update 14".

Anyway, there you go.


Tuesday, 23 September 2014

Adobe: stop closing ColdFusion bugs you haven't dealt with

I've had a frickin' gutsful of Adobe's amateurish and disrespectful approach to dealing with bugs in the bug tracker. I spotted yet another "closed, not enough time" issue today. One which hit me back in 2011. It was first raised in 2009. Five years ago. It first cropped up in CFMX7. It's not a complicated one, it's just that the seem to have a glitch in working with leap years, for some date calculations. "Bug 82249:(Watson Migration Closure)Datediff function does not calculate differences correctly".

This has gotta stop, Adobe.

I checked the bugbase to see how many issues had been closed with "not enough time".


Dating back to 2005.

These are all bugs that have impacted paying clients sufficiently for them to bring them to Adobe's attention. And Adobe's reaction is to just go "oh well... [shrug]... [clicks the 'Close' button]".

This is unacceptable.

Tuesday, 9 September 2014

Please indicate your irritation @ the ColdFusion Team

They've gone and done it again, as apporproately described by Adam Tuttle:

Thursday, 4 September 2014

212... 0

I've been keeping an eye on how many untriaged ColdFusion bugs there are:

Help provide Adobe with more info, pls

Hey, Adobe are struggling to replicate the issue I detail in 'Have found some evidence for that "There was an error accessing this page. Check logs for more details." issue in CFAdmin', and raised as ticket 3810459. Which Adobe have closed as "works OK on my machine".

This is the situation in which CFAdmin will sometimes present this error when trying to make settings changes:

If you have experienced this, could you pls chime in on 3810459? Even if you haven't solved it, providing Adobe more info would be helpful. Plus would help them realise it's a real issue that impacts a bunch of people, not just me and the other bod who has commented.



Wednesday, 20 August 2014

Go and vote, pls

Sorry for the silence recently... my life is getting very... complex of late.

Anyway, Adobe are playing at silly buggers with a bug that they're dragging their heels about, and they are saying it needs more votes to get more attention.

It's to do with CFClient, but just on principal, I've voted for it because they need to stop with these sloppy implementations. Hopefully you think likewise, so will go vote for this: "queryExecute params not working in mobile".

Sloppy, inconsistent implementations ought not need votes to get fixed. Adobe ought to have more pride in their work. But if instead they need votes... let's give them votes.



Thursday, 17 July 2014

Where are the ColdFusion 10 & 11 updates, Adobe?

Here's a quick thought that's been bugging me for a month or two now. What's happened with the ColdFusion updater?

Checking Wikipedia, the update history for ColdFusion 10 is as follows:
2012-May-15: Adobe ColdFusion 10 (build 10,0,0,282462)
2012-August-31: Adobe ColdFusion 10 Update 1 (build 10,0,0,282462)
2012-September-11: Adobe ColdFusion 10 Update 2 (build 10,0,0,283111)
2012-October-16: Adobe ColdFusion 10 Update 3 (build 10,0,3,283145)
2012-November-02: Adobe ColdFusion 10 Update 4 (build 10,0,4,283281)
2012-November-19: Adobe ColdFusion 10 Update 5 (build 10,0,5,283319)
2012-December-11: Adobe ColdFusion 10 Update 6 (build 10,0,6,283435)
2013-January-15: Adobe ColdFusion 10 Update 7 (build 10,0,7,283649)
2013-February-27: Adobe ColdFusion 10 Update 8 (build 10,0,8,284032)
2013-Apr-10: Adobe ColdFusion 10 Update 9 (build 10,0,9,284568)
2013-May-14: Adobe ColdFusion 10 Update 10 (build 10,0,10,284825)
2013-July-09: Adobe ColdFusion 10 Update 11 (build 10,0,11,285437)
2013-November-12: Adobe ColdFusion 10 Update 12 (build 10,0,12,286680)
2014-January-10: Adobe ColdFusion 10 Update 13 (build 10,0,13,287689)

So there's a steady stream of updates and hotfixes there, up until Jan this year. Then nothing for over six months now. And it's not as if there's no bugs to fix in ColdFusion 10. I posted some analysis of "significant" ColdFusion 10 bugs a while back: "What should Adobe be retro-fitting into ColdFusion 10? Here's a potential list", and there's a reasonable case that Adobe should be dripping out fixes from that list (or similar) pretty much constantly. But nothing.

Some will leap to Adobe's defence saying "but they were busy working on ColdFusion 11", sorry but we oughtn't give a shit. Life goes on, and we've already paid for ColdFusion 10, so they should be making good on the bill of goods they're already sold us before prioritising the next thing they expect us to buy.

I also think by now there ought to have been a few hotfixes for ColdFusion 11... it's not short in the bug / half-finished department either.

So what's going on, Adobe?


Tuesday, 15 July 2014


I'm frickin' lousy with dates (as in "calendar", not as in "romance". Although the same applies, from memory ;-). Well: remembering dates is never a problem, but remembering what the current date is is something I'm not so good at. I forgot to touch base with my big sister on her birthday over the weekend... and there's another anniversary on the same day.

I've been doing this bloody blog for two years now. Which is approximately 23 months longer than I expected it to last.

Last year I gave you some stats ("1"). I'll try to do the same now.

  • I've now published 750 (this'll be the 751st) articles. I still have about a dozen in progress. The same ones as last year, funnily enough. The topics just don't have legs, I think.
  • And the word tally is now up around 600000 words. So in the second year I didn't write quite as much as the first year (350000), but spread over more articles (428 in the last 12 months vs 322 in the first year).
  • I've had another 3000 comments since the previous year's 2000. That's pretty cool. Thanks for the contributions everyone. Often the comments are more interesting than the articles, I find.
  • Google Analytics claims I've had 86000 visitors over the last year (up from 25k in the first year). So this thing is getting more popular. The average per day is 230-odd. It was around 120/day in year one. It's still not a huge amount of traffic, but I guess my potential audience is pretty small too.
  • The busiest day in the last 12 months was 5 March 2014, with 593 visitors. That was towards the end of the isValid() saga, with this article: "ColdFusion 11: Thank-you Carl, Mary-Jo, many other community members and indeed Rupesh", and a click-chasing one entitled "CFML is dying. Let's drop it off at Dignitas". Looking at the analytics, that was the bulk of it, plus I was writing a lot about new features in ColdFusion 11 around about then, which boosted things. That was also my biggest week ever, by quite a margin.
  • The most popular article last year was the one about me migrating from "ColdFusion Builder to Sublime Text 2". That's had 2200 visitors. The next most popular were as follows:
  • The most +1'ed article was "I am one step closer to being unshackled from ColdFusion". It's interesting that that was the one that people liked the most. It had 13 +1s. Most articles get none or maybe one, so that's quite a lot.
  • Last year I worked out which article had the most comments. I have no idea how I did that, and I can't be bothered working it out again. So erm... that'll remain a mystery.
I've blogged a lot about ColdFusion 11 during the year... what with it being in public beta and then being released. I've also compared its functionality to Railo's equivalents. I've shifted my primary dev platform at home to Railo now. I've done a lot of JavaScript over the last 12 months (I've spared you most of the detail), but haven't progressed in other languages as much as I'd like to. That's my mission for the next year.

I battered Adobe a lot about how they (don't) handle their bugs. I will continue to do this. They're long overdue for an updater to ColdFusion 10, for one thing; plus we should have had at least a coupla small updates to ColdFusion 11 by now.

The biggest shift in my coding practices in the last year has been down to reading Clean Code, and adopting a lot of its suggestions. My code is better for it. I've got my colleagues Chris and Brian to thank for this... both the encouragement to read the book, but also keeping at me about it. Sometimes to great irritation on my part. If you have not read that book: do so. Especially if you're either of the two members of our team who still haven't read it. Ahem.

Another thing I've been fascinated with this year gone is TestBox. I love it. I am looking forward to shifting off ColdFusion 9 at work so we can start converting our MXUnit styled tests to BDD ones. Brad and Luis are dudes.

I've bitched a lot about Stack Overflow, but contrary to what I threatened ("Not that it will really matter in the bigger scheme of things..."), I still answer questions there every day (if I can find questions I can answer, that is).

Railo continues to rock. As do Gert, Micha, Igal from Railo. They really have done brilliant work keeping CFML alive and interesting.

A bunch of people have motivated me to write this year... it's too difficult to pull out a list of the main miscreants, but Sean would be the top. And the list of my various muses (or adversaries!) is - as always - on the right hand side of the screen, over there.

Gavin deserves special mention, as he very kindly tried to raise money to get me across to CF.Objective() ("Shamelessful plug"), but we had to kill that plan just as it was getting started ("Do not sponsor me to go to CF.Objective()"). But happily Gert stumped up with a ticket at the last minute ("Well that was unexpected"), so I made it anyhow. I really am taken aback by you guys. Seriously.

And of course Mike from CFCamp paid for my entire conference last year too ("CFCamp 2013"). That was amazing. And I mean both Mike's generousity, and the conference itself. Go to it this year if you can: CFCamp.

Ray's done most of the work for ColdFusion UI the Right Way, but I've helped out a bit. I'm glad we got going with that project.

Thanks for your participation in this blog, everyone. If you weren't reading it or commenting on it, I'd've chucked it in. But you keep coming back. Cheers.

Oh and let's not forget: <cfclient> sucks arse. And I can tell that without using it, Dave Ferguson ;-)


Thursday, 3 July 2014


A few days ago I mentioned that "Adobe apparently cease development and/or support of UI tags in ColdFusion". This was because one of their dudes said as much (this was on 3043516):

Ray sniffed into this - as it didn't sound right to him, and confirmed it was not actually the case. I've been holding off on adjusting my initial comment until I got clarification from the ColdFusion Team themselves.

I had followed up Uday's comment with the observation that it's all well and good to deprecate the UI stuff, but some customers have already in good faith paid for these features, so there really is a professional burden on Adobe to fix the bugs that people have raised, rather than basically just go "[nothing to see here, move along]".

Friday, 13 June 2014

Do me a quick favour?



Thanks, I've got the information I need now. Cheers to everyone who helped.

Could someone pls check whether any of these links yield actual bug records, or simply say:

The information requested is not found
My expectation is that all of them say "not found". Do any work properly for you?