1 May 24

ACF PRO 6.3 Beta 1

By Liam Gladdy

Today, we’re excited to release the first beta of ACF PRO 6.3.

We’ve packed this release full of some of the most common feature requests from our ACF Blocks users, the biggest of these are field validation support and the ability to store field data of a block in the postmeta table, which are the focus of our beta 🎉

For full information on ACF 6.3, please read the final release blog post.

Beta 1 Changelog

  • New – ACF now requires WordPress version 6.0 or newer, and PHP 7.4 or newer.
  • New – ACF Blocks now support validation rules for fields
  • New – ACF Blocks now supports storing field data in the postmeta table rather than in the post content
  • New – Conditional logic rules for fields now support selecting specific values for post objects, page links, relationships and users rather than having to enter the ID
  • New – Icon selection for a custom post type menu icon
  • New – Icon selection for an options page menu icon
  • New – ACF now surfaces debug and status information in the WordPress Site Health area
  • New – The escaped html notice can now be permanently dismissed
  • Enhancement – Tab field now supports a selected attribute to specify which should be selected by default, and support class attributes
  • Fix – Block Preloading now works reliably in WordPress 6.5 or newer
  • Fix – Custom post types registered with ACF will now have custom field support enabled by default to better support revisions
  • Fix – The first preview after publishing a post in the classic editor now displays ACF fields correctly
  • Fix – ACF fields and Flexible Content layouts are now correctly positioned while dragging
  • Fix – Copying the title of a field inside a Flexible Content layout no longer adds whitespace to the copied value
  • Fix – Flexible Content layout names are no longer converted to lowercase when edited
  • Fix – ACF Blocks with attributes without a default now correctly register
  • Fix – User fields no longer trigger a 404 when loading results if the nonce generated only contains numbers
  • Fix – Description fields for ACF items now support being solely numeric characters
  • Fix – The field group header no longer appears above the WordPress admin menu on small screens
  • i18n – All errors raised during ACF PRO license or update checks are now translatable
  • Other – The ACF Shortcode is now disabled by default for new installations of ACF as discussed in the ACF 6.2.7 release notes

About the Author

For plugin support, please contact our support team directly, as comments aren't actively monitored.

  • Dominique Pijnenburg says:

    An icon picker? Wow, that’s something I wanted for a long time, but not specifically for the current implementation but as a field type. Will it also become available in that way?

  • Josh B says:

    This version busts one of my custom ajax post forms and returns a 400 error when trying to post to the CPT from the form, maybe a compatibility issue with Elementor. Reverting to 6.2.10 pro fixes the issue.

    [23-May-2024 08:15:49 UTC] PHP Warning: Trying to access array offset on value of type bool in wp-content/plugins/elementor-pro/modules/dynamic-tags/acf/tags/acf-image.php on line 59

    r.send(i.hasContent && i.data || null)

    in jquery.min.js?ver=3.7.1:2

    Full error:

    
    send    @   jquery.min.js?ver=3.7.1:2
    ajax    @   jquery.min.js?ver=3.7.1:2
    (anonymous) @   jquery-migrate.min.js?ver=3.4.1:2
    e.<computed>    @   jquery-migrate.min.js?ver=3.4.1:2
    (anonymous) @   ugc-submission.js:7
    dispatch    @   jquery.min.js?ver=3.7.1:2
    v.handle    @   jquery.min.js?ver=3.7.1:2```
    
    It's 100% possible it's an issue on my end, but the fact that reverting the plugin from 6.3.0.1 to 6.2.10 and it works correctly and posts the form contents to the CPT is strange.
    • Josh B says:

      [23-May-2024 08:15:49 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/elementor-pro/modules/dynamic-tags/acf/tags/acf-image.php on line 59

      Was the full php warning, not sure how that got cutoff.

      • Liam says:

        Hey Josh, Please contact our support team for more help here – although looking at the error, it actually looks like this is a bug in Elementor – depending on what your previous version was etc, they might need to update their code for a previous change in ACF.

        Either way, drop support@advancedcustomfields.com a ping and they’ll look into it further.