Item13561: PERL type configuation settings lose their formatting when LocalSite.cfg is saved.

pencil
Priority: Urgent
Current State: Closed
Released In: 2.0.2
Target Release: patch
Applies To: Extension
Component: ConfigurePlugin
Branches: master
Reported By: MichaelDaum
Waiting For: MichaelDaum
Last Change By: GeorgeClark
Perl HASH config items need to preserve a maintainable format. For now things like {FormTypes} are nice in Foswiki.spec but uglified once it made its way to LSC. Every call to configure -save will revert formatting of perl HASHes. There are too many extensions in need of these kind of config items.

-- MichaelDaum - 27 Jul 2015

This was fixed at one point. Regression.

-- GeorgeClark - 27 Jul 2015

Michael, I'm checking in a two-line patch which adds formatting to the configuration, but it doesn't preserve the original formatting. So manually crafted settings will be re-formatted, but they won't be wrapped back together onto a single line. Please check if this is sufficient or if more work is needed.

-- GeorgeClark - 05 Aug 2015

And one other unrelated question... In debugging this I used {FormTypes}. The documentation on that field says it will automatically be changed if new form types are added. I can't find any code where that's done. Is that still true and I missed the code, or is the documentation wrong?
This setting is automatically updated by configure to list all the installed FormField types. If you install an extension that adds new Form Field types, you need to run configure for them to be registered.',

-- GeorgeClark - 05 Aug 2015
 

ItemTemplate edit

Summary PERL type configuation settings lose their formatting when LocalSite.cfg is saved.
ReportedBy MichaelDaum
Codebase 2.0.1, 2.0.0
SVN Range
AppliesTo Extension
Component ConfigurePlugin
Priority Urgent
CurrentState Closed
WaitingFor MichaelDaum
Checkins distro:90dd7ce46dad
TargetRelease patch
ReleasedIn 2.0.2
CheckinsOnBranches master
trunkCheckins
masterCheckins distro:90dd7ce46dad
ItemBranchCheckins
Release01x01Checkins
Topic revision: r6 - 10 Oct 2015, GeorgeClark
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy