[Looking for Charlie's main web site?]

Note that ColdFusion 10 Update 13 is "needed" for OS X-only...and some confusion

Note: This blog post is from 2014. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.
Some of you may have seen that Adobe released a new hotfix for ColdFusion 10 last night, called Update 13. If you only read the text in the update (shown in the "Server Update" page of the CF admin), you might proceed to apply that update (which is ok).

But guess what: it technically only has changes related to Mac OS X (specifically adding support for its Mavericks version).

This is addressed if you read the technote that the update text points to, or the Adobe blog entry from last night which announced the update (more on these in a moment.) Those DO indicate that if you are not running that OS, you need not apply the update. (And the day after I wrote this entry, this indication was added to the update text itself.)

But what if you are on Windows (or another *nix variant besides OS X)? Should you apply it? What if you do? (there's NO PROBLEM!) What if you don't? And given that the update text says you need to reconfigure the web server connector, do you really need to bother on Windows?

And what if you are installing CF10 for the first time, since you DO need to apply updates upon installation? (you can either apply update 13 or 12, but you must apply at least one of them to be fully updated.)

As important, how might Adobe have better clarified this, and how might they make a simple change now related to that (they since did)?

I address in this entry these questions and a few other concerns I have, about confusion that may ensue.

Summary of concerns

I started to write some of this as a comment on the Adobe blog entry, but once it got to more than a paragraph or two I realized that was not the place. I'll instead point to this entry there.

And I then realized there was some more I could share, to help others, so I have expanded this still further.

So here are my concerns:

  • a minor quibble, but also easily fixed I think: why doesn't the update page (shown in the CF Admin) also clarify if this is for OS X-only, so that those on Windows (for instance) don't bother to proceed to apply it?
  • what happens if folks on Windows do apply it? (again, there's no harm!)
  • what will happen in the community now that we have an update that for some is "not needed"? Those whose CF admin shows an update pending may be left thinking that they (or someone else) haven't done their job (they should go ahead and apply it)
  • the hotfix text DOES tell folks they have to reconfigure the web server connector. Surely some will do that needlessly. What may happen for people who do reconfigure their connector when that's not necessary?
  • and what if someone is installing CF10 for the first time, on Windows. Should they apply this update? (Yes, unless for some reason they opted to install only update 12, seeing this only had changes for OX S.)
  • finally, can Adobe update the text on the CF 10 Admin update page for update 13, to clarify that it's for OS X only? (And that it's ok if others do?)

I'll address these points in more detail.

But beyond those technical matters about the update page text, some may also wonder:

  • what happens if people on Windows DO proceed to do the update? (there's nothing wrong!)
  • Is there really nothing in the update that applies to Windows?

I'll discuss these, also, but since those last two points are important, let me say right away lest anyone be scared about them, it's ok if you proceeded to do the update on Windows.

And while a review of the hotfix files changed shows files NOT specific to OS X, that too is ok! As I'll explain later, keep in mind that the hotfixes are cumulative. So this hotfix includes changes that were in previous hotfixes AS WELL AS the changes in this fix itself.

So bottom line: you don't need to apply it on Windows, but it is ok if you do. And if you've not applied any update at all, you should apply at least 12, if not 13.

Still, for all these reasons above, I have a bit of fear that this update, being labeled as "OS X-only" could cause some confusion, especially for Windows users, so I wanted to address these things here.

About the text of the update page, and whether this is for OS X only

(This issue has been addressed since I wrote this entry.) So first, about how easily people can be confused about whether the update applies on other than OS X, here's the issue.

If you view the update as displayed in the CF Admin "server update" page, it (for Update 13) reads simply:

> ColdFusion 10 Update 13 includes support for OS X Mavericks.
> For details click on the "Read More" link below.

OK, it does say it "includes support for OS X", but it doesn't say that it's ONLY for OS X. More on why I fear that could cause problems in a moment.

Let me note first that I DO realize that the technote pointed to there does say that "This update applies only to users who are on OS X Mavericks (10.9) or plan to upgrade to OS X Mavericks".

And the Adobe blog entry from last night, after discussing the fixes for OS X, does also state that "Users on other platforms need not apply this update".

My concern is that this is NOT clarified in that page shown in the CF Admin, which is what I suspect most will see (only). And more to the point, I have seen (in mailing lists, blogs, and my CF troubleshooting consulting services) that many (if not most) people never bother to click that "read more" link, to see that technote.

I fear that there will be some confusion as people speak about the update (whether it should or should not be applied, and whether one who has not done so is or is not "fully up to date".)

About the text of the update page, and whether people applying it MUST reconfigure the web connector

But my bigger concern is that the text on that CF Admin "server update" page (for Update 13) does go on to say specifically:

>IMPORTANT: After applying the update, reconfigure the connector using wsconfig tool. It is in {cf_install_home}/cfusion/runtime/bin.

So for those on Windows who do proceed to apply the update on Windows, if they have previously applied update 12 and reconfigured their connectors, they don't technically need to do it again (but they may).

Why is that a problem? Well, it could be an issue for some people, because rebuilding the connectors does several things (beyond just rebuilding the connector), like adding the CFIDE directory back to sites where folks may have removed it (especially an issue if you choose to reconfigure for "all sites") . It will also remove any custom mods that some may have made to the [cf10]\config\wsconfig files, such as uriworkermap.properties.

Now, it's true that I'm usually on a crusade to explain to people why they SHOULD be sure to reconfigure their connectors, when they are supposed to, as I have discussed in these blog entries:

And in fact, if someone has just installed CF10 for the first time, they should apply at least some update (whether update 13 or update 12). And as I discuss in those blog entries, they then SHOULD reconfigure their connector.

But in a case like this where the hotfix does not have any changes for Windows, and some will apply it on Windows who already have applied update 12 and reconfigured their connectors, the update text suggests that *everyone applying this update* should reconfigure their connectors, I'm just worried for them who would do the reconfiguration needlessly.

What about those installing CF 10 for the first time, especially on Windows?

(Update: I have added this question and answer two days after writing the entry, to address the question as I saw it being raised in the community.)

Here's another area where there will be some confusion.

As most know, when you install CF10 for the first time, it does NOT have any updates yet installed, so you need to apply them. (That's not new to CF10. It was the case in previous releases, as I have blogged about before.)

So yes, if someone is is installing CF10 for the first time, they need to apply the updates. Since they are cumulative, they need only do the latest. Now, if you're on Windows, then technically you can apply update 12 instead of 13, since the changes in 13 are unique to OS X. But as I will explain in more detail later, update 13 DOES still have in it all the changes from the previous 12 updates, since again they are cumulative.)

So it's not that you must not or cannot apply update 13 on Windows. It's just that you need not, if you already have installed update 12, as update 13 has no changes other than something that supports OS X.

But to be clear, if you are installing CF10 for the first time, you do need to apply SOME update after install, whether update 13 or 12 (or in the future, update 14 or later.)

Adobe: Can you tweak the update text?

So while it's great that the Adobe blog entry about this update and its technote do both clarify that it applies only to OS X, I wonder if Adobe could tweak the text shown on the updates page to add they did in the blog entry, "This update applies only to users who are on OS X Mavericks (10.9) or plan to upgrade to OS X Mavericks"?

At least then those who may see the update in their CF Admin going forward would be made more aware not to apply it if on another OS.

And then the text saying they must reconfigure the connector would make more sense as applying only to Apache on OS X.

But then, how about going a step further to clarify that as well as pointing out that it is indeed ok for those on Windows to apply the update. How do I know that, well, not from wording in these resources, but from my own testing. More on that next.

What if those on Windows DO apply the update?

One might reasonably wonder what happens if someone on Windows DOES go ahead and apply the update. Is it ok if they did? Should they go ahead, just so they no longer see an available updated? And what if they don't?

Well, the good news is that I just applied update 13 on Windows (on a dev machine), and I can report that it worked just fine.

I'll note that I did NOT bother to rebuild the connector, because judging from the technote and blog entry, I really didn't need to.

But that really leads to my final concern about this update...

Is there really nothing in Update 13 that applies to Windows? (The answer seems "no")

I know the technote and blog entry say it "only applies to OS X", so if those on WIndows do not, is there really truly nothing in the update for Windows users?

For reasons I've outlined above I went ahead and did it, to see what may happen (if anything). And again the good news is that the update does "just work" on Windows.

But after doing the update, I was a little curious to just double-check to make sure that there were indeed ONLY files related to OS X...

Yes, the update IS extracting files that are not OS X-specific--but not to worry

So I looked at the list of files updated by the hotfix, as shown in C:\ColdFusion10\cfusion\hf-updates\hf-10-00013\hotfix_filelist.log, and I was surprised (at first) to see many, many files not limited to OS X.

Again, before I leave any readers worried, fear NOT! this is not a problem. I will explain what we're seeing after showing what I saw, as others may notice. Here was the list of "modified" files, which had caused me stress initially:

Modified:   C:\ColdFusion10\cfusion\bin\cf-bootstrap.jar
Modified:   C:\ColdFusion10\cfusion\bin\cf-startup.jar
Modified:   C:\ColdFusion10\cfusion\bin\cfcompile.bat
Modified:   C:\ColdFusion10\cfusion\bin\cfcompile.sh
Modified:   C:\ColdFusion10\cfusion\bin\cfinfo.bat
Modified:   C:\ColdFusion10\cfusion\bin\cfinfo.sh
Modified:   C:\ColdFusion10\cfusion\bin\coldfusion.exe
Modified:   C:\ColdFusion10\cfusion\bin\coldfusionsvc.exe
Modified:   C:\ColdFusion10\cfusion\bin\mfc100.dll
Modified:   C:\ColdFusion10\cfusion\bin\msvcr100.dll
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\CheckConfig.exe
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\com2java.exe
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\com2java.xml
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\com2javacmd.exe
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\install_license.bat
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\international\CheckConfigEnglishResourceDll.dll
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\international\com2javaEnglishResourceDll.dll
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\international\ntvauthEnglishResourceDll.dll
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\international\ntvinvEnglishResourceDll.dll
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\international\regjvmcmdEnglishResourceDll.dll
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\international\regjvmEnglishResourceDll.dll
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\international\regprogidEnglishResourceDll.dll
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\international\regtlbEnglishResourceDll.dll
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\international\setdllhostEnglishResourceDll.dll
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\java2com.bat
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\jintmk.dll
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\ntvauth.dll
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\ntvinv.dll
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\ntvocx.dll
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\regjvm.exe
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\regjvmcmd.exe
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\regprogid.exe
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\regtlb.exe
Modified:   C:\ColdFusion10\cfusion\jintegra\bin\setdllhost.exe
Modified:   C:\ColdFusion10\cfusion\jintegra\jintegra_changelist.txt
Modified:   C:\ColdFusion10\cfusion\jintegra\version.txt
Modified:   C:\ColdFusion10\cfusion\lib\ib6core.jar
Modified:   C:\ColdFusion10\cfusion\lib\ib6http.jar
Modified:   C:\ColdFusion10\cfusion\lib\ib6swing.jar
Modified:   C:\ColdFusion10\cfusion\lib\ib6util.jar
Modified:   C:\ColdFusion10\cfusion\lib\jintegra.jar
Modified:   C:\ColdFusion10\cfusion\lib\mysql-connector-java-commercial-5.1.17-bin.jar
Modified:   C:\ColdFusion10\cfusion\lib\neo-drivers.xml
Modified:   C:\ColdFusion10\cfusion\lib\TypeViewer.dll
Modified:   C:\ColdFusion10\cfusion\runtime\lib\tomcat-coyote.jar
Modified:   C:\ColdFusion10\cfusion\runtime\lib\wsconfig.jar
Added:   C:\ColdFusion10\cfusion\lib\updates\chf10000013.jar
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\adminapi\administrator.cfc
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\adminapi\customtags\l10n.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\adminapi\security.cfc
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\Application.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\archives\wizards\archivewizard_page_scheduledtasks.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\archives\wizards\controludfs.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\cftags\l10n.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\cftags\l10n_testing.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\datasources\mysql5.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\debugging\index.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\logviewer\_searchloglogic.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\logviewer\_searchloglogic_other.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\scheduler\scheduleedit.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\security\cfadminpassword.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\security\userpassword.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\settings\memoryvariables.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\settings\version.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\setup\migrationcf8_import.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\setup\migrationcf9_import.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\updates\_settings.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\updates\_sysinfo.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\updates\_updates.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\updates\Application.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\updates\download.cfc
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\updates\index.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\updates\installer_input.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\updates\task\checkupdates.cfm
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\componentutils\cfcexplorer.cfc
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\scripts\ajax\ext\map\GMapPanel3.js
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\scripts\ajax\ext\map\mapiconmaker.js
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\scripts\ajax\FCKeditor\fckeditor.js
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\scripts\ajax\package\cflayout.js
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\scripts\ajax\package\cfmap.js
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\scripts\ajax\package\cfwebsocketChannel.js
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\scripts\ajax\package\cfwebsocketCore.js
Modified:   C:\ColdFusion10\cfusion\wwwroot\CFIDE\scripts\ajax\resources\cf\map\marker.png
Removed:   C:\ColdFusion10\cfusion\lib\updates\chf10000012.jar

I thought, "what are those DLLs and BAT files about? Those are obviously for Windows only. And what about all those CFM files in the Admin? Are those really only updated for the sake of OS X users? And the wsconfig.jar?"

And to be clear, I WAS in fact only updating from Update 12 to 13, as shown in the last line, where it was removing update 12.

And then I realized: ah, the CF10 hotfixes are cumulative. If you never applied any, and you applied the latest--such as after installing CF10--then you would get what was new in THAT hotfix AND all the previous ones.

And THAT's what all these file changes are about. They're not REALLY being "modified". It's just that the hotfix automatically exports all the files even if you don't REALLY need them to be "updated".

More specifically, I directly compared the various folders listed above (as found, deep within the hotfix jar) to the corresponding folders in the backup directory (C:\ColdFusion10\cfusion\hf-updates\hf-10-00013\backup), and indeed they were all the same, no not really "modified". (The wsconfig.jar was indeed updated, but again that's a known aspect of the OS X support that Update 13 is all about. I did not study any further to see what else was "really" changed for the OS X support.)


So I hope all that may help someone. It all had me wondering, and as I explored it, I thought others may be curious.

Again, to repeat my one plea to Adobe from the top: could you consider adding text to the update 13 text (as shown in the CF Admin page) to clarify a) that this is indeed really only for those on OS X, b) that only THEY must reconfigure their connector (if applying this update, after already having applied an earlier one and already reconfigured their connector after that), and c) that it's ok if someone on Windows DOES proceed to apply the update? :-)

I'll look forward to thoughts from Adobe or others to clarify.

But let me ask commenters please: let's not turn this into a screed of complains about how this is "just another example of Adobe dropping the ball", yadda yadda. That's not constructive. What I have offered is (I hope) constructive criticism. And while I could have made the plea to Adobe in just a couple of paragraphs (and will in my comment on their blog), I thought that readers may benefit from far more detail here. I don't write all this to complain against Adobe but to help other CFers.

For more content like this from Charlie Arehart: Need more help with problems?
  • If you may prefer direct help, rather than digging around here/elsewhere or via comments, he can help via his online consulting services
  • See that page for more on how he can help a) over the web, safely and securely, b) usually very quickly, c) teaching you along the way, and d) with satisfaction guaranteed
