hide certain settings from the Library Settings Editor

Bug #977382 reported by Jason Etheridge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Triaged
Wishlist
Unassigned

Bug Description

Some functionality is implemented with org unit settings, but have dedicated interfaces for controlling the setting. Two that I can think of are ui.hide_copy_editor_fields and circ.staff_client.do_not_auto_attempt_print. I believe there are others. Trying to edit these from within generic settings editor is sub-optimal. Perhaps we should add a boolean to config.org_unit_setting_type for hiding (or not even retrieving) certain settings within the editor?

Tags: admin-pages
Revision history for this message
Bill Erickson (berick) wrote : Re: [Bug 977382] [NEW] hide certain settings from the Library Settings Editor

On Mon, Apr 09, 2012 at 05:40:42PM -0000, Jason Etheridge wrote:
> Public bug reported:
>
> Some functionality is implemented with org unit settings, but have
> dedicated interfaces for controlling the setting. Two that I can think
> of are ui.hide_copy_editor_fields and
> circ.staff_client.do_not_auto_attempt_print. I believe there are
> others. Trying to edit these from within generic settings editor is
> sub-optimal. Perhaps we should add a boolean to
> config.org_unit_setting_type for hiding (or not even retrieving) certain
> settings within the editor?

Alternatively, we could just avoid fetching any org settings that have
datatype of 'object' or 'array', since (IIRC) they cannot be edited
in the org settings UI anyway. It's less flexible, but is simpler to
implement and may suffice.

-b

--
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: <email address hidden>
| web: http://esilibrary.com
| Equinox Software, Inc. / Your Library's Guide to Open Source

Revision history for this message
Jason Etheridge (phasefx) wrote :

> Alternatively, we could just avoid fetching any org settings that have
> datatype of 'object' or 'array', since (IIRC) they cannot be edited
> in the org settings UI anyway.  It's less flexible, but is simpler to
> implement and may suffice.

In fact, I just tried editing the hide fields setting and the database
value went from

["Fine Level","Floating?"]

to

"Fine Level,Floating?,Loan Duration"

which is horribly wrong. No big explosion in the copy editor, but it
is broken once the setting is thus munged.

Changed in evergreen:
importance: Undecided → Wishlist
Changed in evergreen:
status: New → Incomplete
Changed in evergreen:
status: Incomplete → Triaged
Elaine Hardy (ehardy)
tags: added: wishlist
tags: added: admin-pages
tags: removed: wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.