This is an old revision of the document!
Under Construction.
Setting up Fields for the Community Builder integration.
Before you can properly and fully integrate Community Builder with our supported extensions, you have to create and set up a couple of fields which will be mapped to our extension's user profile.
To create new Community Builder fields go to your site backend → Community Builder → Field Management.
Here you can create unlimited fields for your CB user profile, some of these fields will have to be mapped into our extension with their respective counterparts.
The role of this mapping is to tell our extensions which fields from CB will reflect the component fields, in order to load that data in the item listings, item details, some payment items, and even modules.
Most of the fields that you have to create will be of type "Text Field" since these are the fields we use on the component user profiles.
Let's go through the most common fields you will have to map and their CB counterpart.
| Component Field | CB Field Type | Info |
|---|---|---|
| Name | Text Field | |
| Surname | Text Field | |
| Address | Text Field, Area, or Editor | You can set multiple types for this field, according to how much freedom you want to give to the user. |
| City | Text Field, Drop Down(Single Select) | You can either let the user input a city, or provide him with a predefined list with the Drop Down field. |
| Country | Text Field, Drop Down(Single Select) | Same as City |
| Phone | Text Field | It's indicated that you also set a numeric filter in the Validation tab for this field. |
| Paypal | Text Field | |
| Google Maps X | Text Field | |
| Google Maps Y | Text Field | |
| Verified | Checkbox | This field should not be shown to the actual user. This should be set by the admin from the CB user profile. |
| Powerseller | Checkbox | Same as Verified |
| isBidder | Checkbox | Same as Verified |
| isSeller | Checkbox | Same as Verified |
Please do not take these field assignments trivially if using the CB integration. Failing to assign them to adequate field types, or mapping them to existing CB fields which store other data than what you are trying to map, may lead to errors or inconsistent behaviour.