[roger coryell]

Will contact you vis contact link as suggested

[Ryan]

I am trying to add a single field called “Sachem Name” to my connections pro plugin on the website. I have looked at and read all your support, including the docs you have emailed to me and nowhere in there does it say, this is how to create an additional field. I have bought multiple templates and the plugin and have put many hours into this. I simply need instructions on how to create ONE additional field. Does that exist???

[James]

I also need to know how to add a custom text fields.

[James]

Please can someone provide some insight on this. I would think this paid plugin would have offered this. I just want to have a few fields, a couple plain text & a couple with options, that directory members can fill out on their profile. I am completely shocked that this isn’t available.

[ian1119]

This can probably be done using ‘pods’; custom content type and fields from Automattic, See https://wordpress.org/plugins/pods/

I have not tried this approach with Connections but in principal it should work as fields can be added to installed plugins.

Please post back here if you do give this a try to say how you get on.

[James]

Thank you. I will look into that.

Did you ever solve your problem from 2 years ago?

[Jmaes]

This is not resolved. I would like to hear from Steven on this.

[Steven Zahm]

@ Ryan

re: I simply need instructions on how to create ONE additional field. Does that exist???

I just wrote and published a new QuickTip that walks thru how to add a simple text field. This should give you everything you need to add what you need.

Hope that helps!

[Steven Zahm]

@ James

re: Please can someone provide some insight on this. I would think this paid plugin would have offered this. I just want to have a few fields, a couple plain text & a couple with options, that directory members can fill out on their profile. I am completely shocked that this isn’t available.

Actually Connections is a free plugin. Also I am not sure why you would be shocked that a feature does not exist when there is no claim that it does exist outside mentions of an API and references to other extension that use that API which can be used as reference on how to add a custom field in these support forums.

re: I also need to know how to add a custom text fields.

I just posted a new QuickTip oh how to add a simple text field.

You can follow those instructions to add what you need. You mention the need for multiple text fields. The QuickTip only covers adding a single one. This can be very easily changed. This section of code in the QuickTip:

$atts = array(
    'title'    => 'Metabox Name',         // Change this to a name which applies to your project.
    'id'       => 'custom_one',           // Change this so it is unique to you project.
    'context'  => 'normal',
    'priority' => 'core',
    'fields'   => array(
        array(
            'name'       => 'Field Name', // Change this field name to something which applies to you project.
            'show_label' => TRUE,         // Whether or not to display the 'name'. Changing it to false will suppress the name.
            'id'         => 'field_id',   // Change this so it is unique to you project. Each field id MUST be unique.
            'type'       => 'text',       // This is the field type being added.
            'size'       => 'regular',    // This can be changed to one of the following: 'small', 'regular', 'large'
        ),
    ),
);

Here’s how it can be tweaked to add three text fields:

$atts = array(
    'title'    => 'Metabox Name',         // Change this to a name which applies to your project.
    'id'       => 'custom_one',           // Change this so it is unique to you project.
    'context'  => 'normal',
    'priority' => 'core',
    'fields'   => array(
        array(
            'name'       => 'Field Name One', // Change this field name to something which applies to you project.
            'show_label' => TRUE,             // Whether or not to display the 'name'. Changing it to false will suppress the name.
            'id'         => 'field_id_1',     // Change this so it is unique to you project. Each field id MUST be unique.
            'type'       => 'text',           // This is the field type being added.
            'size'       => 'regular',        // This can be changed to one of the following: 'small', 'regular', 'large'
        ),
        array(
            'name'       => 'Field Name Two', // Change this field name to something which applies to you project.
            'show_label' => TRUE,             // Whether or not to display the 'name'. Changing it to false will suppress the name.
            'id'         => 'field_id_2',     // Change this so it is unique to you project. Each field id MUST be unique.
            'type'       => 'text',           // This is the field type being added.
            'size'       => 'regular',        // This can be changed to one of the following: 'small', 'regular', 'large'
        ),
        array(
            'name'       => 'Field Name Three', // Change this field name to something which applies to you project.
            'show_label' => TRUE,               // Whether or not to display the 'name'. Changing it to false will suppress the name.
            'id'         => 'field_id_3',       // Change this so it is unique to you project. Each field id MUST be unique.
            'type'       => 'text',             // This is the field type being added.
            'size'       => 'regular',          // This can be changed to one of the following: 'small', 'regular', 'large'
        ),
    ),
);

As you see, you duplicate the one section over and over the amount of fields that you need.

[Steven Zahm]

@ ian1119

No Pods will not work for this because Connections does not use a custom post type (CPT) to store its data. Two reasons. The first is that Connections is older than the CPT feature. The second is that Connections uses a db schema optimized for directories. The CPT schema is optimized for post like data. Granted other direct plugins do do use a CPT. There’s trade offs and benefits for either method.

[Author]

Posts