Meta Field Block

Description

This single-block plugin allows you to display a meta field or a custom field as a block on the front end. It supports custom fields for posts, terms, and users. It can be nested inside a parent block that has postId and postType context, such as Query Block, WooCommerce Product Collection, or used as a stand-alone block.

Vous pouvez afficher n’importe quel champ dont la valeur peut être récupérée par l’API du cœur (get_post_meta, get_term_meta, get_user_meta) et qui est une chaine de caractères ou peut être converti en chaine de caractères. Pour afficher la valeur du champ dans l’éditeur de blocs, il doit être accessible via l’API REST ou avoir le type de champ défini sur dynamic.

You can also display custom fields created by the Advanced Custom Fields or Meta Box plugin explicitly. It supports all ACF field types and Meta Box field types whose values are strings or can be converted to strings. Some other ACF complex fields such as Image, Link, Page Link, True False, Checkbox, Select, Radio, Button Group, Taxonomy, User, Post Object and Relationship field types as well as Meta Box fields such as Select, Checkbox, Radio, Image, Video, Taxonomy, User, Post field types are also supported in basic formats.

Cette extension fournit également des API de crochet conviviales pour les développeurs/développeuses qui vous permettent de personnaliser facilement la sortie du bloc, d’afficher des champs de type données complexes ou d’utiliser le bloc comme un texte indicatif pour afficher n’importe quel type de contenu avec object_id et object_type en tant que paramètres de contexte.

Un cas particulier où ce bloc est vraiment utile est lorsque vous avez besoin d’obtenir le post_id correct dans votre code court lorsque vous l’utilisez dans une boucle de requête. Dans ce cas, vous pouvez définir le type de champ comme dynamic et entrer votre code court dans le nom du champ. Le bloc l’affichera correctement à la fois sur l’interface publique et dans l’éditeur. Alternativement, si vous voulez uniquement voir l’aperçu de votre code court dans l’éditeur, vous pouvez également utiliser ce bloc comme une meilleure version du core/shortcode.

Liens

Quel est le résultat HTML d’un champ personnalisé ?

La sortie HTML d’un champ personnalisé sur l’interface publique dépend du contexte du champ. Il utilise l’une de ces fonctions de l’API du cœur pour obtenir la valeur du champ : get_post_meta, get_term_meta, get_user_meta.

Quel code HTML est généré pour les champs ACF ?

  1. Tous les types de champs basiques qui renvoient des chaînes ou qui peuvent être convertis en chaînes sont pris en charge – La fonction get_field est utilisée pour générer le code HTML.

  2. Type Lien – Le code HTML généré est :

    <a href={url} target={target} rel="noreferrer noopener">{title}</a>
    

    Aucun attribut rel n’est ajouté si l’attribut target n’est pas égal à _blank

  3. Type Image – Le code HTML généré provient de la fonction wp_get_attachment_image. La taille de l’image est définie par le réglage « Taille de l’aperçu ».

  4. True / False type – The HTML output is Yes if the value is true, and No if the value is false. Below is the code snippet to change these text values:

    add_filter( 'meta_field_block_true_false_on_text', function ( $on_text, $field_name, $field, $post_id, $value ) {
      return 'Yep';
    }, 10, 5 );
    
    add_filter( 'meta_field_block_true_false_off_text', function ( $off_text, $field_name, $field, $post_id, $value ) {
      return 'Noop';
    }, 10, 5 );
    
  5. Type Case à cocher/Liste déroulante – Le code HTML généré est :

    <span class="value-item">{item_value}</span>, <span class="value-item">{item_value}</span>
    

    item_value peut être égal à value ou label en fonction du format de présentation du champ. Plusieurs valeurs sélectionnées sont séparées par le caractère , (virgule) et l’extrait de code ci-dessous permet de modifier ce séparateur :

    add_filter( 'meta_field_block_acf_field_choice_item_separator', function ( $separator, $field_name, $field, $post_id, $value ) {
      return ' | ';
    }, 10, 5 );
    
  6. Type bouton radio / Groupe de boutons – Le code HTML généré est value ou label en fonction du format de présentation du champ.

  7. Type Lien vers la page, type Objet de la publication – Le code HTML généré pour un champ à valeur unique est :

    <a class="post-link" href={url} rel="bookmark">{title}</a>
    

    Pour un champ à valeur multiple :

    <ul>
      <li><a class="post-link" href={url} rel="bookmark">{title}</a></li>
      <li><a class="post-link" href={url} rel="bookmark">{title}</a></li>
    </ul>
    
  8. Type Relation – Le code HTML généré est :

    <ul>
      <li><a class="post-link" href={url} rel="bookmark">{title}</a></li>
      <li><a class="post-link" href={url} rel="bookmark">{title}</a></li>
    </ul>
    
  9. Type Taxonomie – Le code HTML généré est :

    <ul>
      <li><a class="term-link" href={term_url}>{term_name}</a></li>
      <li><a class="term-link" href={term_url}>{term_name}</a></li>
    </ul>
    
  10. Type Compte – Le code HTML généré pour un champ à valeur unique est :

    <a class="user-link" href={author_url}>{display_name}</a>
    

    Pour un champ à valeur multiple :

    <ul>
      <li><a class="user-link" href={author_url}>{display_name}</a></li>
      <li><a class="user-link" href={author_url}>{display_name}</a></li>
    </ul>
    
  11. Pour d’autres types de champ plus complexes, vous pouvez générer un code HTML personnalisé en utilisant le crochet :

    apply_filters( 'meta_field_block_get_acf_field', $field_value, $post_id, $field, $raw_value, $object_type )
    

    Ou en utilisant le crochet général :

    apply_filters( 'meta_field_block_get_block_content', $content, $attributes, $block, $object_id, $object_type )
    

