Repeater field meta with ackward encoding?

Hey.

We always make this encoding for complex fields. It was from the first plugin version because of conflicts with the editor validator, which marks a block as broken when you reload the editor page. https://github.com/nk-crew/lazy-blocks/blob/bde3082f739fdc112ce775668f104e51b7a37fec/controls/repeater/index.php#L107

The same value is saved in the Meta and in the block attribute. This is why we created a special function to get the meta value get_lzb_meta https://github.com/nk-crew/lazy-blocks/blob/122bec9ebd8aac9f6b42b0088c6f617e36166f5c/lazy-blocks.php#L345

Regards, nK.

Hi,

So, this is expected?

I’m having an issue where those values aren’t being updated, I was wondering if it was something with this.

Thanks.

Also, doesn’t this make this fields less compatible with other plugins (or code) that are fetching that data?

Thanks.

Yes, this is expected. 3rd parties can use this meta value, but this value needs to be encoded first. For example:

<?php

/* Use get_post_meta */
$meta_val = get_post_meta(get_the_ID(), 'steps', true);

if ( $meta_val ) {
  $meta_val = json_decode( rawurldecode( $meta_val ), true );

  var_dump($meta_val);
}

/* Use get_lzb_meta */
$meta_val = get_lzb_meta('steps');
var_dump($meta_val);

Our function will also look at the registered block controls and prepare proper values.

But if you have problem with updating this field when change block attributes, this sounds like a bug. This is how look the repeater control value in the block attribute (not meta) – https://shot.nkdev.info/VbpK6Dc3hz9xBx57Ns2k

Can you export your block to JSON, so I can test it locally?

Yes, definitely doesn’t look like that:

<!-- wp:lazyblock/curso-datas {"lazyblock":{"slug":"lazyblock/curso-datas"},"blockId":"10Nqd6","blockUniqueClass":"lazyblock-curso-datas-10Nqd6"} /-->

JSON export of that specific block.

Thanks.

• This reply was modified 1 year, 8 months ago by Alvaro Gois dos Santos.

My example was for the block, which is not used Meta control, I wanted to show you an example with repeater control, in which value is encoded. The same happens with Meta controls, but these controls save data to the post meta instead of block attributes.

I have also checked your JSON and the block is working correctly.

• https://shot.nkdev.info/kcC1JSpqJj4VPxKMsscn
• https://shot.nkdev.info/9lN8ZLbg8jt7wyjg9Pvp

So I have to look elsewhere. I do sometimes see an odd admin notification about JavaScript not being active, which is false. I wonder what’s blocking the whole post from updating?

Gutenberg seems yet too capricious.

Thanks.