Form Designer gets stuff into the datastore.
Templates get stuff out of the datstore.
Just adding a new field to a form is only half the job.
researchcooperative:....Are there any examples of Jamroom sites where the profile forms ARE displayed for public view, and are also used as the base for profile searching?....
Here on jamroom.net perhaps, you can search here for profiles:
https://www.jamroom.net/profile
If your wanting to add other fields other than the default ones to be searched, the template controlling that page is found at:
ACP -> PROFILES -> USER PROFILES -> TEMPLATES -> index.tpl -> MODIFY
You'll see this line:
{jrSearch_module_form fields="profile_name,profile_url"}
The fields are the fields that are searched.
If your not using that module specific search, but rather the site-wide one, then you can add in Additional Search Fields into:
ACP -> LISTING -> SEARCH -> GLOBAL CONFIG -> Additional Search Fields
Quote: If you would like to have additional DataStore fields available for search, enter the DataStore field name, one per line.
Example:
If you have created a custom User Profiles field via the Form Designer called "profile_location" you would enter profile_location on a line by itself to enable that field to be searched.
researchcooperative:.....At this stage, I just need to see how a profile form can be made public,....
If your talking about the
form then there is nowhere. The profile
form (the input location where people type stuff in and submit it) is only shown to someone who has a profile. You can only see forms that belong to your profile.
If your talking about displaying some information that was collected via a profile form out to the screen, that can be done in a template in the skin.
The simplest version would be a file created at:
/skins/(YOUR SKIN)/
some-name.tpl
{jrCore_list module="jrProfile"}
That would appear in the browser to anyone who visited the url:
your-site.com/
some-name
The would see a list of profiles formatted in the default layout. The default layout is provided by the item_list.tpl file from the module.
so in the case of a profile thats:
/modules/jrProfile/templates/item_list.tpl
That is a naming convention, there are others.
item_detail.tpl = the main details page found on the profile
item_list.tpl = the formatting of the item in a list
item_action.tpl = the way it looks in the activity timeline
index.tpl = the main module list found at the base module url, eg your-site.com/profile
To over-ride any of those templates at skin level, you can copy it from:
/modules/jrProfile/templates/item_list.tpl
to
/skins/(YOUR SKIN)/jrProfile_item_list.tpl
and it will be over-ridden in all locations.
"Altering a Module's Template"
https://www.jamroom.net/the-jamroom-network/documentation/development/1051/altering-a-modules-template
Alternatively if you dont want to over-ride
all locations with a new custom layout for the list template, you can provide one for just that particular location.
eg:
{jrCore_list module="jrProfile" template="custom-row-template.tpl"}
(call it whatever you like)
To get a base structure for that template layout, its a good idea to copy the default one from:
/modules/jrProfile/templates/item_list.tpl
to
/skins/(YOUR SKIN)/custom-row-template.tpl
Then make alterations. Any alterations will then ONLY effect that location that asks to use the template "custom-row-template.tpl".
If you want to know what variables you have available to you to use other than the ones that are listed in the default version of item_list.tpl, then you put in {debug} into that template and you can use any of the variables that are in there.
"{debug}"
https://www.jamroom.net/the-jamroom-network/documentation/development/1477/debug
The way the values for those variables get to being available in that {debug} dialog is because they got entered in via the Form Designer.
updated by @michael: 04/07/15 11:54:53PM