What is the HTML output of Meta Box fields?

  1. Similar to ACF fields, all basic fields that return strings or can cast to strings using the function rwmb_get_value are supported.

    The HTML output of cloneable basic fields is:

    <span class="value-repeater-item">{item_1_value}</span>, <span class="value-repeater-item">{item_2_value}</span>
    

    Use the following hooks to change the tag and the separator:

    apply_filters( 'meta_field_block_mb_clone_field_item_separator', ', ', $field, $post_id, $field_value )
    apply_filters( 'meta_field_block_mb_clone_field_item_tag', 'span', $field, $post_id, $field_value )
    
  2. Single image types – The HTML output is from the wp_get_attachment_image function. The image size is from the image_size setting.

  3. Image list types (Image, Image advanced, Image upload) – The HTML output is:

    <figure class="image-list">
      <figure class="image-item"><img /></figure>
      <figure class="image-item"><img /></figure>
    </figure>
    
  4. Checkbox / Switch type – Similar to ACF True / False type.

  5. Multi-choice types (Select, Select advanced, Button group, Autocomplete, Image select, Checkbox list) – The HTML output is:

    <span class="value-item">{item_value}</span>, <span class="value-item">{item_value}</span>
    

    To display the label instead of the value, use this hook:

    apply_filters( 'meta_field_block_mb_field_choice_item_display_label', false, $field_name, $field, $post_id, $value )
    

    To change the separator, use this hook:

    apply_filters( 'meta_field_block_mb_field_choice_item_separator', ', ', $file_name, $field, $post_id, $value )
    
  6. Radio type – The output is the field value by default. To display label or change the separator, use the same hooks as the multi-choice types.

  7. Post type – The HTML output for a single-value field is:

    <a class="post-link" href={url} rel="bookmark">{title}</a>
    

    Pour un champ à valeur multiple :

    <ul>
      <li><a class="post-link" href={url} rel="bookmark">{title}</a></li>
      <li><a class="post-link" href={url} rel="bookmark">{title}</a></li>
    </ul>
    
  8. Taxonomy, Taxonomy advanced type – The HTML output for a single-value field is:

    <a class="term-link" href={term_url}>{term_name}</a>
    

    Pour un champ à valeur multiple :

    <ul>
      <li><a class="term-link" href={term_url}>{term_name}</a></li>
      <li><a class="term-link" href={term_url}>{term_name}</a></li>
    </ul>
    
  9. User type – Similar to ACF User type

  10. Video type – The HTML output for a single-value field is:

    <video controls preload="metadata" src={video_src} width={video_width} poster={poster} />
    

    Pour un champ à valeur multiple :

    <figure class="video-list">
      <figure class="video-item"><video /></figure>
      <figure class="video-item"><video /></figure>
    </figure>
    
  11. To display complex field types or change the output of a field, use the hook meta_field_block_get_mb_field or the general hook meta_field_block_get_block_content.

