Update: Since this post was made, the final version of Update 16 was released and should be used instead.
The ColdFusion 10 Update 16 prerelease build has been refreshed.
For changes please refer this document.
For instructions on how to install this update you can refer this blog post announcing the Update pre-release.
We look forward to your feedback and suggestions.
NB. Users who had applied ColdFusion 10 Update 16 pre-release build earlier, should uninstall and re-apply this update build. The build number after applying this update should be 10,0,16,293399 (PreRelease).
Newbie
25 posts
Subscribe
I find all of this confusion with ColdFusion quite amazing. We moved to Rails from CF last year and it’s been the best move we made. just look at the above threads – nothing has changed with regards to ColdFusion’s crazy connector updates. CF remains a confusing, buggy, yet very expensive, product, where nobody knows what update does what and the documentation and support is all fragmented. Just try searching google for ColdFusion support, it’s a joke. The last straw for us was repeated connector failings and Adobe telling us nothing was wrong. Poor product. Period.
[subscribe] (yep Charlie, one of those posts!)
Expanding on Shawn’s idea, I can see the value. But Shawn, would you want them to offer just a link to the XML, which is the feed for the updates? There’s is a URL for update’s jar in that feed, but not everyone would likely know what to do with that feed and how to extract the URL.
Or did you want them perhaps to list either the latest or all jars in the sidebar? that could get unwieldy, I think.
Of course, Piyush did note that he updated the originaly u16 prerelease blog entry to offer the link to that one jar, but you’re asking for something more generic, right?
And if you did think the feed would be what should be shown (not each jar), would you want them to list only a link to the production release feed the prerelease one also?
I could see there being some potential confusion in that a link only to the feed may not be as clear to some readers that one is for prerelease and another is for final.
And some people would also need that info offered in the doc page Piyush shared, to know what to do with the jar if downloaded manually.
I’m just noting that there’s not much room in the sidebar for all this, which may explain why they’ve not done something like you ask yet. 🙂
Maybe they could come up with a better single page that covers it all, whether in the docs or as a blog post, and then offer a link to that in the sidebar for folks with this interest you express. (Of course, then some would never notice it if it WAS added, but that’s not a problem they can solve easily, right?)
As always, just trying to help (you, them, and other blog readers, in this case).
How about a link on the side bar of this blog called Coldfusion Manual Updates? The need will exist beyond this prerelease patch. Should be one central advertised location for manual updates.
Thanks Shawn, for the clarification.
The suggestion has been incorporated in the original post announcing the prerelease.
Missed my point, it should be available easily, not digging through files. Link on either this blog, or the Adobe CF landing page. Lots of information gets buried here when they get answered in these one offs.
Shawn,
The download link for update jars can be found embedded in the updates.xml file set in your CF administrator updates settings. For prerelease builds of CF updates, the file is:
https://cfdownload.adobe.com/pub/adobe/coldfusion/PR/updates.xml.
To apply the update manually, download the update jar manually and follow the instructions at:
http://help.adobe.com/en_US/ColdFusion/10.0/Admin/WSe61e35da8d318518-33adffe0134c60cd31c-7ffe.html
Please put a link on this site for manual updates. Not every web server can reach out to Adobe, it should be easy to find.
Barry,
You can manually download the update from the following hyperlink:
https://cfdownload.adobe.com/pub/adobe/coldfusion/PR/10/hotfix_016.jar
You will also find hyperlink above, embedded in the updates.xml file for the prerelease (https://cfdownload.adobe.com/pub/adobe/coldfusion/PR/updates.xml).
Please note that this is a prerelease build of Update 16.
May I know if there’s a reason you want to download the hotfix jar manually, and not use the built-in updater mechanism in the ColdFusion Administrator.
On a separate note, The typo and the hyperlink in the post have been corrected.
Thanks Charlie for pointing those out. You’ve been most kind.
Barry, this is still a prerelease, which is why you don’t see it in the official feed. Instead, you need to check a different URL to see prerelease builds (a point some have argued against).
Two aspects of this blog post may have confused matters for you: first, the details about how to get the prerelease builds are in the first post about the update 16 prerelease, which is pointed to above (though not as a hyperlink). It’s https://coldfusion.adobe.com/post.cfm/coldfusion-10-update-16-prerelease-build-available.
Second, the title of this post says “update 16 *and* prelease build”, which could be read by someone to imply that update 16 was final and something else was a “prerelease build”. It’s just a unfortunate choice of wording, I think.
Piyush, if you may be able to tweak this entry to turn that URL into a hyperlink and perhaps also remove the “and” from the title, it may help avoid such confusion. Thanks.
I somehow missed the announcement of this update. I have been going to http://www.adobe.com/go/coldfusion-updates to locate current updates of ColdFusion and I’m not seeing that this site has been updated to show the new update.
Also, where would I go to manually download this update?
@Charie, you make a good point. We will see if this can be accommodated into the release notes going forward.
Hmm, that’s a little curious. I mean, I think most of us would read that just as well to be used to indicate fixes that were updated (not just new) in the refresh. It would help folks who had a problem with a feature (listed as fixed in the first release) to see that it may be “really” fixed now in the update (like the spreadsheet issue you refer to, I suppose).
Do you think you guys only use it to indicate “new” fixes, and not also “updated fixes”?
Charlie,
There are no new fixes in the new update 16 build, only a couple of spreadsheet related fix reversions.
The asterisk related annotation, therefore would not really translate into anything for the document.
It will be duly removed. Thank you for pointing that out.
This is off-topic to the post itself here, but it’s definitely related: I suspect some readers will want to be notified if you may answer that question (to know if/when an update to the document may be shared), so we may well soon see folks posting comments with the content “subscribe”.
For those who have wondered about those (in other posts here), it’s because this blog software Adobe uses does not currently let people ONLY subscribe to a thread (by clicking the “subscribe to this comment thread” and leaving off any comment). We are REQUIRED to post at least some comment.
This is unfortunate, as it does cause several of the posts to be littered with such “subscribe comments”, and understandably, if one wants to see comments but has nothing specific to add.
Adobe folks, is there any chance you could get your blog software to allow us to leave off a comment and only subscribe to comments? It may be simple some config option you need to enable. I can’t see any reason not to, if it’s that easy.
Another benefit would be that I suspect there may be some people who would love to subscribe to comments but are reluctant to have to have that show up so publicly as a comment (even if an empty one). And yes, they can just change their name and choose not to “remember my information” for that post.
But if the software just worked by allowing one to silently subscribe, it would kill two birds with one stone. 🙂
Even better would be if there was provision for us to subscribe to ALL comments in ALL posts. Some of us do care enough about virtually every topic that’s blogged about here that we’d just as soon see every comment.
While I’ve not seen any blog software offer that sort of option via a form, I HAVE seen many offer an RSS feed of all their comments (like they have such a feed for all posts), and then one could choose to subscribe to that using any RSS-tracking tool/service.
While you DO offer an RSS feed for your posts here, you do NOT offer one for all comments. Could you perhaps consider that? Again, it may well be available already and is just not listed here on the right, or maybe it can be easily turned on (and perhaps more easily than the “silent subscribe to a post’s comments” requested above).
And who knows, if there’s an RSS feed for all comments, maybe you can enable one for a given post’s comments, and some may prefer THAT to a silent subscribe–though I’m sure others will always prefer a silent subscribe checkbox to handling RSS feeds.
Anyway, is there someone at Adobe responsible for the blog software who may be able to consider and respond to these ideas/questions? Sorry I couldn’t think of another way to get it in front of such a person. But maybe this will allow others to chime in about the idea, though of course only if they find this blog post. 🙁
@Piyush, thanks for this. But is the document linked to really the right or latest version?
I ask because while it has the indicator at the top saying “** indicates bugs fixed in the refreshed build”, here are no bugs listed with that indicator. (By comparison, the CF11 version of the document, referenced in the other blog post today, DOES indicate at leasst 2 such updated bugs.)
(And I don’t think I’m seeing any sort of cached version of the page, since it’s the first time I’m opening it and again it DOES have the header indicating how updated bugs are to be found. Still, I also forced a browser refresh and see the same thing.)
As always, just trying to help.
You must be logged in to post a comment.
23 Nov
10AM Pacific
Online
