Nextgen 2.0.14 no activation because of a fatal error
-
Tried to upgrade from 2.0.11 to 2.0.14. Done via FTP to avoid problems and slow loading, but at the end, after a quarter of an hour or more, in the backend a message warned that can’t activate the plugin because of a fatal error.
Server crashed and blank pages in front-end, slow loading in back-end.
Rolled back to 2.0.11, empty again all caches (w3tc plugin), and after another half an hour server and site are resurrected, very slowly.
Before this I had tried the upgrade on a test site and there were no problems, but on this site I haven’t W3TC.
2.0.11 works, anyway heavy like an elephant and in the editor frequently there are problems with lost connection when WP begins the autosave.
Tomorrow I’ll try again with w3tc deactivated, not now because I’m too stressed.
- The topic ‘Nextgen 2.0.14 no activation because of a fatal error’ is closed to new replies.