Designing a profile form for profiles in Quota X, and a different form for profiles in Quota Y
Using Jamroom
researchcooperative:1. If my understanding is correct, from any profile anywhere, we can click into the generic form designer and design fields that will then be listed with a .tpl label.
you can get to the Form Designer from any form's UPDATE or CREATE screen. From there you can add more form fields. The Form Designer has nothing to do with .tpl files which are found in the skins directory or the TEMPLATES tab of the module/skin. I do not understand this part of the question ".....that will then be listed with a .tpl label......"
researchcooperative:2. Where in the system should that .tpl file name be taken to then build a form (i.e. a compiled set of fields) that is specific to profiles in Quota X?
starting to get lost here, .tpl files are found in the skins, eg:
/skins/jrElastic/*
and are also accessable via the ACP at:
ACP -> SKINS -> YOUR SKIN -> TEMPLATES
researchcooperative:3. Can we then repeat the process, and design another form that is specific to profiles in Quota Y?
If you add fields to the form via the Form Designer, then those fields will be accessable along with the other information stored by that form. So if the form is the one for UPDATE on the audio module, wherever you get the audio module item back from the datastore those extra fields will be there too.
If you setup a system where QUOTA A has different fields to QUOTA B and profiles in each of those quotas uploads a new audio file, then each will have different data attached to the item that comes back.
Items are retrieved from the datastore with the {jrCore_list} function.
researchcooperative:4. Can the fields we create for these different forms be displayed separately in different sections of the form designer? Or should we say, use the first 10 lines for fields in one form, and then the next 10 lines for fields in a different form? The field name could also include the destination quota name, to clearly assign the fields for the forms of different quotas.
The Form Designer is only seen by the admin user, you can move the fields up and down to group them, there is no way to show "only the fields that are visible to QUOTA A" in the Form Designer design screen.
Thoughts: If the two forms are really different, I'd probably be thinking of making a separate module for each.
