Michael Beckwith
Michael Beckwith
@rickcurran One thing I'm noticing is that you're using the `text_datetime_timestamp` but your return format isn't taking into account the hours/minutes/seconds details as well. Curious if that's playing its own...
Biggest thing with the format portion is that I believe that's just for the display, since all we're doing is storing a timestamp in the database. For what it's worth...
Curious if we should maybe check for the existence before trying to assign the getRowId variable.
Still need to dig in a little, but it seems like something is failing in the sanitization areas for that field.
In update_data() from CMB2_Field ``` if ( 'options-page' === $a['type'] || empty( $a['id'] ) ) { return cmb2_options( $a['id'] )->update( $a['field_id'], $a['value'], false, $a['single'] ); } ``` `$a['id']` is ending...
@jtsternberg do you have any ideas here regarding this? If you have input, we're all ears at the moment.
Nothing coming to mind why that would cause failure in some way.
We fully support the usage of Carbon Fields if that gets your needs handled and your website goals met. By all means make use of them too.
I'm assuming you saw https://github.com/CMB2/CMB2/wiki/Field-Types#taxonomy_multicheck and it's not meeting what you're hoping for, in this case. Correct?
Just so I'm clear on this, this needs to be unique across ALL posts? Not just unique with the context of ONE post?