Extraits à copier & coller

When using the meta_field_block_get_block_content hook to customize block content, we recommend selecting dynamic as the field type. This way, both the front end and the editor will show the changes. If you are working with ACF Fields, we suggest using the meta_field_block_get_acf_field hook to modify the field content. Similarly, Meta Box users should use the meta_field_block_get_mb_field hook to modify the content. ACF snippets can also be used with Meta Box fields, but you must use the correct hook name and replace the get_field function with the rwmb_get_value function.

  1. Comment modifier la sortie HTML du bloc ?
    En utilisant le crochet meta_field_block_get_block_content :

    add_filter( 'meta_field_block_get_block_content', function ( $block_content, $attributes, $block, $post_id, $object_type ) {
      $field_name = $attributes['fieldName'] ?? '';
    
      if ( 'your_unique_field_name' === $field_name ) {
        $block_content = 'new content';
      }
    
      return $block_content;
    }, 10, 5);
    

    Utilisation du crochet meta_field_block_get_acf_field pour les champs ACF uniquement :

    add_filter( 'meta_field_block_get_acf_field', function ( $block_content, $post_id, $field, $raw_value, $object_type ) {
      $field_name = $field['name'] ?? '';
    
      if ( 'your_unique_field_name' === $field_name ) {
        $block_content = 'new content';
      }
    
      return $block_content;
    }, 10, 5);
    

    Cet extrait basique est très puissant. Vous pouvez l’utiliser pour afficher n’importe quel champ provenant de publications, de termes, de comptes ou de réglages. Voir en détail les cas particuliers ci-dessous.

  2. Comment envelopper le bloc avec un lien vers la publication dans la boucle de requête ?
    En utilisant le crochet meta_field_block_get_block_content :

    add_filter( 'meta_field_block_get_block_content', function ( $block_content, $attributes, $block, $post_id ) {
      $field_name = $attributes['fieldName'] ?? '';
    
      if ( 'your_unique_field_name' === $field_name && $block_content !== '' ) {
        $block_content = sprintf('<a href="%1$s">%2$s</a>', get_permalink($post_id), $block_content);
      }
    
      return $block_content;
    }, 10, 4);
    

    Utilisation du crochet meta_field_block_get_acf_field pour les champs ACF uniquement :

    add_filter( 'meta_field_block_get_acf_field', function ( $block_content, $post_id, $field, $raw_value ) {
      $field_name = $field['name'] ?? '';
    
      if ( 'your_unique_field_name' === $field_name && $block_content !== '' ) {
        $block_content = sprintf('<a href="%1$s">%2$s</a>', get_permalink($post_id), $block_content);
      }
    
      return $block_content;
    }, 10, 4);
    

    Cet extrait fonctionne uniquement avec un bloc ayant des balises HTML « inline » ou une image.

  3. Comment afficher un champ d’URL d’image comme une balise d’image ?
    En utilisant le crochet meta_field_block_get_block_content :

    add_filter( 'meta_field_block_get_block_content', function ( $block_content, $attributes, $block, $post_id ) {
      $field_name = $attributes['fieldName'] ?? '';
    
      if ( 'your_image_url_field_name' === $field_name && wp_http_validate_url($block_content) ) {
        $block_content = sprintf('<img src="%1$s" alt="your_image_url_field_name" />', esc_attr($block_content));
      }
    
      return $block_content;
    }, 10, 4);
    

    Utilisation du crochet meta_field_block_get_acf_field pour les champs ACF uniquement :

    add_filter( 'meta_field_block_get_acf_field', function ( $block_content, $post_id, $field, $raw_value ) {
      $field_name = $field['name'] ?? '';
    
      if ( 'your_image_url_field_name' === $field_name && wp_http_validate_url($block_content) ) {
        $block_content = sprintf('<img src="%1$s" alt="your_image_url_field_name" />', esc_attr($block_content));
      }
    
      return $block_content;
    }, 10, 4);
    
  4. Comment afficher plusieurs champs méta dans un même bloc ?
    Par exemple, si nous avons besoin d’afficher le nom d’un utilisateur ou d’une utilisatrice à partir de deux champs méta prénom et nom.

    add_filter( 'meta_field_block_get_block_content', function ( $block_content, $attributes, $block, $post_id ) {
      $field_name = $attributes['fieldName'] ?? '';
    
      if ( 'full_name' === $field_name ) {
        $first_name = get_post_meta( $post_id, 'first_name', true );
        $last_name  = get_post_meta( $post_id, 'last_name', true );
    
        // If the meta fields are ACF Fields. The code will be:
        // $first_name = get_field( 'first_name', $post_id );
        // $last_name  = get_field( 'last_name', $post_id );
    
        $block_content = trim("$first_name $last_name");
      }
    
      return $block_content;
    }, 10, 4);
    

    Choisissez le type de champ dynamique et saisissez le nom du champ full_name.

  5. Comment afficher un champ de réglage ?
    Par exemple, nous devons afficher un champ de réglage nommé footer_credit dans l’élément de modèle de pied de page du site.

    add_filter( 'meta_field_block_get_block_content', function ( $block_content, $attributes, $block, $post_id ) {
      $field_name = $attributes['fieldName'] ?? '';
    
      // Replace `footer_credit` with your unique name.
      if ( 'footer_credit' === $field_name ) {
        $block_content = get_option( 'footer_credit', '' );
    
        // If the field is an ACF Field. The code will be:
        // $block_content = get_field( 'footer_credit', 'option' );
      }
    
      return $block_content;
    }, 10, 4);
    
  6. Comment utiliser MFB comme texte indicatif pour afficher n’importe quel type de contenu ?

