There is currently an error in the JSON parsing of saved user billing/shipping information on Adobe's My Information page. It causes the busy overlay to remain, preventing interacting with the forms beneath. The symptom of the problem looks like this:
I wanted to get in there and change my email address from firstname.lastname@example.org to email@example.com because I've recently been getting A TON of spam due to my email address being among the 150 million records in the Adobe data breach last November. Of course, I used a strong, unique password before the data was compromised, so I don't have to worry about my credentials on other websites (I recommend 1Password and LastPass if you're still playing loosey-goosey).
At any rate, this is the cause of the busy overlay being stuck on:
Et voila! Now the form can be edited. You will receive an error when an Ajax validation attempt is made: "NetworkError: 404 Not Found - https://firstname.lastname@example.org?_=1393805436151" Apparently, they don't use that account status check anymore. Regardless, the form will save the new email address and allow the verify address link to be visible and clicked.
This is yet another reason I recommend creating a unique email address for every website on which you create an account. Seriously, consider it if you have the ability to run your own mail servers. It's interesting to see when specific vendors leak their user's data -- sometimes before they know of the issue or acknowledge it publicly.
@ 4:22 PM
by Joseph Lamoree
If you use the ORM features (in particular, secondary caching) of Adobe ColdFusion 10 and encountered the bug that prevents application startup with an Ehcache exception including the message "Another CacheManager with same name '_ORM_...' already exists in the same VM", and you used the workaround of downgrading to Ehcache 2.4.7 from the bundled Ehcache 2.5.1 version, then you will experience troubles after applying Adobe ColdFusion 10 HotFix 11 (and subsequent, cumulative patches). The first time ormReload() is called, an exception like the following will be thrown:
Presumably, the old Adobe ColdFusion code didn't call the Ehcache manager in this way, which is now incompatible with Ehcache 2.4.7. The solution is to simply undo the downgrade and run with the version provided by Adobe ColdFusion.
The original bug exists in the Adobe BugBase as #3327626 and #3583147. The ORM secondary cache issue was addressed with changes in the significant ColdFusion 10 Update 11. In a weird sort of meta coincidence, there is a bug in the display of the list of bugs fixed that causes the page to render incompletely. It was just too delicious not to capture.
This Ehcache version incompatibility is probably old news to anybody who has kept current with patches. Adobe ColdFusion Update 11 came out 9 Jul 2013. However, I'm just now seeing the issue because I brought an internal server from update 10 to 13 this weekend. I should also mention that this problem in our environment manifested as a White Screen of Death (no exception display or debugging info). I tracked down the cause by adding the following to Application.cfc:
<cffunction name="onError" returntype="void" access="public" output="false">
<cfargument name="exception" type="any" required="true"/>
<cfargument name="eventName" type="string" required="true"/>
<cfdump var="#arguments.exception#" abort="true"/>
Starting the CFML app with that application error handler in place allowed me to see what was going horribly wrong. Hopefully that's helpful to someone.
@ 11:26 PM
by Joseph Lamoree