i have problem

This thread is resolved. Here is a description of the problem and solution.

Problem:
You are working on a site under development and encountered a problem with duplicate ACF fields from different language fields. After setting all field groups to 'Same fields across languages' and removing duplicates, the data in the fields was saved for all languages in the admin. However, on the site, two out of three languages display correctly, but the third shows an error: 'Uncaught Error: Illegal offset type in isset or empty'.
Solution:
We recommend checking a similar support ticket that might help resolve the issue you are facing: https://wpml.org/forums/topic/fatal-error-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in-var-w/
Before making any changes, please back up your database first.
Additionally, verify if the ACF options were translated in other languages using the format "%options_(language_code)_resources%", where (language_code) is replaced with the actual language code.

Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket at 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.

Tagged: Compatibility, Exception

This topic contains 3 replies, has 0 voices.

Last updated by Andrey 6 days, 21 hours ago.

Assisted by: Andrey.

Author	Posts
March 17, 2025 at 4:57 pm #16826595
mykolaA-2	Background of the issue: I am working on a site under development and encountered a problem with duplicate ACF fields from different language fields. Your employee advised me to remove the duplicates for other languages and set all field groups to 'Same fields across languages' because we have the same fields for all languages, only the texts are different. I did this, and the data in the fields was saved for all languages in the admin. Symptoms: On the site, 2 out of 3 languages show correctly, but on the third, I get an error: Uncaught Error: Illegal offset type in isset or empty in /var/www/html/dev.lanet.click/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-flexible-content.php on line 727. Questions: How can I resolve the error related to illegal offset type in ACF fields? Why does the error occur only in one language and not the others?
March 19, 2025 at 11:29 am #16834737
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+02:00)	Thank you for contacting WPML support. I would suggest checking the following support ticket as it may help to resolve the issue you are facing: https://wpml.org/forums/topic/fatal-error-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in-var-w/ Before making any changes, please back up your database first.
March 19, 2025 at 1:50 pm #16835603
mykolaA-2	I try delete all options_ru_ MariaDB [base name]> select * from wp_options where option_name like 'options_ru_%'; Empty set (0,003 sec) but when I go to my settings (ACF options page), the data in ru is still present in the admin and the error has not disappeared
March 19, 2025 at 4:02 pm #16836366
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+02:00)	Have you checked other possible languages in which the ACF options were translated? For example, "%options_(language_code)_resources%", where (language_code) is replaced with the other possible language.