SAVE YOUR TIME WITH MFB PRO

To display simple data type fields for posts, terms, and users, you only need the free version of MFB. MFB Pro can save you 90% of development time when working with ACF, or Meta Box complex fields. It achieves this by transforming your ACF complex field types into container blocks, which work similarly to core container blocks. This eliminates the need for creating custom blocks or writing custom code for displaying complex fields.

Below are some video tutorials that demonstrate how MFB Pro can help you display complex fields:

How to build a post template without coding

How to display ACF Repeater fields as a list, grid, or carousel

How to display ACF Gallery fields as a grid, masonry, or carousel

The main features of MFB PRO are:

Si cette extension vous est utile, veuillez s’il vous plait laisser une évaluation rapide et une note sur WordPress.org pour la faire connaître au plus grand nombre. Ce serait très apprécié.

Vous pouvez consulter mes autres extensions si cela vous intéresse :

  • Content Blocks Builder – This plugin turns the Block Editor into a powerful page builder by allowing you to create blocks, variations, and patterns directly in the Block Editor without needing a code editor.
  • SVG Block – A block to display SVG images as blocks. Useful for images, icons, dividers, and buttons. It allows you to upload SVG images and load them into the icon library.
  • Icon separator – A tiny block just like the core/separator block but with the ability to add an icon.
  • Breadcrumb Block – A simple breadcrumb trail block that supports JSON-LD structured data and is compatible with WooCommerce.
  • Block Enhancements – Adds practical features to blocks like icons, box shadows, transforms, etc.
  • Counting Number Block – A block to display numbers with a counting effect
  • Better YouTube Embed Block – A block to solve the performance issue with embedded YouTube videos. It can also embed multiple videos and playlists.

The plugin is built using @wordpress/create-block.
MFB is developed using only native Gutenberg features to keep it fast and lightweight.
MFB Pro uses SwiperJS for the carousel layout. However, if you don’t use the carousel layout, the script and styles won’t be loaded on your page.

Captures d’écrans

  • Meta field settings

  • Réglages de préfixe et de suffixe

  • Style de préfixe et de suffixe

  • Enable Show in REST API ACF setting

Blocs

Cette extension fournit 1 bloc.

  • Meta Field Block Display a custom field as a block on the frontend. Supports custom fields for posts, terms, and users. Officially supports ACF, Meta Box, and all text-based meta fields.

