Meta Box

Hi Long,
Thanks for your reply! Yes, live editing would be the whole point, but since that's not possible due to the nature of MB Blocks -- storing everything on server side and having to parse through a PHP template rather than updating everything through JS -- a quick workaround to this issue would be greatly appreciated.

Please note WP core blocks don't have this issue:
- in these you can enter custom text inline, on the editor side and not on the side, without triggering any Ajax
- Also, the WP blocks "range" system, i.e. on the paragraph typography option, does not call Ajax if you change a value
- finally, the built-in colour picker doesn't let you fine-tune colours so you don't end up changing it multiple times just to get to the colour you want. And even the colour change won't trigger Ajax.

So they managed to avoid this issue completely, I assume by assigning the appropriate classes to blocks via JS instead of parsing everything on the back end on every change.

Since at the end of the day most changes are made through classes, perhaps some options can be added to the fields to determine if the change of the field needs to fire Ajax or to just toggle some class to a specific part of the HTML? It sounds complicated, but it looks like WP Core is doing it so there should be a way to achieve this.

But that's for later. I think as a quick fix, a delay to Ajax would solve the most immediate performance issue.

Thanks for your work!
Mauro.

Hello there, this is still an issue. Here are some more details shared by a fellow developer:

PHP Notice: Undefined index: to in /home/XYZ.cloudwaysapps.com/XYZ/public_html/wp-content/plugins/meta-box-aio/vendor/meta-box/mb-relationships/inc/query/normalizer.php on line 82

WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near...

/**
 * Normalizes single relationship query arguments.
 *
 * @param array $args Query arguments.
 */
protected function normalize_args( $args ) {
    $direction    = isset( $args['from'] ) ? 'from' : 'to';
    $relationship = $this->factory->get( $args['id'] );

    $args['id_field']   = $relationship->get_db_field( $direction );
    $args['direction']  = $direction;
    $args['items']      = $this->get_ids( $args[ $direction ], $args['id_field'] );
    $args['reciprocal'] = $relationship->reciprocal;

    unset( $args[ $direction ] );
    return $args;
}

Sometimes the $args array doesn’t have a ‘to’ key. That’s where the php warning comes from. It's possible to fix the php warning by verifying if the ‘to’ key exists. If it’s missing, you can create it manually. This solution is not the best one because it fixes the PHP warning but it doesn’t fix the database error.

/**
     * Normalizes single relationship query arguments.
     *
     * @param array $args Query arguments.
     */
    protected function normalize_args( $args ) {
        $direction    = isset( $args['from'] ) ? 'from' : 'to';
        $relationship = $this->factory->get( $args['id'] );

$args['id_field']   = $relationship->get_db_field( $direction );
$args['direction']  = $direction;
if(!isset($args['to']))
{
    $args['to'] = null;
}
$args['items']      = $this->get_ids( $args[ $direction ], $args['id_field'] );
$args['reciprocal'] = $relationship->reciprocal;

unset( $args[ $direction ] );
return $args;
}

Hello Anh, revisiting this, is latitude and longitude binding possible now?
I'd also need to have zoom level exposed.
Please let me know, I now need this urgently.

Oh almost forgot! The code that defines relationships is in:
wp-content/plugins/mundana-itineraries/classes/MundanaItineraries_MetaBoxes.php on line 258 (function register_relationships).

The code that retrieves data is in the same directory, in the file MundanaItineraries.php on line 495 (method get_related_to) and 527 (method get_related_from).

In the theme this is used in several places, here is an example:
wp-content/themes/mundana/template-parts/content-hotel.php

I'm missing something too!
I tried adding other blocks and the wpautop is applied to them as well, so this is not an issue with MetaBox. I also tried changing the theme so it's not an issue with the theme.

I guess it's a problem introduced by one of the other plugins.
I managed to solve this bypassing the_content and loading the blocks like this:

if ( has_blocks( $post->post_content ) ) {
    $blocks = parse_blocks( $post->post_content );
    foreach( $blocks as $block ) {
        echo render_block( $block );
    }
}

Thanks for looking into this Anh, your help is precious and always appreciated!
M.