Home›Support›English Support›[Resolved] FATAL ERROR in Advanced Custom Fields Multilingual version 2.1.4.1
[Resolved] FATAL ERROR in Advanced Custom Fields Multilingual version 2.1.4.1
This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing a Fatal Error with the Advanced Custom Fields Multilingual (ACFML) plugin version 2.1.4.1, it might be due to a compatibility issue with the plugin's latest update. Solution: We recommend updating the ACFML plugin to version 2.1.4.2. This update addresses the Fatal Error issue and should restore functionality to your site. To update, simply go to your WordPress dashboard, navigate to the 'Plugins' section, and select the update option for ACFML.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please open a new support ticket with us.
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.
Background of the issue:
Hi, with the upgrade of the Advanced Custom Fields Multilingual plugin to version 2.1.4.1 I encountered a Fatal Error for which I report the error log below. By deactivating the plugin, the site works correctly. To remedy the problem and keep the plugin active, I had to temporarily restore version 2.1.3. Looking forward to hearing from you how to patch the issue.
Symptoms:
Fatal error: Uncaught InvalidArgumentException: item should be a Collection or an array or an object in /home/***/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/Obj.php:112
Questions:
How can I resolve the Fatal Error encountered with Advanced Custom Fields Multilingual version 2.1.4.1?
Is there a patch or update available to fix this issue?
I checked for a possible theme/plugin conflict on the staging/test site, and the issue disappeared when I deactivated the “Advanced Custom Fields: Extended” plugin.
It looks like there’s a conflict between Advanced Custom Fields: Extended and the latest version of ACFML.
To fix this, we need to recreate the issue on a new WordPress site so we can report it to our compatibility team.
I’ll work on replicating it on a new site and escalate it to the team and get back to you.
Thank you for reporting the issue. I’m able to replicate this issue at a fresh WP site and now I’m going to escalate it to our compatibility team and will get back to you with an update soon.
Hi Noman, the workaround works, but this is not a stable solution. You know, when the plugin will be updated, my change will be replaced. Could you provide a stable release of the plugin, please?
