[Resolved] Fatal error: Uncaught TypeError: Illegal offset type
This thread is resolved. Here is a description of the problem and solution.
Problem: The client was experiencing a fatal error on all products with a gallery after using the WPML plugin to translate from Polish to Czech and enabling media translation settings.
Solution: 1. We asked the client if the issue disappeared when filling all the custom fields (ACF) with test information. 2. We inquired whether these fields were set to be translatable, copied, or copied once. 3. We guided the client to check the configuration by going to Custom Fields -> Edit the Field group that contains these fields -> Edit the fields. 4. We provided a link to a guide for setting the correct configuration: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/ 5. After consulting with colleagues, we concluded that WPML does not generate errors if ACFs are left empty in the original content, suggesting that the issue might be due to custom code or third-party plugin/theme functionality.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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 further assistance is needed, please contact us in the 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.
2.- Please increase the WP memory Limit. Minimum requirements are 128Mb: https://wpml.org/home/minimum-requirements/
You can add this to wp-config.php to increase WP memory:`
1.- Please share a URL where the issue can be seen.
2.- I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to back up the site before providing us access. If we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.
To see the configuration you can go to Custom Fields -> Edit the Field group that contains these fields -> Edit the fields and you will find the configuration.
I consulted my colleagues about this issue and WPML won't generate any error if the ACFs are left empty in the original content regardless of the configuration. So everything points to a custom code or a functionality from a third-party plugin/theme that is causing this problem because is trying to display the content from ACF that doesn't exists.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
