[Resolved] I have many Toolset WooCommerce fildes that I didnt create

[Author]

Posts

[doronY]

Sure Shane
I just did

[doronY]

I restored the staging site,
Please note that even before the code if I update a product this specific field content will be lost...

[Shane]

Hi Doron,

I suspect you forgot to re-add the admin account that you created.

I've enabled the private fields once more so that you can send them.

Thanks,
Shane

[Shane]

Hi Doron,

I've updated the code and tested it and this below should resolve the issue now.

	$cfgs = get_posts( [ 
	    'post_type' => 'wp-types-group',
	    'post_title' => 'Toolset WooCommerce',
	    'numberposts' => -1
	]);
	  //wp_delete_post( 57358, true ); 
	foreach ( $cfgs as $cfg ){
      if ($cfg->post_title == 'Toolset WooCommerce' )
	  	  wp_delete_post( $cfg->ID, true ); 
	}

I've already ran it on your staging site so the items should be deleted now.

Thanks,
Shane

[doronY]

Thank you
I still have the problem that the content in the filed "פרטים נוספים" is not saved
Did you check it?

[Shane]

Hi Doron,

I did check and saw the issue for you.

However this could be a plugin conflict why the WYSIWYG field isn't saving the data. Even a new field that I created had this issue as well.

Would you mind temporarily disabling all your non-toolset plugins and trying the field again.

Thanks,
Shane

[doronY]

Hi
yes, now I have only toolset and woocommerce plugins activated and it is still not saving the data
You can check it 🙂

[doronY]

also tested it with different Themes, the same problem...

[doronY]

Hi again
So, I now see that this is a known toolset problem that solved on "3.4.14" version
Did you know that problem? we could save 3 days 🙂
so, I update the plugin and it is all good now
thank you
Doron

[Shane]

Hi Doron,

My apologies I hadn't noticed the plugin was outdated at the time. I should've checked the release notes on the update.

My focus was mainly on the Toolset Woocommerce Custom fields.

However i'm happy that all the issues have now been resolved.

Thanks,
Shane

[Shane]

You can go ahead and mark this ticket as resolved.