I mentioned this one during my tour, the ColdFusion MX 6.1 updater is now available. This update to ColdFusion MX 6.1 consists of several fixes that have previously been available separately; the JRun Updater 3 (for ColdFusion server configurations only), new releases of DataDirect JDBC drivers and JIntegra COM support, making sure that these important components are up to date, all security fixes through July and over 60 bugs fixed in ColdFusion. It rolls together all ColdFusion MX 6.1 hot fixes and security patches that have been released to date, eliminating the need to install multiple hot fixes and patches. Many other included fixes have not been available elsewhere. Details at http://www.macromedia.com/support/coldfusion/ts/documents/cfmx61_updater.htm.
ColdFusion MX 6.1 Updater Available
19 responses to “ColdFusion MX 6.1 Updater Available”
-
It only took 2 years!
-
It took 1 year actually … RedSky(CFMX6.1) was released last August-ish.
-
Will this work if CF is configured as a J2EE/Multiple instance install?
-
Yes, but you have to install it for each instance. If you read the Release Notes, they tell you all you need to know.
-
I am not sure what is more sad, the fact that people post dumb comments, or the fact that they know that the comments are dumb and post them anyway under a veil of anonymity.
-
This guy posted on Seans site also, must be a serial blog blagger!
-
My blog as well. If you don’t have the guts to name yourself, your opinion is worthless.
-
Hi Ben,
I’m trying to update my CF in JRun mode and I always get CFIDE path is not a CFMX 6.1 CFIDE Directory. All the installation was made with default values. The default path is the same where the CFIDE directory is located.
Any ideas? -
João,
I did this last night, I beilieve the standard CF/JRun4 installation (cfusion) sets the CFIDE at [webroot/CFIDE].
Try renaming [JRunRoot/servers/cfusion/cfusion-ear/cfusion-war/CFIDE] TO CFIDE_OLD and see if you can still access the administrator, if not your CFIDE dir will be under your webroot. -
Sorry João, too little sleep last night :<
I meant if you cannot access the cfadmin after renaming the CFIDE dir then that will be where it is installed.
I’m sure it depends on what server selection you make at install (All/Default/Built-in). -
ben
can i install this version of the updater over top of a beta install of this updater? will that muck anything up?
thanks
tony -
Tony, I can’t think of any reason why it would not, but … make a backup. 🙂
-
Ben,
Why no updater for Mac OS X systems? We use OS X for development and would like the 6.1 update for this platform.
Darrell, SybronDental -
After installing the updater, I check the version number on the CF administrator and came to discover that I didn’t have the correct version number (6,1,0,83762). I previously installed hotfix hf53486_61 and my version number was 6,1,hf53486_61. I found out that in order to get the correct version number I have to go into my web.xml located in the WEB-INF directory of the instance and remove the hotfix from the param-value. After that CF administrator showed the correct version number.
Just a little tidbit so someone else doesn’t reinstall the update 50 times :P. -
Darrell,
1) Go here: http://www.macromedia.com/support/coldfusion/downloads_updates.html
2) Download and run the "English Java Installer".
Thanks -
Damon, Thanks for the info RE: updater for OS X.
Darrell Johnson -
All, I’m working with a client who set up a server, installed CF from a 6.0 disk… upgraded to 6.1…. no problems. But now, after installing the 6.1 updater, the left panel in the CF admin will not load and barks about MDAC’s or something. Sorry, client was unclear… but thought that might be enough for the fellow bloggers.
-
I have tried this on several machines from different locations…
The links to the MX6.1 Updaters on the Updater page gives me a 404. Did Macromedia take down the updaters? -
Sorry… let me be more specific….
This file…..
http://download.macromedia.com/pub/coldfusion/updates/cfmx_61update_win.exe
gives me the 404.
I can get to the page that lists the newest updaters, but the links that point to the files themselves produces the 404.
Sorry for the confusion.
Leave a Reply