Bug 5221 - Preselect tab containing itemtype/authorized value image in use
Summary: Preselect tab containing itemtype/authorized value image in use
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: System Administration (show other bugs)
Version: Main
Hardware: All All
: PATCH-Sent (DO NOT USE) minor (vote)
Assignee: Owen Leonard
QA Contact: Bugs List
URL: /cgi-bin/koha/admin/itemtypes.pl?op=a...
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-14 19:15 UTC by Owen Leonard
Modified: 2010-11-30 15:54 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Example screenshot (9.59 KB, image/png)
2010-09-14 19:15 UTC, Owen Leonard
Details
Proposed fix (4.71 KB, patch)
2010-09-15 12:51 UTC, Owen Leonard
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Owen Leonard 2010-09-14 19:15:07 UTC
Created attachment 2624 [details]
Example screenshot

When editing the details of an itemtype or authorized value the user is presented with a set of tabs containing the various icon sets. If you have previously chosen an icon for the record you're editing the interface should preselect the tab it's on.
Comment 1 Owen Leonard 2010-09-15 12:51:57 UTC
Created attachment 2626 [details] [review]
Proposed fix
Comment 2 Chris Cormack 2010-11-01 22:22:27 UTC
Pushed, please test on master and close
Comment 3 MJ Ray (software.coop) 2010-11-10 08:49:12 UTC
This bug is mentioned in:
Fix for Bug 5221 - Preselect	tab containing itemtype/authval image in use http://lists.koha-community.org/pipermail/koha-patches/2010-October/012735.html
Comment 4 Chris Nighswonger 2010-11-18 03:15:09 UTC
This bug has a patch presently committed to HEAD and 3.2.x.

Please take the appropriate action to update the status of this bug.

Remember, bugs which have been resolved should be tested and marked closed, preferably by the original reporter.
Comment 5 Chris Nighswonger 2010-11-30 15:54:45 UTC
A fix for this bug has been committed to the current development HEAD as well as released in 3.2.1.