Project

General

Profile

Actions

Bug #6903

closed

services_dnsmasq_edit.php: Configuration XML hosts section order appears randomized

Added by Kevin Wojniak about 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Backup / Restore
Target version:
Start date:
11/08/2016
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3.x
Affected Architecture:

Description

Related to #6893 - when I view the diff of the configuration XML after a change to DNS Resolver's Host Overrides section, the <unbound><hosts> entries appear to be randomized when they get written out to the XML. This makes viewing the diff confusing as it shows several lines modified, when in reality only a single change may have taken place.

It would be nice if the order of the XML elements matched the order displayed in the GUI.

Actions #1

Updated by Steve Beaver about 5 years ago

  • Assignee set to Steve Beaver
Actions #2

Updated by Steve Beaver about 5 years ago

  • Subject changed from Configuration XML hosts section order appears randomized to services_dnsmasq_edit.php: Configuration XML hosts section order appears randomized
  • Status changed from New to Feedback

It is certainly not "randomized", but since the two tables may be sorted (by clicking the column headers) the hosts can appear in whichever order you want.

Currently on saving a new override the hosts are sorted alphabetically by host name, so they should always appear in a consistent order when the page is first loaded, and this seems a desirable feature. Of course it also means that if you add a new override and its name begins with 'A', it will be added to the start of the list and all existing hosts will move down one.

A better approach might be to leave the list unsorted on save, but sort it when rendering the display?

A change to that effect has been pushed. Please test in the next snapshot.

Actions #3

Updated by Steve Beaver about 5 years ago

  • % Done changed from 0 to 100
Actions #4

Updated by Steve Beaver about 5 years ago

  • Status changed from Feedback to Resolved
Actions #5

Updated by Jim Pingle almost 5 years ago

  • Target version set to 2.3.3
Actions

Also available in: Atom PDF