Title:
[atuttle] CF11 Update 5 (beta1) breaks "View Undelivered Mail" feature of CF Administrator
| View in TrackerStatus/Resolution/Reason: Closed/Fixed/
Reporter/Name(from Bugbase): Adam Tuttle / Adam Tuttle (Adam Tuttle)
Created: 03/02/2015
Components: Administrator
Versions: 11.0
Failure Type: Non Functioning
Found In Build/Fixed In Build: CF11_Final /
Priority/Frequency: Critical / All users will encounter
Locale/System: ALL / Platforms All
Vote Count: 1
With Update 5 (beta1) installed, I get a browser alert error alert that reads, "Error retrieving markup for element mailBody : Client verification failure. [Enable debugging by adding 'cfdebug' to your URL parameters to see more information]". After closing the error, the mail viewer screen looks like below:
https://dl.dropboxusercontent.com/u/3831772/cfbug-11u5-undelivered-mail.png
If I downgrade back to Update 4 (official stable release), the errors go away and I can see my undeliverable mail.
---
Additional information provided by Charlie Arehart:
I can confirm Adam's observation (I just hadn't used that feature to have noticed it since applying the update). And I have confirmed I had no errors in applying the update (in the update log, wihch I would always propose people check when they experience errors in the admin or CF after applying an update). I'll assume Adam had none in his also.
And FWIW, I confirmed this on a machine where I had not yet applied update 5 prerelease. Before the update, I could access the "view undelivered email" feature just fine. After the update, I get the same error Adam does. I'll add that (since I have debugging enabled on that machine), I do also see more error info that may help someone:
Client verification failure.
You must have a valid login to access this page.
In seeing that, I wondered if this might be a bigger problem with other features of the admin, or perhaps on doing features that execute upon clicking a submit button in the interface. But I tested the "verify all connections" on the DSN page, and it worked fine. I also did a "clear template cache" operation. So it's not some sort of global failure of the Admin API or something, as might be suggested by the wording of the error.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3947096
External Customer Info:
External Company:
External Customer Name: Adam
External Customer Email:
External Test Config: My Hardware and Environment details:
OSX 10.10.2 (Yosemite), Java 1.7.0_55, Apache 2
Attachments:
Comments: