AdvancedCustomFields / AdvancedCustomFields/acf
acf-json + fields' translation
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
I would like to use fields (defined, versioned and deployed using ACF-JSON) for various sites having different languages.
Is there a plan to handle ACF JSON when it comes to i18n fields?
A couple of hooks (are available at load-time/save-time to load/write translations (acf/prepare_field_group_for_export, NB: acf_import_field_group is missing a similar hook, only acf/update_field_group is provided) but formalize it (and why not, implement it), would be appreciated for forward-compatibility.
w3c issued a couple of guideline and draft on this topic some months ago:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the ACF-JSON export and import flow, especially the mentioned acf/prepare_field_group_for_export, acf_import_field_group, and acf/update_field_group hooks. Compare the current behavior with the linked W3C internationalization guidance and determine the scope for formalizing or implementing translated fields. Done should include an agreed, forward-compatible approach for loading and writing translations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- internationalization, localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100