|
| Summary: | [Chameleon] Proper Buttonizer Error Reporting | ||
|---|---|---|---|
| Product: | Chameleon | Reporter: | Chris Thorne <cthorne@dmsolutions.ca> |
| Component: | Core | Assignee: | chameleon-dev <chameleon-dev@lists.maptools.org> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 1.99 | ||
| Target Milestone: | 2.0 Final | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
this would be nice to fix for 1.99 ... the buttonizer still spits out ominous looking php error messages whenever an image isn't found or something isn't set right.
Changed Target Milestone to 1.99 Final
Has anything been don with this bug even though this is targeted for 1.99 Final?
nope
I think that pretty much all error conditions that can occur in buttonizer are now trapped and reported through the error manager.
Darren's Comment: Issue noticed during cwc2 1.0.3 training course. > 2. Error messages from Buttonizer (like problems loading fonts/images) > need to be suppressed. > I am not sure what the issue is here. I am not sure if we need to suppress the Buttonizer Errors, or rather we need to address the issue of proper error messages for the Buttonizer. Making Buttonizer smarter, so that the user does not have to be. ;) Is this what you mean by your above comment, Darren? In any case, Buttonizer should validate and report any issues with the parameter's Buttonizer uses. The current buttonizer error are very cryptic