Thanks for your patience. I wanted to provide an update that the report I submitted is currently in the review queue.
In the meantime, if possible, please provide a backup copy of the site or access to a staging environment, as this will likely be required by our 2nd Tier Support team for deeper investigation.
I have already included all the tests and checks I performed in the report, and I hope this information will help with troubleshooting. I will come back to you once I have feedback.
Thanks for your patience. I’ve included the file and shared the solution you provided, and the report is now in the queue for a second review. I will get back to you as soon as I receive feedback.
Thanks for your patience. As mentioned in chat, the report is still under review from our 2nd Tier Support. I will get back to you once I've feedback. My apologies for the delay and the inconvenience.
Thanks for your reply. I’m sorry, but I don’t have any updates yet from our 2nd Tier Support, as they need a bit more time to look into this. My apologies for the delay.
Thanks for your patience. I’ve received feedback from our 2nd Tier Support, and they’ve indicated that they need more time to investigate this issue. In the meantime, you can use the suggested workaround of renaming the ACF field to resolve the issue while we continue with a more in-depth investigation on our side.
Thanks for your patience. I have feedback from our 2nd Tier Support, and this is what you'll have to do on your end.
-Navigate to WP > Plugins > Add New > Commercial Tab > Update Advanced Custom Fields Multilingual to 2.1.5
-Then, navigate to WPML > Settings > Custom Fields Translation > Uncheck "Show "Multilingual Content Setup" meta box on post edit screen." as shown in the attached screenshot.
Then, please retry and let me know how it goes.
The topic ‘[Closed] This seems to be a global issue, as we cannot add next PL translation including ACF fields for these…’ is closed to new replies.
