not sure the PR that's supposed to fix it is merged, I'll let you know later today

already did it, didn't solve the issue

alright, thanks

Hey all, I've followed this gist to the T in order to create a custom form field --- I've got the field rendering correctly, but I'm finding that the value is not persisting when I save. I've checked Vuex and it doesn't appear to be propagating the value there via the

@push('vuexStore')

call mentioned in the gist. Any thoughts on why that might be? https://gist.github.com/pboivin/19d49cbb3c0a6c5c06469117597cc0f7

The only thing I could think of is that the

in-store="value"

property needs to be the field name, but I tried that with the same results

I've tried outputting it on the front as well via the

$block

object but it's not serialized in the content field

Hi @tfilos, since your field is used in a block, did you make sure to use the fieldName mixin?

if you dont mind sharing your code, it'd be helpful to review

I actually did not --- I have everything in gists, no problem. I reckon this is the most pertinent: https://gist.github.com/paperscissors/c2e9546a97da441301ca803d08889f51

And the field blade for context: https://gist.github.com/paperscissors/576455144a7a1fd73cca644ef67878d4

But no, I didn't use that mixin so that may very well be the problem.

the name of the field needs to be dynamic depending on which blocks its in, so you should use the name prop from your blade

You know, I did have a name prop set in the blade file but I was getting an error about "name" component not existing

Okay, added that in --- still isn't saving, though

are you passing a name when using the field in your block, and did you update the component to use the name prop as the name of the radio input that is driving your component?

Aha, I am not currently passing the name to the radio button name. Will do. I had assumed that the binding would be sufficient there.

I've got that in place, still not saving though. Will dump the content field just to double check

Yeah, still not showing up there

Name value is showing up as

blocks[154][deck_theme]

if I output that, so the name is coming through

Not seeing that name in the Vuex fields array though

are you sure this line is executed? https://gist.github.com/paperscissors/c2e9546a97da441301ca803d08889f51#file-decktheme-vue-L53

I would look at the color field to understand what you did differently. Can you share the updated Vue component ?

Looks like the

updateValue

method is not being called at all

Yes definitely, I'll share and compare the rest of the color field. This stuff I copied from that other gist, but maybe there are differences

your onblur method is not called by anything

your input radio doesn't run any code on change currently, you need to bind an event to it, or watch v-model changes