Forum Replies Created

  • I found another option, you can add to‘core/editor’) meta that isn’t saved and can be sorta a transient between blocks.

    Register a meta field to a post type and then use dispatch to save data. The interesting thing about this is you don’t need to save it to database as Gutenberg editor has an in memory data store for meta until you actually hit the save button.

    			'auth_callback'     => function() {
    				return current_user_can( 'edit_posts' );
    			'sanitize_callback' => 'sanitize_text_field',
    			'show_in_rest'      => true,
    			'single'            => true,
    			'type'              => 'string',
    'core/editor').editPost({meta: {acf_sync: JSON.stringify(sync)}});
    const meta ='core/editor').getEditedPostAttribute('meta').acf_sync;
  • Well, I think I found a solution to this in the most Gutenberg way possible.

    Set block template javascript variable in the template, then read that variable instead of relying on“core/block-editor”).

    Since Gutenberg is all about saving the data into the html this seemed like the best way to get field data from other blocks.

    // Dynamic block ID.
    $block_id = 'repeater-' . $block['id'];
    $blockClasses = implode( ' ', array( $block['className'] ) );
    $per_page = get_field( 'per_page' );
    $allowed_blocks = array( 'acf/card' );
    <div id="<?php echo $block_id; ?>" class="<?php echo $blockClasses; ?>">
    	<InnerBlocks templateLock="false" allowedBlocks="<?php echo esc_attr( wp_json_encode( $allowed_blocks ) ); ?>"/>
    <div class="items-repeat"></div>
    	var <?php echo $block['id']; ?> = {
    	   'per_page': <?php echo $per_page; ?>

    Then in my javascript onchange I can get the block / field from the variable


Viewing 3 posts - 1 through 3 (of 3 total)