tracker issue : CF-3554978

select a category, or use search below
(searches all categories and all time range)
Title:

Automatic updates improvements

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Philipp Cielen / Philipp Cielen (Philipp Cielen)

Created: 05/06/2013

Components: Hot Fix Installer

Versions: 10.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: Final /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Platforms All

Vote Count: 5

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on February 18, 2019 using build 2016.0.01.298513 
I was asked by Rupesh Kumar to post this to the public CF Bugbase:

Ideally CF would handle most of the things mentioned in the FAQ (http://blogs.coldfusion.com/post.cfm/coldfusion-hotfix-installation-guide) automatically. It could automatically detect that access to the hotfix RSS-feed  is not possible and offer alternatives:

If CF cannot access the remote RSS file it could offer to try again using a proxy and ask for configuration details (and if successful automatically store these for later use)

As an alternative a direct link to the manual downloads could be provided. Maybe the hotfix file could then be downloaded and placed in an existing directory labeled hotfixes. Then the next time the CF administrator is opened it could automatically detect a new hotfix file in that directory and ask if it should be installed etc.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3554978

External Customer Info:
External Company:  
External Customer Name: cielen.com
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

+1. -- Adam /////////////
Vote by External U.
15501 | May 06, 2013 06:49:13 AM GMT
Good idea to improve usability.
Vote by External U.
15502 | May 06, 2013 10:49:13 AM GMT
This is quite important as the official CF 10 lockdown guide tells you to put request DENY on the CFIDE/scripts directory, which is required to get updates via the automatic updater. If you follow that advice (and you should), updates won't succeed and you'll be left wondering why.
Vote by External U.
15503 | July 02, 2013 08:36:43 AM GMT
If Adobe wants to help ensure systems around the world running their software really are secure then the update process needs to be as simple and fool proof as possible.
Vote by External U.
15504 | July 02, 2013 09:07:23 AM GMT
+1 This recently bit me - when following the Lockdown guide. Though I think the documentation in the lockdown guide could be altered slightly, too. Simply, have the DENY rule for / CFIDE/scripts removed prior to the update process - then re-enable it after the update process. Similarly, don't ADD it to the DENY list (in the docs) until after the updates are completed and the alias for the scripts folder created. - Though this option then shows a disconnect with the other DENY instructions. (I prefer the above option - of redoing it - it makes more logical sense.) Lastly, publish in the SUPPORT section for ColdFusion, the URL for manually retrieving hotfixes / updates and also place this URL somewhere relevant for the auto-update process. Gavin.
Comment by External U.
15499 | July 02, 2013 06:33:20 PM GMT
right now if the server's updater can't reach the update site, it reports no updates available instead of an error (ER: CF-3586646).
Vote by External U.
15505 | July 02, 2013 08:02:07 PM GMT
Proxy configuration on this page can be skipped as proxy settings are picked in case a proxy is configured for the server. We can look at providing a link to download the update manually in the technote document that we publish with each update. Also, the DENY rule on /CFIDE/scripts would no longer be needed as this has taken care of in the next release.
Comment by Vamseekrishna N.
15500 | August 19, 2015 12:04:29 AM GMT
Hi Adobe, I've verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513). Update files are directly downloadable from their release notes page, and the scripts folder has been moved out of /CFIDE. Thanks!, -Aaron
Comment by Aaron N.
30305 | February 18, 2019 06:22:29 AM GMT