ACF - Set fields as translatable #113
Conversation
| private function define_integrations() : void { | ||
| $this->define_integration_migrators(); | ||
| $immediate_integrations = [ |
There was a problem hiding this comment.
Don't know if it's an overkill for now, but it seems that we might need other situations for this and we could structure things a bit better in an array that indicates when to run each integration.
|
@xipasduarte We're forcing all the fields that have translatable post/term ids to be translatable. This is used when a post's language is changed and the IDs are automatically corrected, and also when copying to another language via the duplicate-post plugin, which still needs us to fix and translate the IDs. If we don't force all these ACF fields with translatable post/term IDs to be translatable by default, then the user can very easily run into issues where meta values contain IDs for a language that is not the post/term's language, which we obviously want to avoid. |
closes #38