fatal error upgrading to 4.2.1

  • Resolved solarheatengines

    (@solarheatengines)


    9 years, 10 months ago

    Here’s the error message I got back:
    Fatal error: Call to undefined function wp_json_encode() in /homepages/22/d233747096/htdocs/dougsdiy.com/wp-admin/includes/misc.php on line 668

    This message would raise my blood pressure on some of my sites, but this isn’t one of them. I would, however, like to get this fixed eventually. Any guidance on how to start would be appreciated.

    Doug

Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator James Huff

    (@macmanx)

    Try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, access your server via FTP or SFTP, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue (theme functions can interfere like plugins).

    Thread Starter solarheatengines

    (@solarheatengines)

    I”m not quite sure how I would reset my plugins without a dashboard. I did try renaming the plugin directory and renaming the theme. Neither of them had any effect.

    Moderator James Huff

    (@macmanx)

    I”m not quite sure how I would reset my plugins without a dashboard. I did try renaming the plugin directory and renaming the theme.

    If you renamed your plugin directory, as directed in the linked guide, then you did reset your plugins without a Dashboard. ??

    Since neither of those worked, try downloading WordPress again and delete then replace your copies of everything except the wp-config.php file and the /wp-content/ directory with fresh copies from the download. This will effectively replace all of your core files without damaging your content and settings. Some uploaders tend to be unreliable when overwriting files, so don’t forget to delete the original files before replacing them.

    Thread Starter solarheatengines

    (@solarheatengines)

    Thank you MacManX!
    I did what you said and all is back in proper working order.

    Moderator James Huff

    (@macmanx)

    You’re welcome!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘fatal error upgrading to 4.2.1’ is closed to new replies.