Fatal error upon updating
-
Not working
This is what is displayed:Statut : Résolution de l’adresse de http://ftp.qualitiges.org
Statut : Connexion à 213.186.33.204:21…
Statut : Connexion établie, attente du message d’accueil…
Réponse : 220-Bienvenue,
Réponse : 220-
Réponse : 220- On Vous Héberge ?
Réponse : 220-
Réponse : 220-Vous êtes connecté sur webm295.
Réponse : 220 This is a private system – No anonymous login
Commande : USER Qualitiges
Réponse : 331 User Qualitiges OK. Password required
Commande : PASS ********
Réponse : 530 Login authentication failed
Erreur : Erreur critique : Impossible d’établir une connexion au serveurI tried as well with USER Adminlike ion WordPress
Statut : Résolution de l’adresse de http://ftp.qualitiges.org
Statut : Connexion à 213.186.33.204:21…
Statut : Connexion établie, attente du message d’accueil…
Statut : Serveur non sécurisé, celui-ci ne supporte pas FTP sur TLS.
Commande : USER Admin
Réponse : 331 User Admin OK. Password required
Commande : PASS ********
Réponse : 530 Login authentication failed
Erreur : Erreur critique : Impossible d’établir une connexion au serveurI think the password is correct : it is the one I used to log in in WordPress before the update of the plugin
I tried as well the one that is used to log in on this forum. It is not working.The message of “fatal error” is still appearing in my control panel…
Hello @melissa,
Can you confirm that you have a PHP version >= 5.3 and that in your .htaccess file there is not another version call ?
We had a long conversation about it
https://wordpress.org/support/topic/fatal-error-upon-updating?replies=35
Further to my previous posts the issue is fixed. What I actually dit is based on what @thomasnguyencom and Reedyseth said.
To log with FTP my miskake was to try with User name and password I use for wordpress.
What is to be done is to use OVH parameters that were sent by OVH when the wordpress blog was created to upload the website online :
– http://ftp.cluster
– login
– passwordI was able to find the folder for “Subscribe To Comments Reloaded”
Then I deleted the folder (mouse right click / delete)
My website is back and so is the admin page to login.
Hi @reedyseth! It´s working now. I updated PHP to version 5.3. Thank you very much!
I updated PHP to version 5.3. Thank you very much!
Glad to hear that.
Regards.!!
I just had this problem. My site didn’t work with a 500 internal server error. However I noticed images loaded ok, and my Gallery3 worked. So the problem had to be WordPress.
I edited wp-config.php to enable debug output.
define('WP_DEBUG', true); @ini_set('display_errors', 1);
Then when I loaded my site I saw –
Parse error: syntax error, unexpected T_STRING in /home1/xxxxxxx/public_html/yyyyyy/wp-content/plugins/subscribe-to-comments-reloaded/subscribe-to-comments-reloaded.php on line 19Then I found this thread, and I downloaded the zip of the older version of the Subscribe To Comments Reloaded plugin, and uploaded that. My site worked!
I use Bluehost as well. I checked the Php version and Bluehost says: “Bluehost currently offers PHP 5.4 and 5.6.” However, in cPanel, it says I am using PHP version 5.2.17. I also made a phpinfo file and it says 5.2.17 as well. That is the issue. I guess I’ll see about updating that.
Your WordPress version is not catching up the latest one, there is a explicit way to say that, see this two threads.
https://wordpress.org/support/topic/fatal-error-upon-updating?replies=23
https://github.com/stcr/subscribe-to-comments-reloaded/issues/170
One of your links is this thread 🙂 I solved it and I know the problem. I posted to provide more info for people. It’s really great to see you helping people here though. I have deactivated the plugin so it doesn’t auto-update and I’ll set my Bluehost to a newer version of PHP so it will work.
One of your links is this thread 🙂
Haha, yes I noticed that later 🙂
Glad to hear that now is working !
- The topic ‘Fatal error upon updating’ is closed to new replies.
(@mandy-roberson)
8 years, 3 months ago
Receiving the following message when updating the plugin –
Plugin could not be activated because it triggered a fatal error.
Also triggering a syntax error –
/plugins/subscribe-to-comments-reloaded/subscribe-to-comments-reloaded.php on line 19
These errors actually took a client’s site offline, and I had to delete the plugin to get the site back up. Tried reinstalling with the latest version and received the errors again.
https://wordpress.org/plugins/subscribe-to-comments-reloaded/