I am trying to test version 5.0.8 on our staging server. I see the message about the license not being for multiple domains preventing me from updating. I downloaded the latest version from the EE site and successfully updated it manually, but the site gives a critical error when activated…
[15-Aug-2023 16:29:18 UTC] PHP Fatal error: Uncaught TypeError: ftp_nlist(): Argument #1 ($ftp) must be of type FTP\Connection, null given in /www/source/wp-admin/includes/class-wp-filesystem-ftpext.php:438
Yes, direct is the setting for that constant. This staging server is on an AWS Lightsail WordPress instance. WP_CONTENT_DIR is not present in wp-config.php
As far as I can tell, this is an issue with how the site is set up rather than Event Espresso itself.
EE uses the WordPress filesystem to access files based on how your install is configured, in this case it looks like it’s trying to use FTP to connect but that isn’t set up? I’m guessing it’s something within AWS but I don’t use it so can’t say for sure.
When you install/update plugins, does usually ask for FTP credentials?
Thanks. It does ask for FTP credentials unless I have the FS_METHOD constant defined as ‘direct’. With that constant defined, all other plugins install and update without issue. Only EE would crash the site when activated.
RESOLVED: I did some reading on the FS_METHOD constant and found that it needs to be near the top of the wp-config.php file just below db information. That seems to have worked.
Thanks. It does ask for FTP credentials unless I have the FS_METHOD constant defined as ‘direct’. With that constant defined, all other plugins install and update without issue. Only EE would crash the site when activated.
The issue isn’t the update itself.
Event Espresso downloads the translation files on the fly, why? Because we have a lot of translations so including them all bumps up the size of the plugin a lot.
So on activation of each version of the plugin EE will download the translation file and to do so it uses the WP_Filesystem. Most plugins don’t do that on the fly so you won’t see the same issue with them as the update itself is handled through WP core, the error above isn’t from the update process itself.
RESOLVED: I did some reading on the FS_METHOD constant and found that it needs to be near the top of the wp-config.php file just below db information. That seems to have worked.
That’s odd, it should work as long as it’s above this line:
/** Sets up WordPress vars and included files. */
require_once ABSPATH . 'wp-settings.php';
Which is usually at the very bottom of wp-config.php and what calls all of the WP settings, you can’t set those same settings after that.
The support post ‘Activating on staging server’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
Support forum for Event Espresso 3 and Event Espresso 4.