> or another Linux variant besides OS X

OS X is *NOT* Linux.

OS X is built on Darwin, which is a FreeBSD variant and (via NeXTStep,FreeBSD,NetBSD) a derivative of BSD UNIX.

Linux is a separate system entirely, inspired by UNIX in general, but not actually based on or derived from any common ancestor.

Given that CF is also supported on Sun Solaris and HP-AIX (and possibly others?), an appropriate way to write the parenthesised text would be something like "or any unix-like OS besides OS X", or even just "or any other OS besides OS X" would be fine.
Thanks Charlie for ones again in in-depth blog entry. Much appreciated.

I would like Adobe to look into the possibility to send relevant updates to relevant OS's through the CFIDE update mechanism.

In other words, if we on Windows ignore this update, the auto notification inside CFIDE is somewhat useless, as we will always see that there are updates available.

Second if this is only applicable on OSx then why should we on Windows get this update?
# Posted By David E | 1/12/14 1:32 PM
Hi Charlie,

Thanks for raising the concerns. Let me try to answers them as simple and clear as possible:-

a) that this is indeed really only for those on OS X,
ColdFusion 10 Update 13 is only meant for Mac OS users.

b) that only THEY must reconfigure their connector, and
Any users installing this update would need to reconfigure the connectors, using the wsconfig tool.

