Background of the issue:
We're struggling to migrate our Bedrock/Composer based website which uses WPML to standard WordPress. While we have all the plugins and files running now, when we try to migrate the database we are receiving the following error: Fatal error: Uncaught InvalidArgumentException: item should be a Collection or an array or an object in C:MAMPhtdocsvanillavpwp-contentpluginssitepress-multilingual-cmsvendorwpmlfpcoreObj.php:112 Stack trace: #0 [internal function]: WPMLFPObj::WPMLFP{closure}(NULL, 'setup_complete', false) #1 C:MAMPhtdocsvanillavpwp-contentpluginssitepress-multilingual-cmsvendorwpmlfpcorefunctions.php(152): call_user_func_array(Object(Closure), Array) #2 [internal function]: WPMLFPObj::WPMLFP{closure}(NULL, 'setup_complete', false) #3 C:MAMPhtdocsvanillavpwp-contentpluginssitepress-multilingual-cmsvendorwpmlcollectsrcIlluminateSupportTraitsMacroable.php(56): call_user_func_array(Object(Closure), Array) #4 C:MAMPhtdocsvanillavpwp-contentpluginssitepress-multilingual-cmsvendorwpmlfpcoreObj.php(90): WPMLFPObj::__callStatic('propOr', Array) #5 [internal function]: WPMLFPObj::WPMLFP{closure}('setup_complete', false) #6 C:MAMPhtdocsvanillavpwp-contentpluginssitepress-multilingual-cmsvendorwpmlfpcoreObj.php on line 112. As this is a WPML error I'm hoping you can give us some insight into how to fix this so we can move our website off Bedrock.
Symptoms:
Fatal error: Uncaught InvalidArgumentException: item should be a Collection or an array or an object in C:MAMPhtdocsvanillavpwp-contentpluginssitepress-multilingual-cmsvendorwpmlfpcoreObj.php:112
Questions:
How can we fix the InvalidArgumentException error during the database migration?
Are there specific steps to migrate a Bedrock/Composer based website using WPML to standard WordPress?
The topic ‘[關閉] Migration from bedrock/composer’ is closed to new replies.
管理 Cookie 同意
我们使用 cookies 来优化我们的网站和服务。 您的同意允许我们处理浏览行为等数据。 不同意可能会影响某些功能。
功能性
始终启用
为了我们的网站正常运行和通信所需的信息。
首选项
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.