Installation

  1. Téléverser les fichiers de l’extension dans le répertoire /wp-content/plugins/meta-field-block ou installez directement l’extension via l’écran des extensions WordPress.
  2. Activez l’extension depuis la page « Extensions » de WordPress

FAQ

Qui a besoin de cette extension ?

Cette extension a été conçue pour les développeurs et développeuses, mais tout le monde peut l’utiliser.

Prend-il en charge la saisie et l’enregistrement de la valeur méta ?

Non. Il affiche uniquement les champs méta sous forme de blocs.

Prend-il en charge tous les types de champs méta ?

Seuls les types simples tels que chaîne, entier ou nombre peuvent être utilisés directement. Les autres types complexes tels qu’objet ou tableau doivent être convertis en chaînes de balisage HTML.

Prend-il en charge tous les types de champs ACF ?

It supports all basic field types that return strings or cast to strings. Some complex field types like image, link, page_link, post_object, relationship, taxonomy, and user are also supported in a basic format. To display complex ACF field types such as Group, Repeater, Flexible Content, Gallery, File, etc., you will need to either purchase MFB PRO or write your own custom code using the hook API.

Does it support all types of Meta Box fields?

It supports all basic field types and some complex field types such as Image, Video, Choice fields, Taxonomy, User, Post, in basic format. For other complex field types, you can use the built-in hook to display your fields with custom markup. MFB PRO allows you displaying the Group field as a container block, Cloneable Group field as a repeater block with group, row, stack, grid, or carousel layout, Post field as a Query Loop, Image list fields as a gallery with grid or masonry layouts, or as a carousel of images.

À quoi servent le préfixe et le suffixe ?

La valeur de ces réglages doit être du texte brut ou certaines balises HTML autorisées. Leurs valeurs seront formatées avec wp_kses( $prefix, wp_kses_allowed_html( "post" ) ). Ils sont utiles dans certains cas comme pour l’affichage du nom du champ méta ou l’affichage d’une valeur avec un préfixe ou un suffixe, par exemple 100 $, 100 px, etc.

Inclut-il un style pour le champ méta ?

Le bloc ne fournit aucun style CSS pour la valeur du champ méta. Mais il fournit dans les réglages un style basique pour le positionnement du champ.

Prend-il en charge d’autres frameworks de champs méta ?

Oui, tant que ces champs méta sont accessibles via la fonction get_post_meta, ou get_term_meta, ou get_user_meta et que la valeur de retour est une chaine de caractères ou peut être convertie en chaine de caractères. Pour afficher la valeur dans l’éditeur de blocs, il faut accéder au champ méta via l’API REST.

Que se passe-t-il si le balisage affiché est vide ou différent de la valeur méta ?

Il est possible que la valeur de votre méta contienne des balises ou des attributs HTML qui ne sont pas autorisés à s’afficher. Pour corriger ce problème, vous devez utiliser le crochet apply_filters( 'meta_field_block_kses_allowed_html', $allowed_html_tags ) pour ajouter vos balises et attributs au tableau des balises autorisées. Par défaut, le bloc autorise toutes les balises de la valeur $allowedposttags et les attributs de base pour les éléments iframe et SVG.

If you don’t want to sanitize the content at all, use this hook apply_filters( 'meta_field_block_kses_content', false, $attributes, $block, $post_id, $object_type, $content ). However, we don’t recommend doing it unless you have a good reason.

Avis

26 juin 2025 1 réponse
Really useful and well working plugin for displaying ACF fields in templates including repeater fields. Awesone friendly and quick support!
18 mai 2025 1 réponse
Wow – been a couple of years since I logged into wp.org This plugin is just the thing needed to display custom fields on the front end without messing with php templates or dealing with the bloat of a page builder. I’m looking forward to getting the Pro version.
22 avril 2025 1 réponse
I was struggling with showing some dynamic content in query loop, with help of this plugin I easily resolved it. This block even support shorcode, so you create your dynamic field structure your way by using any shortcode creation plugin and just put that shortcode in this field option and wow its clearly understand the loop context and show it correctly.
3 mars 2025 1 réponse
Very handy when using Gutenberg, and cherry on the cake, the hooks for devs. Thanks!
Lire les 51 avis

Contributeurs/contributrices & développeurs/développeuses

