Background of the issue:
I am trying to get WPML to catch all of the ACF fields on our blocks in the translation editor on our production environment. On my local instance, the fields come through, but not on production. I thought committing and pushing up the .mo and .php files generated by running translation locally to production would overwrite the translation on production, but it seems to have no effect. The only condition I can find that may be different between my local and production is the ability to write to the languages folder; this error appears on production: hidden link
Symptoms:
WPML is not catching all ACF fields in the translation editor on the production environment. Some content remains in English in the German translation, indicating fields not picked up by WPML. These fields do not show up in the advanced translation editor.
Questions:
Do you have any ideas as to why WPML would not pick up all of our ACF fields on the production version of our site?
Is there some way to make the translation files generated on local read on production?
My apologies for the delay, I'm trying to set up the staging site to migrate to on our Cloudways servers but I"m having some trouble. Do you have the option from your hosting provider to create a staging site? or using something like WP Staging? I'm still trying, just wanted to ask in case it would help speed up the troubleshooting.
Also, the replies from here will automatically go to the email address you have on your WPML account. If you would like to update that email, you can do so from wpml.org/account.
We don't have the permissions legally to transfer any of the content over to a separate platform, and we have a workaround for now on this problem, so I will end our thread here. Thank you for your help in the meantime.
Okay thanks for letting me know. If you would like to share your workaround in the next reply, please feel free. Otherwise, you can mark this ticket as resolved. Thanks!
