Linking ACF Select with Forminator Select Field

Hi @markclifford,

Trust you are doing good and thank you for reaching out to us.

I assume that you are looking forward to populating the select fields with posts from the custom post type, please correct me if I am wrong. Can you please check if the following code snippet helps?

<?php

add_filter(
	'forminator_cform_render_fields',
	function( $wrappers, $model_id ) {
		if( $model_id != 361 ){
			return $wrappers;
		}

		$select_fields_data = array(
			'select-1' => 'post',
		);

		foreach ( $wrappers as $wrapper_key => $wrapper ) {
			if ( ! isset( $wrapper[ 'fields' ] ) ) {
				continue;
			}

			if ( 
				isset( $select_fields_data[ $wrapper[ 'fields' ][ 0 ][ 'element_id' ] ] ) &&
				! empty( $select_fields_data[ $wrapper[ 'fields' ][ 0 ][ 'element_id' ] ] )
			) {
				$posts = get_posts( array( 'post_type' => $select_fields_data[ $wrapper[ 'fields' ][ 0 ][ 'element_id' ] ] ) );

				if ( ! empty( $posts ) ) {
					$new_options = array();
					$opt_data = array();
					foreach( $posts as $post ) {
						$new_options[] = array(
							'label' => $post->post_title,
							'value' => $post->post_title,
							'limit' => '',
							'key'   => forminator_unique_key(),
						);
						$opt_data['options'] = $new_options;
					}
					$select_field = Forminator_API::get_form_field( $model_id, $wrapper['fields'][0]['element_id'], true );
					if( $select_field ){
						if( $select_field['options'][0]['label'] != $opt_data['options'][0]['label'] ){
							Forminator_API::update_form_field( $model_id, $wrapper['fields'][0]['element_id'], $opt_data );
							$wrappers[ $wrapper_key ][ 'fields' ][ 0 ][ 'options' ] = $new_options;
						}
					}
				}
			}
		}

		return $wrappers;
	},
	10,
	2
);

add_filter(
	'forminator_replace_form_data', 
	function( $content, $data, $fields ) {
		if( $data['form_id'] != 361 ){
			return $content;
		}

		if ( ! empty( $content ) ) {
			return $content;
		}

		$form_fields = Forminator_API::get_form_fields( $data['form_id'] );
		$data_field = '';
		foreach($data as $key => $value){
	    	if ( strpos( $key, 'select' ) !== false ) {
	    		$values = '';
	    		$field_value = isset( $data[ $key ] ) ? $data[ $key ] : null;

		    	if ( ! is_null( $field_value ) ) {
		    		$fields_slugs  = wp_list_pluck( $form_fields, 'slug' );
					$field_key     = array_search( $key, $fields_slugs, true );
					$field_options = false !== $field_key && ! empty( $form_fields[ $field_key ]->raw['options'] )
							? wp_list_pluck( $form_fields[ $field_key ]->options, 'label', 'value' )
							: array();

					if ( ! isset( $field_options[ $field_value ] ) && isset( $_POST[ $key ] ) ) {
						return sanitize_text_field( $_POST[ $key ] );
					}
				}
			}
		}
	    return $content;
	},
	10,
	3
);

Please note, you need to update the form ID (361) in the above code and replace the posts from the following line with your custom post type.

'select-1' => 'post',

Please test the code using a dev/staging environment before pushing it to the live website. The code could be added using a mu-plugin, please find more details here: https://wpmudev.com/docs/using-wordpress/installing-wordpress-plugins/#installing-mu-plugins

Please feel free to get back to us if you need any further clarification.

Kind Regards,
Nebu John

Hi @markclifford

Unfortunately, I don’t have this theme to test the code/form with it (as it’s a third-party premium theme) but it certainly is not correct behavior of the page and the query should not show up on page.

It actually looks like some kind of syntax error, because the code is thrown directly to the page (printed out) instead of being executed.

That said:

1. I understand that if you remove the code that my colleague shared – the issue goes away, right?

2. to make sure – the issue is happening “right away” when you visit the page with the form or after you attempt to submit the form only?

3. could you share screenshot of the entire custom code (the one we shared but after your modifications – “as is”, how you added it)? Also, did you add it as MU plugin or, by any chance, put in theme’s functions PHP file or some kind of theme’s “custom code” Option?

Kind regards,
Adam

Hi @markclifford,

I hope you are doing well today!

Please share the code as text instead of images, also it would be great if you can share an export of the form which will help us more.

You can find more info on how to export the form here : https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#import-export

After exporting, please share the form code using a service such as https://pastebin.com which is free to use.

Please always make sure to use such service to share the codes and don’t post the code here directly as it will most likely be unusable.

Kind regards,
Zafer

Hi @markclifford,

In the given code, I see you are using the following:

$select_fields_data = array(
			'select-1' => 'categories',
		);

The above usage isn’t correct. So just to be sure that we understand the workflow you have.

The Nominee is a custom post type and it has a category called “Awards”? And you want to list all the Awards categories in the Forms Select field, right?

How is the Nominee post type created? Is that part of the theme, custom code or plugin? Could you also please share a screenshot of the mentioned post types you have on your side so that we could have a better idea?

Also please share the URL of the pages of the Nominee post type and the category page ie the URL after /wp-admin/ in your WP Dashboard, so that it would help us to determine the correct slugs that needs to be used in the code.

Looking forward to your response.

Kind Regards,

Nithin

Hi @markclifford

I hope you are doing well.

Let me explain how it works because it is a 2-steps solution.

First of all, we need to create our Select field in Forminator with the options, the shared code will do that for you dynamically, it will list all the Categories into that Select removing the need to manually update the form if you add or remove any new category.

But this is optional, I imported your field and I can see you are adding the options manually.

The second part is the mapping itself, Forminator has out-of-the-box mapping with custom fields which will work with ACF, for example, input, textarea or others, but some complex relationships may require a code.

I tried to duplicate this behaviour on my lab site and I can confirm the mapping will work well with some updates on your form.

– Edit the Post data, map the select and your ACF Field:

https://monosnap.com/file/deKRvDZdd2QOt2Md3XKEjOgVHCVAgV

Make sure the first field matches the ACF field name.
Edit your Select Field, use the Value the Post item ID:

https://monosnap.com/file/oHmrcAENSBznJ3qH1XcEBATMy3bIi0
https://monosnap.com/file/f1XI8WngQONGA7OKFxovGKBdu0kYel

Now it will work out of the box:

https://monosnap.com/file/cE6VyH7zSgPj4WwwxiumavLLlfnIaU

With the first shared code, you can make it more dynamic but also requires an update on

$new_options[] = array(
 ...
'value' => $post->post_title,
....

To

$new_options[] = array(
 ...
'value' => $post->ID,
....

Because the Post ID is which will do the mapping.

Let us know if you have any additional questions.

Best Regards
Patrick Freitas

Hi @markclifford

Please replace this line in code

$posts = get_posts( array( 'post_type' => $select_fields_data[ $wrapper[ 'fields' ][ 0 ][ 'element_id' ] ] ) );

with this code

$p_args = array(
	'post_type' =>  $select_fields_data[ $wrapper[ 'fields' ][ 0 ][ 'element_id' ] ],
	'numberposts' => -1,
);

$posts = get_posts( $p_args );

The difference is that the original line uses get_post with no post number specified so it will always follow current site settings or whatever other code custom-set post number “meanwhile”.

The new version specifically sets number of posts to -1 value which means “all posts”.

Kind regards,
Adam