c) that it's ok if someone on Windows DOES proceed to apply the update?
A non Mac OS users (including all other ColdFusion 10 supported OS) can install it. It is a cumulative update and would not break the server, if applied.
For those of us working in Windows environments where we have an obligation to run 'all' updates, and document everything extensively, this update is exceedingly frustrating and could have been handled better (my personal opinion anyhow).
# Posted By Dana K | 1/13/14 9:45 AM
@Peter, I had mean to say "(or another *nix variant besides OS X)". Sorry, it was late on a Saturday evening when I wrote those this, wanting to get it out especially for Windows users. I have corrected that.

@David, thanks for the kind regards, and appreciating the reason I write these as I do. It's comments like that which help to keep bloggers going. As for your observations about the update mechanism, let's see if Adobe may have a comment on your suggestion.

@Anit, I appreciate your points a and c, but on b I must express confusion. Why would someone on another OS need to reconfigure their connectors, especially for instance if a Windows user had installed update 12 and reconfigured their connectors at that time? There's certainly no need for them to do it again upon applying this update, is there?

Maybe what you meant to say is "if a Windows user had either not applied update 12 or had not reconfigured their connector when they did", then yes they must do it.

This is a long-standing problem with the wording in all these updates over the past year regarding the updates and when a connector reconfigure is required. For readers interested in more, I addressed this in the other blog entry I linked to above.

