Project

General

Profile

Actions
Copy link

Bug #6893

closed

Configuration XML is inconsistent with self closing tags

Added by Kevin Wojniak over 7 years ago. Updated about 7 years ago.

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

100%

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

Description

Whenever I make changes I do "Download configuration as XML" and store the file in a git repository, so I always view the diff of what's changed. Very often, tags that are empty don't always generate the same output.

For example, the <shaper> element was:

<shaper>
</shaper>

but now it's:

<shaper/>

Files

config_diff.png (114 KB) config_diff.png Kevin Wojniak, 11/04/2016 10:14 AM
Actions
Copy link
 #1

Updated by Kevin Wojniak over 7 years ago

Here's another example. I only deleted some L2TP users, but the XML has changed for these values (screenshot from SourceTree).

Actions
Copy link
 #2

Updated by Jim Thompson over 7 years ago

  • Assignee set to Anonymous
Actions
Copy link
 #3

Updated by Anonymous over 7 years ago

  • Status changed from New to Feedback

Null configuration settings are now written as <tag></tag> instead of <tag /> for consistency

Actions
Copy link
 #4

Updated by Anonymous over 7 years ago

  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by Kevin Wojniak over 7 years ago

Awesome, thanks for the quick fix!

Actions
Copy link
 #6

Updated by Anonymous over 7 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #7

Updated by Jim Pingle about 7 years ago

  • Target version set to 2.3.3
Actions
Copy link

Also available in: Atom PDF