Ver. 2.5 500 internal server error on front end
I upgraded jetpack from 2.4.2 to 2.5. Immediately would get 500 internal server error on the front end if i was logged in – back end was still accessible. If i deleted the cookies for the site (not sure which one it was), front end was restored, but as soon as i logged back in, error occurred on front end. Restored jetpack 2.42 and error no longer occurs.
Upgrade has hosed wordpress.
Renaming the plugin folder has restored the front end – though it may be just the caching plugin serving the static html as not all pages are appearing.
Rolling back to 2.4.2 hasn’t helped though and I still cannot log into the back end. wp-admin is unresponsive.
Turned on WP debug, but nothing in there to indicate what the issue is.
I can now get into my backend and pages have returned, by removing jetpack from the plugins folder.
I tried installing the 2.5 plugin via the zip file to see if that would work, but no, that hosed WP again.
Hi to the both of you:
Could you post your site URLs here, so I can have a look?
If you want it to remain private, you can also contact us via this contact form:
Make sure to include a link to this thread in your message.
I have a similiar problem. MU-sites with jetpack activated went offline, after renaming the plugindir and thereby deactivating it, i get this when I want to reactivate:
Notice: wpdb::escape is deprecated since version 3.6! Use wpdb::prepare() or esc_sql() instead. in /wp-includes/functions.php on line 2905 Warning: require_once(wp-content/plugins/jetpack/modules/publicize/publicize.php): failed to open stream: No such file or directory in wp-content/plugins/jetpack/modules/publicize.php on line 26 Fatal error: require_once(): Failed opening required 'wp-content/plugins/jetpack/modules/publicize/publicize.php' (include_path='.:/usr/share/pear:/usr/share/php') in /wp-content/plugins/jetpack/modules/publicize.php on line 26
Note: I remove the first part of the absolute path.
Hm, the dir was empty, but it shouldn’t. seems like the autoupdater didn’t work the way it should.
After manually reuploading it via ftp it works as it should.
Maybe there should be a file-exist check before it fails silently?
Majoga — can you check your server’s error log?
I will be happy to do so when i have some time to investigate the issue again. I have currently reverted to 2.4.2 per my first post. I haven’t updated it on any other sites as of yet. When i can get freed of client issues i will revisit. Unfortunately, i can’t give an eta. If i had to guess, i’d say it would probably be a couple of weeks before i can get to it.
- The topic ‘Ver. 2.5 500 internal server error on front end’ is closed to new replies.