« Meta Field Block » est un logiciel libre. Les personnes suivantes ont contribué à cette extension.

Contributeurs

“Meta Field Block” a été traduit dans 6 locales. Remerciez l’équipe de traduction pour ses contributions.

Traduisez « Meta Field Block » dans votre langue.

Le développement vous intéresse ?

Parcourir le code, consulter le SVN dépôt, ou s’inscrire au journal de développement par RSS.

Journal des modifications

1.4.3

Release Date – 17 June 2025

  • Improved – Added error handling for get_term_link to prevent string casting errors.
  • Added – (MFB Pro) Allowed binding a text field as the label for a button created from a URL field.
  • Added – (MFB Pro) Displaying a group field as a details block, and displaying a repeater or cloned group as an accordion.
  • Improved – (MFB Pro) Allowed selecting a field path for sub-field blocks instead of entering it manually.

1.4.2

Release Date – 12 May 2025

  • Improved – Ignored the cloneable setting for Meta Box image-related and choice-related field types
  • Added – (MFB Pro) Set a video sub-field as the background video of a parent group field.
  • Added – (MFB Pro) Bind a sub color field to the overlay color feature.
  • Improved – (MFB Pro) Handle missing media uploads for button and image block bindings.
  • Improved – (MFB Pro) Render only one item as the fallback value for a single ACF Post Object field.
  • Improved – (MFB Pro) Allow displaying the sample ID input setting when choosing the meta type as ‘post’ and the current post type is not post or page

1.4.1

Release Date – 28 April 2025

  • Fixed – (MFB Pro) The target attribute of the ACF link was not binding correctly.
  • Fixed – (MFB Pro) Removed the duplicate store registration warning.
  • Fixed – (MFB Pro) Error when the hosting environment does not support mb_encode_numericentity.
  • Improved – (MFB Pro) Preload layout for carousels is now calculated correctly before the script executes.
  • Improved – (MFB Pro) Don’t show carousel preview in the Block Editor on Mobile and Tablet modes
  • Improved – (MFB Pro) Some small adjustments on the carousel layout

1.4

Release Date – 14 April 2025

  • Added – Supported most of field types for the Meta Box framework.
  • Added – (MFB Pro) Display the ACF repeater field in a carousel layout besides group, row, stack and grid layout.
  • Added – (MFB Pro) Display the ACF gallery field as a carousel of images.
  • Added – (MFB Pro) Set an image sub-field as the background image of a parent group field.
  • Added – (MFB Pro) Most Meta Box complex fields have PRO features similar to ACF fields.
  • Added – [MFB Pro] Background overlay and doutone to background images.
  • Improved – [MFB Pro] Add block bindings to image and button blocks.
  • Added – Supported displaying post title with MFB.
  • Added – Shadow, heading color support features.
  • Improved – Add new hook meta_field_block_ignore_wrapper_block to allow omitting the block wrapper, prefix, suffix in the output.
  • Improved – Add new hook meta_field_block_ignore_prefix_suffix to allow omitting the prefix, suffix in the output.
  • Improved – Add new hook meta_field_block_get_block_wrapper_extra_attributes to allow adding custom attributes to the block wrapper.
  • Changed – Replace the hook meta_field_block_acf_field_true_false_on_text by the hook meta_field_block_true_false_on_text. The new hook can be applied to both ACF and Meta Box fields.
  • Changed – Replace the hook meta_field_block_acf_field_true_false_off_text by the hook meta_field_block_true_false_off_text. The new hook can be applied to both ACF and Meta Box fields.
  • Fixed – Non UTF-8 characters in button’s text are rendered incorrect

1.3.5

Release Date – 13 February 2025

  • Fixed – (MFB Pro) Load alt text for gallery images

1.3.4

Release Date – 27 January 2025

  • Improved – (MFB Pro) Allow custom sorting with the nested Query Loop for the relationship field
  • Fixed – (MFB Pro) Load all posts stored in the relationship field for the Query Loop
  • Updated – Freemius SDK 2.11.0

1.3.3

Release Date – 06 January 2025

  • Fixed – (MFB Pro) ACF Relationship field and custom post types
  • Improved – (MFB Pro) Add the plugin version to the premium style file
  • Updated – Update Freemius SDK 2.10.1

1.3.2

Release Date – 17 November 2024

  • Improved – Updated translation text for compatibility with WordPress 6.7

1.3.1

Release Date – 28 October 2024

  • Improved – Prevent inner links from being clickable in the editor
  • Improved – Add code to check if the post and term exist before displaying them
  • Updated – Upgrade to Freemius SDK 2.9.0

1.3.0

Release Date – 05 August 2024

  • Added – (MFB Pro) Register custom bindings for heading and paragraph when displaying a text field as a heading or a paragraph block
  • Added – (MFB Pro) Allow linking an image field to a custom URL from another field
  • Improved – (MFB Pro) Display dynamic value in the editor when displaying a field as a heading, paragraph, button, image, or video block
  • Improved – (MFB Pro) Allow displaying the value of URL, and email as button text when displaying them as a button
  • Fixed – (MFB Pro) Expanding image is not getting dynamic value
  • Refactor – Replaced classnames with clsx
  • Refactor – Replace useSetting by useEttings
  • Updated – Tested up to 6.5 for block bindings

1.2.14

Release Date – 31 July 2024

  • Improved – Escape the style attribute for prefix and suffix

1.2.13

Release Date – 17 July 2024

  • Improved – Ignore array and object fields from the list of suggested names in the meta field type
  • Improved – MFB Pro: Change the label with mailto prefix to the mail value
  • Updated – Update Freemius SDK to 2.7.3

1.2.11

Release Date – 06 June 2024

  • Added – Support clientNavigation interactivity
  • Added – Allow changing the object type via the new filter meta_field_block_get_object_type
  • Improved – MFB Pro: Use useEntityRecord to display suggested names for setting fields

1.2.10

Release Date – 07 May 2024

  • Added – Add correct format for ACF textarea and editor field in the editor
  • Updated – Use useSettings instead of useSetting since WP 6.5
  • Improved – Flush server cache for object type and ACF fields when necessary
  • Improved – Add field label to the layout variations of SFB: Group, Flexible content, Repeater
  • Improved – MFB Pro: Don’t allow editing field path for repeater items SFB
  • Improved – MFB Pro: Flexible content field type

1.2.9

Release Date – 01 May 2024

  • Improved – Invalidate the MFB cache when updating a post, a term, a user, or settings
  • Updated – Help text in the settings page

1.2.8

Release Date – 22 April 2024

  • Updated – Since WP 6.5 we could not get the post ID and post type from the current context when accessing the template editor from a post/page.
  • Added – Add the emptyMessage feature to static blocks

1.2.7

Release Date – 16 April 2024

  • Added – Support displaying custom fields inside the Woo Product Collection block

1.2.6

Release Date – 22 March 2024

  • Added – Add query, and queryId of Query Loop as context parameters
  • Updated – PRO: Render nested ACF oEmbed fields

1.2.5

Release Date – 11 March 2024

  • Updated – Update inline documentation
  • Fixed – When front-end forms are submitted to admin-post.php, nopriv users are redirected to the login page.
  • Added – PRO: Display ACF gallery field
  • Added – PRO: Display ACF File as a video

1.2.4

Release Date – 22 February 2024

  • Added – Add typography and gap settings to prefix and suffix
  • Removed – Remove the redundant blockGap support feature
  • Improved – Remove _acf_changed from the list of suggested names
  • Fixed – Remove the block margin on value, prefix and suffix when the block is used inside a flow-layout block
  • Fixed – PRO: Correct the name for some field types for ACF
  • Added – PRO: Enable the hideEmpty setting for static blocks
  • Improved – PRO: Change the default perPage value for ACF query fields from 100 to 12
  • Added – PRO: Add the linkToPost setting to the ACF image field and ACF URL-as-image field

1.2.3

Release Date – 24 January 2024

  • Added – New dynamic field type to display private fields, support running shortcodes, and see the changes made by the hook meta_field_block_get_block_content both on the front end and the editor.
  • Updated – Change the name of a private hook from ‘_meta_field_block_get_field_value’ to ‘_meta_field_block_get_field_value_other_type’
  • Updated – Change the permission for getting custom endpoints from publish_posts to edit_posts

1.2.2

