Update: I have learned since posting this that the problem is about the Adobe security certificate embedded in CF, which is used when pulling down the update file. That has never happened before, that I know of: certainly not since the new CF update mechanism introduced in CF10, but I don't recall it in any updates before that. So as I said above, this update is requires that you first must be on the latest PREVIOUS update before applying it. The new update requirement is a twist/challenge (FWIW, CF 11 received its last update in June 2019, when it and CF20 were last updated, as I posted then.) So those on CF2018 must first be on update 4 before going to this new update 5, while those on CF2016 must be first on update 11 before going to this new update 12.Īs always, I share a bit more here, for my readers. Uniquely, though, this update is the first ever to require that you must first have updated to the PREVIOUS update before applying this new one. I will update this (and that) if we hear new info from Adobe.īeyond adding important security and bug fixes as seems typical, this update offers several new or changed features, as well as updated support for things (such as Java 12), as is also often the case. So I would recommend folks hold off on applying it for now. And I may revise the content as necessary.Īdobe has announced today that there are new updates for CF2018 (update 5) and CF2016 (update 12).Īs an update to this post, I have offered a new post, pointing out that many people are having problems with this set of updates here. Corrections are welcome, in the comments. Same with links and subsequent comments from myself or others. Some content may be outdated-though not necessarily.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |