We’re excited to announce the first beta release of ACF PRO 6.0. ACF PRO v6.0.0-beta1 is now available with improved performance for Repeater fields with large datasets, and a new generation of ACF Blocks. 🎉🥳
ACF 6.0 has been released! Read the release post.
We’d like to thank all of our GitHub developer preview users for their help in getting ACF 6.0’s block changes ready for release. Across the 4 developer previews (tagged as ACF 6.0.0-alpha#) we’ve fixed numerous bugs and implemented several additional new features based on your feedback, and we can’t wait to see what you develop with ACF Blocks in ACF 6.0!
ACF 6.0 introduces a new way of collecting translations from our wonderful contributors. For all the strings contained in the free version of ACF, these are now collected from translate.wordpress.org
This means ACF 6.0 introduces 10 new languages (or language variants) and updates almost all of the existing ones.
Many of you have submitted translations for numerous languages on WordPress.org since that translation functionality was introduced, but until this release they were never included or loaded into ACF. We’ve imported all the contributions we’ve received directly from our users into translate.wordpress.org for languages which weren’t already complete. These should be reviewed by the WordPress language editors over this beta cycle.
The existing languages we bundled in ACF have been trimmed where they are already complete and approved on translate.wordpress.org to only include the pro strings, but where a language is not complete, we’ve kept all the free strings included too, to avoid losing data while we wait for approval.
If you’d like to help us translate ACF to your language, or help verify translations for your language, you can do so on translate.wordpress.org. WordPress’s Translation Handbook has everything you need to get started. Once complete, you can request WordPress’s translation editors review your submissions as detailed here, or you can request to become a Project Translation Editor, where you can take control over ACF’s translations for your language.
For strings specific to the PRO version of ACF, we’ve updated our
.pot file generation to only include PRO strings, and you’ll find these files inside a new folder on our GitHub repository,
/lang/pro. Whilst today’s Beta 1 release is only for ACF PRO, we’ve manually updated the ACF Free repo with the new translations so you can start translating during this cycle.
To avoid ACF Free and ACF PRO having divergent translations, updates from translate.wordpress.org will not take effect in either version until each ACF release going forward.
Please let us know if you experience any issues with the new translations, and we can’t wait to see what languages you add support for next. English (Pirate) anyone?
To access this release, please login to your account, navigate to the “Licenses” page and select version “6.0-beta1” from the available downloads.
We’d love to hear what you think of the new features or if you have any questions or issues with the beta version then please don’t hesitate to get in touch.
We are planning another beta release this month with the first look of a plugin UI refresh, which brings an improved user experience to field groups and adding and editing fields.
The final 6.0 release will also contain a number of accessibility fixes, so look out for a release candidate coming soon.
New – Repeaters now have an optional “Pagination” setting which can be used to control the number of rows displayed at once.
New – ACF Blocks now have a versioning system allowing developers to opt in to new features.
New – ACF Blocks now support version 2, enabling
block.json support, reduced wrapper markup, and significant other new features.
New – ACF Blocks now use Block IDs saved in the block comment.
Enhancement – Bulk actions for field groups now include “Activate” and “Deactivate” options.
Fix – ACF Blocks preloading now works for blocks saved in edit mode.
Fix – ACF Blocks edit forms now behave correctly if they are not visible when loaded.
Fix – ACF Blocks now always fire
render_block_preview events when a block preview is displayed or redisplayed.
Fix – ACF Blocks with no fields now display advisory text and are selectable in the block editor. This message is filterable with the
acf/blocks/no_fields_assigned_message filter, providing both the message to be displayed and the block name it’s being displayed against.
Fix – Accordions inside ACF Blocks now match the current native block styling.
Fix – ACF Blocks which contain no fields now preload correctly.
Fix – Changes to an ACF Block’s context now trigger a re-render.
Fix – The field “move” option now no longer displays for fields when only one field group exists.
Fix – Language for field group activation state now standardized to “active” and “inactive.”
Fix – SVGs containing
foreignObject tags now correctly render in JSX rendered ACF Blocks.
i18n – ACF translations are now synced with contributions from translation.wordpress.org at each release, increasing ACF’s supported languages and updating many other translations. PRO strings should still be submitted as pull requests on GitHub (Additional thanks to maximebj, emreerkan and Timothée Moulin for their contributions which are included here).