(Note that the bug report's title indicates that this is a CF11 problem, but it was found ultimately to indeed apply to CF2016 also.) But if you are somehow stuck on CF11 update 12 or CF2016 update 4, the workaround was to obtain a special hotfix jar file, either the one for CF11 or the one for CF2016.(If you find that just clicking the link shows you gibberish in your browser, right-click the link and save the file instead.) Then you were to put that saved jar in the lib\updates folder for your instance(s), and restart CF, and the problem would go away.This issue is discussed in a CF bug entry, CF-4198570, but since I've had a couple of customers recently ask for help on it, I thought I'd bring it up in a blog post here.

cfinput not validating-71cfinput not validating-19cfinput not validating-10

Cfinput not validating yoskar ola dating scam

Both the issues above are certainly more reasons folks should consider that, as is the aforementioned deprecation. Still, my role is that of a CF Server troubleshooter, and when someone comes to me wanting to fix this problem which may be preventing them going forward with an update or migration, they don't want to hear "remove all the CF UI tags and replace them with a better javascript library to do such things".

But I realize some think that's what should be said always to anyone ever using them.

(The problem seems to happen in Chrome more often than other browsers, at least for some users I've talked with.) The issue was originally discussed in the CF bug entry, CF-4198570.

And again since then, you can just go to the next CF update and it fixes the problem.

This is discussed in the Adobe blog post about this new installer in December 2016.

The good news (for those who need this to work, as part of a move to CF2016 perhaps, where they want to minimize effort in making the move), that Adobe blog post (and a related technote) offers a link for you to download that YUI library to put the feature back.

The first problem was introduced in the CF2016 installer released in Dec 2016, and any after that, where Adobe has literally removed the library used for the calendaring, but you can add it back, as I discuss below.

(If you install or installed CF 2016 from the original installer in Feb 2016, you won't see this problem as it wasn't removed then.) The second problem was introduced in those two named updates, and was fixed in the very next updates (CF11 update 13 or CF2016 update 5).

(If you're not clear about the location of where to put the update jar file, for a typical Windows installation the CF2016 location would be C:\Cold Fusion2016\cfusion\lib\updates.

You'll see that that folder holds the jar file for whatever update may have been previously applied.

Solving the 503 error with an updated URLLong-time CFer needing to find new non-CF work? No, the updater does not try to "back up the entire cf directory". [more] How to solve common problems with applying Cold Fusion updates (in 10 and above) Peter Williamson said: I didn't know about the update log, thanks Charlie. [more] Why you should think twice about leaving on the "public JRE" option of the Java JDK installer Charles Robertson said: Charlie. [more] A veteran Cold Fusion troubleshooter who's used CF since 1997, Charlie Arehart is a longtime contributor to the community and recognized Adobe Community Professional.