Release Date – 08 January 2024

  • Updated – Adjust the configuration for freemius

1.2.1

Release Date – 03 January 2024

  • Updated – Support full attributes for SVG and all basic shapes in the allowed HTML tags
  • Added – Add the settings page with guides
  • Added – Integrate with freemius 2.6.2
  • Updated – Add the section tag to the list of HTML tag
  • Updated – Ignore footnotes from the suggested values for the meta field name
  • Updated – Update Requires at least to 6.3

1.2

Release Date – 11 December 2023

  • Added – Allow getting meta fields from terms and users
  • Updated – Add new $object_type parameter to two main hooks meta_field_block_get_acf_field and meta_field_block_get_block_content
  • Added – Add variations for some common ACF field types
  • Updated – Increase the required version of PHP to 7.4
  • Updated – Refactor code for upcoming releases
  • Updated – Move the prefix and suffix to a separate panel

1.1.7

Release Date – 09 September 2023

  • FIX – The block does not show the number 0 if using it as the empty message

1.1.6

Release Date – 13 August 2023

  • DEV – Refactor block.json, update to block API version 3 for better WP 6.3 compatibility
  • FIX – Rename allowed HTML attributes for SVG

1.1.5

Release Date – 15 July 2023

  • DEV – Add a custom hook apply_filters( 'meta_field_block_kses_allowed_html', $allowed_html_tags ) for filtering allowed HTML tags in the value.
  • DEV – Allow displaying iframe, and SVG tag by default.
  • DEV – Force displaying color (text, background, link) attributes for unsupported themes.
  • DEV – Refactor code for React best practice.
  • DOC – Update readme for the hook meta_field_block_get_acf_field

1.1.4

Release Date – 20 May 2023

  • DEV – Change the placeholder text for the block in the site editor.
  • DEV – Add a setting to use the ACF field label as the prefix

1.1.3

Release Date – 31 Mar 2023

  • DEV – Support choice fields: true/false, select, checkbox, radio, button group
  • DEV – Add raw value to the meta_field_block_get_acf_field hook

1.1.2

Release Date – 28 Mar 2023

  • DEV – Refactor both JS and PHP code
  • DEV – Load ACF field value even if we could not load the field object
  • DEV – Separate settings group for WP 6.2

1.1.1

Release Date – 14 Mar 2023

  • DEV – Add a hideEmpty setting to hide the whole block if the value is empty
  • DEV – Add an emptyMessage setting to show a custom text in case the value is empty
  • FIX – The meta field did not show on the archive template

1.1.0

Release Date – 06 Mar 2023

  • DEV – Refactor all the source code for more upcoming features
  • DEV – Make sure the block works with all return formats for the image field, link field
  • DEV – Get all custom rest fields to show on the suggested help
  • DEV – Allow changing the tagName from the block toolbar
  • DEV – Improve performance
  • DEV – Add more core support features
  • DEV – Add more meaningful messages for some use cases
  • FIX – Allow displaying links without text

1.0.10

Release Date – 02 Feb 2023

  • DEV – Support multiple values for ACF User type

1.0.9

Release Date – 15 Sep 2022

  • FIX – Change the textdomain to the plugin slug

1.0.8

Release Date – 10 Sep 2022

  • FIX – Wrong handle for wp_set_script_translations. Thanks to Loïc Antignac (@webaxones)

1.0.7

Release Date – 07 Sep 2022

  • FIX – Add a null check for meta fields value before accessing it’s property

1.0.6

Release Date – 25 Jun 2022

  • DEV – Add an option to show the block’s outline on the Editor

1.0.5

Release Date – 21 Jun 2022

  • DEV – Display the placeholder text on the template context

1.0.4

Release Date – 02 May 2022

  • DEV – Support displaying some field types for ACF such as image, link, page_link, post_object, relationship, taxonomy

1.0.3

Release Date – 30 April 2022

  • DEV – Add supports for borders, and full typography options

1.0.2

Release Date – 28 April 2022

  • DEV – Add the title to block registration in JS
  • REFACTOR source code

1.0.1

Date de sortie – 23 mars 2022

  • Correctif – Le bloc ne fonctionne pas dans l’éditeur de site.

1.0.0

Release Date – 22 February 2022