Investigate storage of Members configuration in the manifest

[brendo]

Look at storing Members configuration data in the Database so that migration between sections is possible.

I believe the current implementation, as noted by michael, won't work as originally planned.

[nickdunn]

I don't think this is an RC1 requirement, since we agreed this wouldn't be in v1.0. The ability to have multiple sections was a future addition. In case you wanted to put this off ;-)

[brendo]

Yeah, cleared the milestone for now.

The use case of creating another section as a transition for members is pretty rare I would think.

The issue, as Bauhouse discovered, is when saving a section that's defined as the 'Active Members section', the Member field ID's will be written to the configuration. While you can create a second section and fill it with Member fields, the transition between the two sections isn't as simple as changing the Preference. You are then required to resave the Members section.

I suppose now that I've said it, it's not that big of deal, especially considering it's not your everyday task.

Leaving this around as I would like to improve this, though as you say, it's probably something that could be left to when multiple section login is introduced

[brendo]

Fields are no longer stored in the manifest, just the template settings and the active members section.