[Help needed] Conditionally replacing a field for another about cmb2-snippet-library HOT 3 OPEN

I just added a snippet that demonstrates deregistering/re-registering a field to replace an existing one: https://github.com/CMB2/CMB2-Snippet-Library/blob/master/filters-and-actions/cmb2_init_%24cmb_id-replace-field.php

However, you can simply replace attributes for an existing field as well: https://github.com/CMB2/CMB2-Snippet-Library/blob/master/filters-and-actions/cmb2_init_before_hookup-add-fields.php#L10-L14

from cmb2-snippet-library.

As long as you're matching up the meta key, you should be able to save content to the same spot regardless of plugin being used.

For example, the default metabox for custom fields from WP core. Say I create a post and save some fields as _my_meta_field. Then I load up and create a field in CMB2, and specify the field ID to be _my_meta_field. Once I go in to edit that post, the values previously saved would already be filled in to the new CMB2 fields.

I could also edit the same meta field from PHP or some sort of import, and it'd all just take.

The reason I say all this, is that it doesn't necessarily matter how the value is provided, as long as the value saved to the same matching spot. That said though, it depends also on the structure of of the saved data. Simple strings are no issues at all. If one method saves the data as a serialized array, and a different one saves as a string, you'll need to do some type checking and whatnot when it comes time to output to the frontend. Array to string errors aren't always fun :D

from cmb2-snippet-library.

Thanks guys for the responses 👍

@jtsternberg the example you provided on first sight looks like exactly what i need!

from cmb2-snippet-library.