The issue is that technically a reconfigure of the connector IS required for some updates, but not for others. So if you are going from one update that required it (and you did it) to another that does not, you need not do it again.

Or if you are installing CF10 for the first time, then you must apply updates as none are included (and you need only do the latest), but then since you will be including earlier updates which DID require a reconfigure, you must do it then.

Anit, is that perhaps why you have said in your comment, "Any users installing this update would need to reconfigure the connectors, using the wsconfig tool." Are you thinking more of those installing CF10 or the first time?

While I can understand you may want to err on the site of protecting such folks, the fact is (unless you tell me otherwise) that it seems that statement is not ALWAYS true, such as for one who had applied update 12 already and DID reconfigure their connectors then.

It is indeed a challenge (on both sited, you and us) to keep all this straight, and I think that's what leads to some of the frustration people express. I appreciate it's just challenging, and I'm trying to help with my blog entries.

Finally, Anit, as an Adobe representative, did you have any thoughts on David's suggestion?

@Dana, I hear you. Let's see if Adobe has any thoughts.
Can you clarify this even more . . .

This update is for those on OS X who has >>already<< installed CF10? What about if you want to install CF10 for the first time on OX Maverick? Won't this mean that the initial install will not run since all the concurrent updates are not included in the install package, thus making it difficult or impossible for one to apply Update 13 to get it working properly?

This is one point that Adobe needs to clarify.
# Posted By Lola LB | 1/13/14 11:55 AM
@Lola, first let me say that I really think you'd be better off asking this question on the Adobe CF team's blog entry for the update (the one I pointed to at the outset above, http://blogs.coldfus...).

I say that not only because that's where you can expect Adobe to answer, but also because it's a good question that others may well have, and should see answered (there, I'd propose, as more will see that than this.)

But I suspect the answer is that you have 2 choices (since it seems it's the Apache connector that is fixed, judging from the bug report pointed to from the technote).

a) you could run the installer, proceeding to integrate CF with Apache (during the install), but then apply the updater from the command line (not the CF Admin, since the connector problem will seemingly prevent you seeing the Admin via Apache until the fix is applied). Then you could run the wsconfig tool to rebuild the connector, and then after a restart you should be able to access the CF admin via Apache.

b) or, one could run the installer, but choose the option to have the installer NOT integrate CF with Apache, using CF's internal (Tomcat) web server instead (which runs at port 8500 by default). You could then run the update in the CF Admin, and THEN run the wsconfig tool to update the connector. Then you cold either use the internal or Apache web server to access the CF Admin going forward. (You can also disable the internal web server and then ONLY be able to access it via Apache).

But that's just my guess. I'd still recommend you ask the question on the CF team blog, so others can see it. Feel free to point to my answer here. You can click the pound sign below my comment here (on my web site) to get the URL to point them directly to this answer. (I can't provide the link yet, as it's created when I post this comment.)
@Charlie, Yes, I should have rephrased it, "if a Windows user had either not applied update 12 or had not reconfigured their connector when they did", then yes they must do it. Thanks.

Re-configuring connector is not always required. That is why, we prefer saying, you "MAY" have to re-configure the connector. And the best example is, if you have already configured the connector for Update 12 on "windows", then apply the Update 13. Connector re-configuration is not required, in this case.

@David, If you are on windows, then you can ignore this update, if you don't wish to install Update 13. Otherwise, you can install it, but would not need to reconfigure the connector. ColdFusion 10 has the same update mechanism across all OS. That is the reason, Adobe created this update as cumulative, so that there is no room for any confusion related to future updates.

@lola, just saw you post as well and Charlie has already responded. If you want to install CF10 for the first time on OX Maverick, then download the latest version of CF10 from www.adobe.com, apply the mandatory update and apply the Update 13 directly. This update is cumulative and includes fixes from previous updates.
If all CF hot fixes are cumulative, then won't all users get the fixes contained in update 13 when the next revision is released?
# Posted By Debbie | 1/16/14 2:05 PM
I'm on Windows and am not going to install this update. I have automatic emails set up though and I get an email every day saying there is an update to apply. Any way to turn that off for this update?
# Posted By Derek | 1/17/14 10:37 AM
Derek, why not just apply the update? I explained above that there is no reason not to.

The problem is with the wording: Adobe was trying to say "the only thing changed in this update is for OS X". They should not have said it is "only for OS X".

Rather than look for a way to stop the notifications, really, just apply the update and be done with it. :-)

