This thread is resolved. Here is a description of the problem and solution.
Problem:
The client encountered a fatal error when using WPML with ACF and ACF Multilingual, specifically a TypeError related to an illegal offset type.
Solution:
We are aware of this issue and are currently working on a permanent fix for a future release of ACF Multilingual. In the meantime, we recommend following the workaround provided on our errata page: Advanced Custom Fields Fatal Error.
Please note that the solution provided might be outdated or not applicable to your case. If the workaround does not resolve your issue, we highly recommend checking our known issues page, verifying the version of the permanent fix, and ensuring that you have the latest versions of themes and plugins installed. If you still need assistance, please do not hesitate to open a new support ticket with us: WPML support forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
This topic contains 1 reply, has 2 voices.
Last updated by 1 year, 3 months ago.
Assisted by: Osama Mersal.
 |
|
 WPML Supporter since 02/2020 Languages: English (English ) Arabic (العربية ) Timezone: Africa/Cairo (GMT+03:00) |
Hi, Thanks for contacting WPML forums support. I'll be glad to help you today. Our dev team is aware of the issue and is working on a permanent fix in a future ACF Multilingual release. You can check the errata page to know the status of this issue on our development queue. (https://wpml.org/errata/advanced-custom-fields-fatal-error-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in/) Best regards,  |
