Background of the issue:
I am developing a site and trying to use the WPML Multilingual CMS plugin. From the moment I activate this plugin, my website under construction crashes.
Symptoms:
Error 503 Backend fetch failed. The page could not be loaded properly.
Questions:
Why does activating the WPML Multilingual CMS plugin cause my site to crash?
How can I resolve the Error 503 Backend fetch failed issue?
And below email I get from WordPress: [Bell Tours] Your Site is Experiencing a Technical Issue
Howdy!
WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
In this case, WordPress caught an error with one of your plugins, WPML Multilingual CMS.
First, visit your website (hidden link) and check for any visible issues. Next, visit the page where the error was caught (hidden link) and check for any visible issues.
Please contact your host for assistance with investigating this issue further.
If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.
hidden link
To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.
When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.6.1
Active theme: Bell Tours (version 1.0.0)
Current plugin: WPML Multilingual CMS (version 4.6.13)
PHP version 7.4.33
Error Details
=============
An error of type E_ERROR was caused in line 112 of the file /data/sites/web/belltoursbe/www/WPAG054/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/Obj.php. Error message: Uncaught InvalidArgumentException: item should be a Collection or an array or an object in /data/sites/web/belltoursbe/www/WPAG054/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/Obj.php:112
Stack trace:
#0 [internal function]: WPML\FP\Obj::WPML\FP\{closure}(NULL, 'post_id', false)
#1 /data/sites/web/belltoursbe/www/WPAG054/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/functions.php(154): call_user_func_array(Object(Closure), Array)
#2 [internal function]: WPML\FP\Obj::WPML\FP\{closure}(NULL, 'post_id', false)
#3 /data/sites/web/belltoursbe/www/WPAG054/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/collect/src/Illuminate/Support/Traits/Macroable.php(56): call_user_func_array(Object(Closure), Array)
#4 /data/sites/web/belltoursbe/www/WPAG054/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/Obj.php(90): WPML\FP\Obj::__callStatic('propOr', Array)
#5 [internal function]: WPML\FP\Obj::WPML\FP\{closure}('post_id', false)
#6 /data/sites/web/belltoursb
Thank you for contacting WPML Support, I will gladly help you.
I noticed that you have 2 sites, I would need the debug information for this website: hidden link
- Can you please tell me if you upgraded the WPML or installed it from scratch on the new site?
- I would need temporary access to your website to investigate this issue and understand it better.
Please fully back up your site (files and database) and confirm it in your next reply.
I would need to access both your site's WP-admin and FTP account, please provide both.
Your next reply is set to private so you can provide the username and password details.
Thank you for the access, I was able to check your website. The PHP & MySQL versions should be ok (they fulfill the minimum requirement for WPML).
Would it be possible to check if the issue happens in a minimal setup, meaning:
- keep the theme you have
- keep active only WPML Plugins and must-have plugins to run the theme
- disable all other plugins
After, check if the issue is still happening.
---
If the issue persists, please share with us the WordPress debug.log content (not WPML debug information) to collect more details on this issue. To enable the WordPress Debug log, open your wp-config.php file of site root and look for define('WP_DEBUG', false);. Change it to:
// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
Normally the errors will be saved to a debug.log log file inside the */wp-content/* directory. Please do the steps to reproduce the bug and check if you are getting any errors or warnings related to WPML in the log file.
If possible please paste the debug.log content to pastebin.com and provide me with that link. (This is the cleanest way because sometimes the logs are long and create a complete mess of discussion).
Thank you for the update, could you please add the code for the debug.log as instructed, and in case the issue persists, errors will show in the log file.
If that happens, please share the debug.log file content with me (you can use Pastebin.com or share a text file via Google Drive or any other file-sharing service).
Regards,
Marsel
The topic ‘[Closed] Error 503 Backend fetch failed’ is closed to new replies.
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.