To me, a more tragic implication of this wording hit last night as I helped a client. They had applied only update 11 previously, somehow not noticing when 12 came out. When I showed them that there were behind, and they saw update 13 and I explained they were cumulative, we proceeded to install it.

But then the update text for update 13 says only that those on OS X need reconfigure their web server connectors. In the case of these folks, they DID ALSO need to reconfigure their connectors, since in now applying update 12, that DOES require reconfiguring them.

It's just such a shame that Adobe has so few lines in that text box for each update on the Admin page. Perhaps they should increase that, to be more clear about issues such as these. Or they could/should be more clear about them in the technote, of course.

I just fear that few people bother to read them. Do we really just say "too bad for them", or might something be done to help a problem that happens to a majority of people? I suppose that's a much bigger question about human behavior, corporate responsibility, etc. I just put it out rhetorically, as much as anything.
@Debbie, yes they will. But the subsequent comment from Derek (and my reply) is why I think people ought not wait, if that may have been what you meant.
OK, I applied the update and didn't rebuild the connector and everything appears to be working fine. Thanks a lot.
# Posted By Derek | 1/17/14 11:09 AM
@Derek, right. It's cool to do the update (on Windows), and if you had rebuilt the connector with update 12, there's no need (on Windows) to rebuild it again after applying update 13. (Anyone reading this in the future, look at the text for any further updates, from 14-on, to see if THEY require a rebuild of the web connectors, on Windows or otherwise.)

Thanks for your confirmation and kind regards, and glad to help.
Hi Charlie, thanks for amazing post. This wonderful post cleared most of my confusions. Sometimes updates creates a lots of problems. My primary concern was "what happens if folks on Windows do apply it? (again, there's no harm!)"

# Posted By Fred | 2/4/14 7:06 AM
Mainly to say thanks! Great article to clear the confusion. However, as I was doing a new machine install, I was even more confused, because I had to deal with the contradictory mandatory update information as well as the shocking instructions - it was actually another article of yours that helped me with that too.
# Posted By Chris Bowyer | 4/30/14 1:04 AM
Copyright ©2024 Charlie Arehart
Carehart Logo
BlogCFC was created by Raymond Camden. This blog is running version 5.005.
(Want to validate the html in this page?)

Managed Hosting Services provided by
Managed Dedicated Hosting