Univention Bugzilla – Full Text Bug Listing |
Summary: | Wrong protocol shown when opening printer shares | ||
---|---|---|---|
Product: | UCS | Reporter: | Lukas Walter <walter> |
Component: | UMC - Printers | Assignee: | Florian Best <best> |
Status: | CLOSED FIXED | QA Contact: | Dirk Wiesenthal <wiesenthal> |
Severity: | normal | ||
Priority: | P5 | CC: | gohmann, jmm, klaeser |
Version: | UNSTABLE | ||
Target Milestone: | UCS 3.2-0-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
What kind of report is it?: | --- | What type of bug is this?: | --- |
Who will be affected by this bug?: | --- | How will those affected feel about the bug?: | --- |
User Pain: | Enterprise Customer affected?: | ||
School Customer affected?: | ISV affected?: | ||
Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
Ticket number: | Bug group (optional): | ||
Max CVSS v3 score: |
Description
Lukas Walter
2013-11-14 15:12:29 CET
Might be a problem with how UMC handles the PrinterURI complex yntax, which consists of a PrinterProcol and a string syntax. Seems to be working in other modules with other syntaxes. The printer URI used the ComplexInput widget which did not have a setInitialValue method. The printer protocol had a ComboBox widget. When the form values were set, the ComboBox widget did not yet have the possible values loaded from the server (udm/syntax/choices request) when the value was set, so the ComboBox declared the value as invalid. It falled back to the first value (which was cupd-pdf://) when the values were finished loaded. Fixed by adding setInitialValue to ComplexInput which calls setInitialValue for every subtype. YAML: 2013-12-12-univention-management-console-frontend.yaml OK, works. YAML OK |