Bug #32013 Edit log level popup broken
Submitted: 1 Nov 2007 0:16 Modified: 15 May 2008 2:44
Reporter: Joshua Ganderson Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Web Severity:S3 (Non-critical)
Version:2.0 OS:Any
Assigned to: Joshua Ganderson CPU Architecture:Any

[1 Nov 2007 0:16] Joshua Ganderson
Description:
Popup fails to load due to bad data sent for instantiation. Reports the following error "A non-numeric value was submitted for the field "threshold". Either the submission was broken or you have accessed this resource improperly."

How to repeat:
Try to edit a log level.

Suggested fix:
Send up the correct key.
[1 Nov 2007 15:02] Sloan Childers
r7929 fixed in development-1.2.1 branch
[9 Nov 2007 1:59] Bill Weber
Verified fixed in version 1.3.0.8022.
[17 Nov 2007 18:56] Sloan Childers
Fixed in 1.3, reopening to fix in 2.0
[2 Feb 2008 0:02] Joshua Ganderson
problem that caused this does not seem to be present in 2.0. However, we may change the way we work with logs in such a way that this will be a problem. Keeping this open for further investigation.
[19 Mar 2008 18:41] Joshua Ganderson
Things appear to be correct in the 2.0 internationalized branch. Will set to qa-testing after merged back into trunk.
[9 Apr 2008 17:35] Bill Weber
i don't see this in build 2.0.0.6011
[15 May 2008 2:44] Paul DuBois
Noted in 1.3, 2.0 changelogs.

The popup for editing log levels failed to load due to bad
instantiation data.