Bug 999444
Summary: | 'loan settings' not work on edit system page | ||
---|---|---|---|
Product: | [Retired] Beaker | Reporter: | wangjing <jingwang> |
Component: | web UI | Assignee: | Dan Callaghan <dcallagh> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | tools-bugs <tools-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 0.15 | CC: | aigao, asaha, dcallagh, jzhao, qwan, rmancy, tools-bugs |
Target Milestone: | 19.0 | Keywords: | Patch |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-11-25 07:18:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1014438 | ||
Bug Blocks: |
Description
wangjing
2013-08-21 10:34:10 UTC
This problem still exists in 0.15 An acceptable alternative to making it work would be to simply hide the non-functional controls when in the edit view. Including this with the other loan UI cleanups planned for 0.15.1 Normally the problem in this situation, is that the widget is not being returned directly in the controller, or is not a member widget of a widget that is. That explains why it doesn't work in the 'edit' page. It does not explain why it does work in the regular page. It turns out that by some stroke of magic the LoanWidget's resources are being added to the TaskSearchForm widget instance, which is being returned at the top level of the relevant controller method. Ignoring that though, the solution here I think is just to return the LoanWidget instance from the controller as well. Actually no, the correct solution is to make LoanWidget a member widget of SystemForm. Do we need to show the loan widget at all on the edit page? Not necessarily. My only reservation is having some widgets mysteriously removed and others not, and for no other reason other than that's what we decided to do (and then have people raise bugs because they don't know any better) I'd be more happy with removing all widgets that are not directly related to editing a system, or keeping them all. This has been fixed as part of the system page redesign (bug 1014438). https://beaker-project.org/dev/proposals/system-page-improvements.html Beaker 19.0 has been released. |