Daniel

Hi Anna,
But as you know its essential field in forms. Any planning to add this in future versions?

Thank you

Ok, that’ll have to do. Thanks.

Thanks Lars! I’m going to be spending a bit of time with this later in the afternoon. I’ll share back here on results and/or issues, as I’m certain that this thread will be useful to others too.

Lars & Ben,

Thanks for your help…. I think we’ve clarified the problem somewhat, but still not getting what’s needed here. Here’s the current code:

in Product-edit.php:

			$food_type_value = get_post_meta( $object_id, 'wcv_custom_product_food_type', true );
			$food_type_options = array (  
				'vegan'   => __( 'Vegan', 'wcvendors-pro' ),  
				'vegetarian'   => __( 'Vegetarian', 'wcvendors-pro' ),  
				'raw'      => __( 'Raw', 'wcvendors-pro' ),
				'organic'      => __( 'Organic', 'wcvendors-pro' ),
				'gluten-free'      => __( 'Gluten Free', 'wcvendors-pro' ),	
			); 
			
			WCVendors_Pro_Form_Helper::select( apply_filters( 'wcv_custom_product_food_type', array( 
				'post_id'			=> $object_id, 
				'id' 				=> 'wcv_custom_product_food_type[]', 
				'label'   			=> __( 'Food Type (Select all that apply)', 'wcvendors-pro' ), 
				'placeholder'   	=> __( 'Food Type', 'wcvendors-pro' ), 
				'wrapper_start' 	=> '<div class="all-100">',
				'wrapper_end' 		=> '</div>', 
				'desc_tip'   		=> 'false', 
				'taxonomy'			=> 'food_type',
				'taxonomy_args'		=> array( 'hide_empty'=>false ),
				'custom_attributes' => array( 'multiple' => 'multiple' ),
				'options' 			=> $food_type_options,  
				'value'             => $food_type_value
				) )
			);

and in Functions.php:

// Food Type
add_action('woocommerce_product_meta_start', 'wcv_food_type', 2);
function wcv_food_type() {
    $food_types = get_post_meta( get_the_ID(), 'wcv_custom_product_food_type', true ); // Set the meta key
	// If top level array exists
	foreach ($food_types as $key => $value) : 
		echo 'food_types' . $key . ' => ' . $value . '<br>';
	endforeach;
	echo '<br>';
}

add_action( 'wcv_save_product_meta', 'food_type_save_product_meta', 10, 1 );
function food_type_save_product_meta ( $product_id ) {

	// product meta - usage food type
	if ( isset( $_POST[ 'wcv_custom_food_type' ] ) ) { 

		$food_types = $_POST[ 'wcv_custom_food_type' ];
		print_r( $food_types);

		if ( ! empty( $food_types ) ) {
			foreach ( $food_types as $food_type ) { $food_type = wc_clean( $food_type ); }
			update_post_meta( $product_id, 'wcv_custom_food_type', $food_types ); 
			update_post_meta( $product_id, 'food_type', $food_types ); 
		} else {
			delete_post_meta( $product_id, 'wcv_custom_food_type' );
			delete_post_meta( $product_id, 'food_type' );    
		}
	}    
}			

Here’s what’s being reported in the Product Page:

food_types0 => 30
food_types1 => 29

The code is apparently saving the selected ‘food_type’ taxonomy terms to the ‘wcv_custom_product_food_type’ array variable when the vendor adds the options in the product-edit form, and the numerical array values being echoed on the product page are the ID’s of the taxonomy terms. However, the selected options/tax terms are not actually being added to the product from what I can tell on the back end, or on the product-edit form on reload. The terms are not checked on the ‘food_type’ taxonomy’s metabox in the product/post back end editor after saving. They’re also not appearing in the admin column on the back end woocommerce ‘products’ listing page. So… something is still missing, or maybe 2 things are.

First, I’m suspecting that the option values echoed on the front-end product page should be taxonomy term names, and not their numerical values. The numerical values seem to be what’s being saved as the ‘value’ part of the ‘key/value’ pair, and I’m not sure why. Maybe that’s the whole problem?

Second, perhaps the values are not being passed properly from the ‘wcv_custom_product_food_type’ variable to the actual ‘food_type’ taxonomy?

I’m not sure why, still getting my sea legs with PHP, and probably need some hand holding here.

Thanks!

Ok, the images are failing… trying this link to the public google drive folder.

https://drive.google.com/open?id=0B9L_6DOCutEEOUN6X3l2c3ZaTmM

Thanks Jamie, this is working. I do have another couple of questions however:

1) if I have a field that needs a character limit and is required, how do I do that? Is it possible to make data-rules an array like this:

			WCVendors_Pro_Form_Helper::input( array(  
				 'type'      => 'text',
				 'post_id'   => $object_id, 
				 'id'     => 'wcv_custom_product_language_spoken', 
				 'label'    => __( 'Language Spoken by Staff', 'wcvendors-pro' ), 
				 'placeholder'   => __( 'Language Spoken by Staff', 'wcvendors-pro' ), 
				 'desc_tip'    => 'true', 
				 'description'   => __( 'Language Spoken by Staff', 'wcvendors-pro' ),
				 'custom_attributes' => array( 
				 	'multiple' => 'multiple',
				 	'data-rules' => array (
						'max_length[120]',
						'required'))				  
			) );

I’m testing this now, and it doesn’t seem to be working. It’s not throwing the error for the required field. Let me know how I’d do this, and how I’d specify the errors for both cases.

In a more general sense, is there documentation anywhere on how to set all the options of the input arrays for these fields? I can’t find any reference on this site beyond the single case example in the “Adding a Custom Field for Products” KnowledgeBase article; I’ve spent a couple hours getting familiar with WP form inputs in general, but it looks like WC Vendors & Pro overlay that functionality and have a language of their own. A reference, if it exists would be great to have access to, and if it doesn’t would be a fabulous thing to create and share.

Thanks!

Ok…. mark this one as resolved, simple/stupid answer. We din’t have Screen Options > Custom Fields enabled in the back end product editor. The fields are all there. Hope this helps other people getting lost in the same confusion.

Thanks.