Bug 9176 - Save buttons in syspref editor are not disabled after saving sysprefs
Summary: Save buttons in syspref editor are not disabled after saving sysprefs
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Staff interface (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Owen Leonard
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-29 21:22 UTC by Jared Camins-Esakov
Modified: 2017-12-07 22:15 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jared Camins-Esakov 2012-11-29 21:22:12 UTC
Unlike the other save buttons in the syspref editor, which are disabled when there is nothing to save, the floating save button remains enabled even after all changes have been saved.
Comment 1 Owen Leonard 2013-02-11 19:11:29 UTC
(In reply to comment #0)
> Unlike the other save buttons in the syspref editor, which are disabled when
> there is nothing to save, the floating save button remains enabled even
> after all changes have been saved.

I don't find that other save buttons become disabled after changes have been saved. Can you confirm and post the steps to reproduce?
Comment 2 Jared Camins-Esakov 2013-02-11 19:34:55 UTC
You are right. On master the other save buttons don't get disabled when you save sysprefs anymore, either. I reported the bug against master right after using an older version where that worked. I have updated the subject to reflect that all the save buttons remain active.
Comment 3 Owen Leonard 2013-02-14 13:52:26 UTC
Can you specify the version under which this works as you describe? Or is this an enhancement?
Comment 4 Jared Camins-Esakov 2013-02-14 13:58:20 UTC
(In reply to comment #3)
> Can you specify the version under which this works as you describe? Or is
> this an enhancement?

It did this on 3.6.x, didn't it?
Comment 5 Owen Leonard 2013-02-15 13:27:17 UTC
(In reply to comment #4)
> It did this on 3.6.x, didn't it?

Not in my test.
Comment 6 Jared Camins-Esakov 2013-02-15 13:28:01 UTC
In that case, this is an enhancement.
Comment 7 Aleisha Amohia 2017-02-13 22:42:49 UTC
This has been fixed in the latest version. Setting to Resolved