Univention Bugzilla – Full Text Bug Listing |
Summary: | Extended Option not possible for UDM objects not having at least one UDM Option already. | ||
---|---|---|---|
Product: | UCS | Reporter: | Janis Meybohm <meybohm> |
Component: | UDM (Generic) | Assignee: | UMC maintainers <umc-maintainers> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | P5 | CC: | best, geerds, gohmann, hahn, klaeser |
Version: | UCS 4.1 | ||
Target Milestone: | UCS 3.2-x | ||
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
Janis Meybohm
2012-11-02 12:25:46 CET
For a different bug I did some research for options: It looks like they were later added to UDM, since the option-concept is optional: In object.__init__() self.options and self.oldoptions must be initializied manually to []. Only if those instance variables exists, does the core UDM code in univention.admin.handlers detect options, enable the [Option] tab and does all the magic stuff. Since there is no hook for running code after creation, adding options to a UDM modules not having options initially does not work. Currently it only works for modules having at least one option already. |