Bug 501523
Summary: | Allow user-definable default setting for Sections field other than "Summary" | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | Gary Case <gcase> | ||||
Component: | Hardware Catalog | Assignee: | Pengfei Xue <pxue> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5.3 | CC: | pxue, rlandry, tfu, wshen | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-04-20 02:38:16 UTC | Type: | --- | ||||
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: | |||||||
Bug Blocks: | 807440 | ||||||
Attachments: |
|
Description
Gary Case
2009-05-19 15:06:34 UTC
Gary, can you take a look @ the catalog extension beta. The behavior is different there which may impact your requirements. Created attachment 559556 [details]
patch for tabs
(In reply to comment #4) > Created attachment 559556 [details] > patch for tabs Maybe I'm not reading the patch correctly but I don't follow how this change allows for user selectable persistent showall? (In reply to comment #5) > (In reply to comment #4) > > Created attachment 559556 [details] > > patch for tabs > > Maybe I'm not reading the patch correctly but I don't follow how this change > allows for user selectable persistent showall? This change doesn't persistent user's preference, it will keep the choice, e.g. showall, after user saves current changes. if we need to store preference persistently, we should change the db, add a new table for this. or we can alter table xmlrpc_login_cookies adding a new field and store the preference again after login cookie expired (In reply to comment #6) > if we need to store preference persistently, we should change the db, add a new > table for this. or we can alter table xmlrpc_login_cookies adding a new field > and store the preference again after login cookie expired We shouldn't need to change any tables. I think a cookie would be fine. In order for showall to work using the login cookie the user must first make an update to the cert. Steps to reproduce: 1. open web2/show.cgi?id= 2. select showall 3. open web2/show.cgi?id=731218 in a new tab 4. still on summary tab adding step 1a. select save changes 4. to on show all. This is a bit of a goofy user experience but I think we can go with it. If the user stays with tab view they won't see a change. If the user goes with showall, at some point they are likely to do an update with show all and from then on the desired default is set. (In reply to comment #13) > In order for showall to work using the login cookie the user must first make an > update to the cert. > > Steps to reproduce: > 1. open web2/show.cgi?id= > 2. select showall > 3. open web2/show.cgi?id=731218 in a new tab > 4. still on summary tab > > adding step > 1a. select save changes 4. to on show all. > > This is a bit of a goofy user experience but I think we can go with it. yes, we need 'save changes' to make tab selection work, we are not using ajax, so, that's expected. verified on web2 verified on partner |