Bug #49236 Failure to track unapplied changes to configuration file

Description:
When making changes to configuration files, choosing to cancel leaves the changes in the page, but doesn't commit them to the file.  If you click apply again, even without making further changes, you will find that the option selected shows up twice (it is added twice).

How to repeat:
1.  Select a configuration file to edit.
2.  Check "enable named pipes"
3.  Click "Apply"
4.  View the file before confirming.
5.  Click "Cancel"
6.  Click "Apply"
7.  View the file before confirming, note that "enable-named-pipes" is listed twice.
8.  Click "Cancel"
9.  Uncheck "enable named pipes"
10. Click "apply"
11. View file, note that "enable-named-pipes" is still listed

Suggested fix:
Do a better job of tracking changes after canceling updates.

Fixed.

fix confirmed. will be included in 5.2.10

sorry, wrong version information, it will be included in 5.2.11

An entry was added to the 5.2.11 changelog:

In the configuration editor, on the Admin tab, the operation of the Apply and Cancel buttons did not work correctly. If an option was selected, and then Cancel selected in the view changes dialog, and then Apply clicked again, the selected option was incorrectly listed twice in the configuration file.