Plugin
PluginActualizado
WPML Advanced Custom Fields Multilingual
Datos del producto
- Versión
- 5.2.0
- Publicado
- 21 octubre 2026
- Tipo
- Plugin
- Licencia
- GPL
- Incluido en
- Todos los planes, o $4.19 / year por separado
- Desarrollador
- OnTheGoSystems
Resumen
WPML Advanced Custom Fields Multilingual de OnTheGoSystems.
Versión 5.2.0, actualizada el 21 octubre 2026.
Registro de cambios
Versión 5.2.0 — 20 octubre 2026
- Nuevo Translated pages carry the inLanguage property in the JSON-LD structured data that ACF outputs.
- Nuevo When an AI agent creates an ACF field group through ACF's abilities, it can now choose the group's translation mode.
- Mejorado With ACF Extended, bidirectional relationship fields now stay paired on translations after WPML copies, duplicates or translates them.
- Mejorado Taxonomy custom fields set to Copy are locked on term translations.
- Mejorado On the Custom Fields Translation settings, the underscore system field of a locked ACF field is now locked too.
- Mejorado When ACF Multilingual is active without Advanced Custom Fields, a notice now says so and offers to activate or install it.
- Mejorado The String Translation packages for field group labels are named after their field group, so it is clear what each one holds.
- Mejorado ACF Link and URL fields that point to your own pages now keep their #anchor, query string and sub-path instead of being cut to the bare page address.
- Mejorado "Overwrite with duplicate" on a field group refreshes ACF's field cache, so it no longer causes PHP warnings.
- Corregido A row inserted into a Copy-mode flexible content field reaches translations that were edited in the WordPress editor.
- Corregido With one field group per language, a translation's admin editor shows its saved values, and saving there keeps them.
- Corregido Saving a translation of a post with repeater fields no longer causes a fatal error when its previous translation job cannot be read.
- Corregido ACF options values translated in String Translation appear on the site, and completed translation jobs no longer overwrite manual String Translation translations.
- Corregido ACF Select fields are copied correctly to translations of existing pages.
- Corregido Field groups loaded from acf-json send their translation preferences to WPML.
- Corregido Options-page values read after switching language return the switched language, not the language the request started in.
- Corregido Flexible content layouts keep their disabled state and custom name in translations.
- Corregido ACF bidirectional relationships are kept per language.
- Corregido Duplicating ACF Extended bidirectional posts no longer adds the translations to the original post's relationship.
- Corregido Row sync, Copy once and field-group setup also run on saves through REST, the front end, WP-CLI and ACF's own data store.
- Corregido Clone field subfields get the right translation preferences, and a Link field's target is no longer sent for translation.
- Corregido ACF blocks are supported with post-meta storage, inline block fields and field groups assigned to blocks.
- Corregido Changing an ACF field's translation preference also updates existing term translations, not only posts.
- Corregido On sites set up with WPML 5.0, ACF field groups open in the WordPress editor again instead of WPML's translation editor.
- Corregido Post types created in ACF while ACF Multilingual was deactivated get their labels registered for translation.
- Corregido The post editor no longer asks to translate a post manually when its field groups mix "Same content" and Expert modes.
- Corregido Upgrading from an ACF Multilingual version older than 2.2.0 no longer leaves an untranslated duplicate "Field Group Labels" package per field group.
- Corregido The field-group modes notice reads correctly in Spanish, Hebrew and other languages, without wrong plural wording around the field count.
- Corregido New layouts are copied in posts with Flexible Content fields.
- Corregido Saving a translated post in the WordPress editor no longer removes its system fields.
- Corregido A Taxonomy field connects the translated terms instead of creating new terms when you save in the WordPress editor.
- Corregido Pagination in repeater fields works on translations.
- Corregido The ACF Multilingual and WPML SEO descriptions translate on the Plugins screen.
- Corregido Built and released together with WPML 5.2.0, with the same shared library version.
- Corregido Read the release announcement for WPML 5.2 for the full story behind this version.
Versiones anteriores
- 5.1.0 (28 septiembre 2026): 1 nuevo, 21 mejorado, 12 corregido, 1 seguridad
- 5.0.0 (12 septiembre 2026): 2 nuevo, 20 mejorado, 1 corregido, 1 seguridad
- 2.2.4 (20 abril 2026): 2 corregido
Preguntas frecuentes
¿WPML Advanced Custom Fields Multilingual es gratis?
El código de WPML Advanced Custom Fields Multilingual tiene licencia GPL, así que cualquiera puede usarlo, modificarlo y compartirlo. Mercado GPL es un servicio de pago: un plan o la compra de WPML Advanced Custom Fields Multilingual te da la descarga y sus actualizaciones. El soporte del propio desarrollador, su clave de licencia y sus servicios en línea no están incluidos.
¿Qué versión de WPML Advanced Custom Fields Multilingual es esta?
Versión 5.2.0, publicada el 21 octubre 2026. Las versiones nuevas aparecen aquí cuando el desarrollador las publica.
¿Cómo actualizo WPML Advanced Custom Fields Multilingual?
Instala MercadoGPL Updater en tu sitio y pega tu clave de Mi cuenta. Instalará por ti las versiones nuevas de WPML Advanced Custom Fields Multilingual.






