Skip Navigation
Home » Errata » Fatal error: Uncaught InvalidArgumentException: item should be a Collection or an array or an object when visiting WPML > Settings

Fatal error: Uncaught InvalidArgumentException: item should be a Collection or an array or an object when visiting WPML > Settings

Resolved

Reported for: Advanced Custom Fields Multilingual 2.0.5

Resolved in: Advanced Custom Fields Multilingual 2.1.0

Topic Tags: Bug

Overview of the issue

If you visit WPML > Settings > Custom fields, you may experience that certain sections go missing. The error log highlights a PHP Fatal error like the following:

PHP Fatal error: Uncaught InvalidArgumentException: item should be a Collection or an array or an object in /wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/Obj.php:112

And the issue disappears once you disable Advanced Custom Field Multilingual.

Workaround

Before taking any actions, please back up the entire site.

To resolve the issue:

  • Open your wp_options table in the database.
  • Look and delete the acfml_field_name_patterns key.

Note: Direct database manipulation is a potent action and may not be recommended as a general practice. Consult with your developer or your hosting provider for guidance.

2 Responses to “Fatal error: Uncaught InvalidArgumentException: item should be a Collection or an array or an object when visiting WPML > Settings”