You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be a bug with the repeating fields using a custom field type. In this case it's a post field type that displays posts from a few different post types. When the post is saved, it ignores the items that were deleted.
CMB2 in our case is being used as a dedicated plugin that other plugins and theme tap into within our network. The custom filed is in the same php file that loads the init.php from CMB2. Just trying to provide as much context as I can here.
This works with a core field such as textfield_small. however when switched to this custom field type, the odd behavior above is experienced.
The text was updated successfully, but these errors were encountered:
If you would be so kind, could you please open up a support thread over at https://wordpress.org/support/plugin/cmb2. We are trying to keep support on the official plugin page. We'll get you taken care of there, and if we confirm that you have found a bug, we will bring the findings over to GitHub for issue tracking and patching.
There seems to be a bug with the repeating fields using a custom field type. In this case it's a post field type that displays posts from a few different post types. When the post is saved, it ignores the items that were deleted.
Here's a Gist of the mb setup and function:
https://gist.github.com/bearded-avenger/ff479f01bc1bbf24fbf1
Here's a quick screencast of what's going on.
http://cl.ly/151z2Y1y340E
CMB2 in our case is being used as a dedicated plugin that other plugins and theme tap into within our network. The custom filed is in the same php file that loads the init.php from CMB2. Just trying to provide as much context as I can here.
This works with a core field such as textfield_small. however when switched to this custom field type, the odd behavior above is experienced.
The text was updated successfully, but these errors were encountered: