ACF Polylang translatable fields
Adds translatable fields to ACF for non-translated contents using Polylang
by Pierre Lebedel · github.com/pierrelebedel/acfpolylangtranslatablefields
★ 2stars
18composer installs
0forks
Install
No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:
wp plugin install https://github.com/pierrelebedel/acfpolylangtranslatablefields/archive/refs/heads/main.zipAlso on Packagist as pleb/acf-polylang-translatable-fields:
composer require pleb/acf-polylang-translatable-fieldsFrom the readme
ACF Polylang Translatable Field
This plugin adds some translatable fields to ACF for non-translated contents using Polylang
The problem
When using Polylang, each translatable post is duplicated, and that the one that matches to the users's language is displayed. The custom fields have to be filled for each post translation.
And when using qTanslate-XT, the post is not duplicate, but that's the field whitch get all translated values internally.
Sometimes, we want some duplicable post types, and some non-duplicable post types with translatable fields.
The solution
This plugin add some fields types to the ACF choices, and when the post form is submitted, that's the field himself whitch got all translated values. Internally, the values are saved with a qTranslate-like HTML comment format :
When filling in the fields, a tab will be displayed for each Polylang configured languages :
Installation
- Download and unzip the package file to your wp-content/plugins/ directory
- Or install with Composer :
composer require pleb/acf-polylang-translatable-fields
Usage
Register fields
You have to choose your field type from the Polylang translatable group inside the ACF field type s
Read the full README on GitHub →
Releases
These releases are tags only. The author does not attach a packaged zip, so there are no download counts to report.