WordPress.org

Support

Support » How-To and Troubleshooting » An Unexpected HTTP Error – to be fixed

An Unexpected HTTP Error – to be fixed

  • My wordpress dashboard is not working properly.

    When I try to search for plugins (under “Install plugin”), it says “An Unexpected HTTP Error occurred during the API request.”
    I also suspect that this problem causes some plugins to fail (some plugins that I install behaved weirdly, like showing blank).

    I’ve tried the common troubleshooting, like deactivating all the plugins and use the default theme, and installing wordpress again, but the problem persists.

    Here is some information:
    Server info: Apache/2.23 CentOS
    Php version: 5.33

    And when I turn on “Debug mode”, this is what is said on the top of every page:
    “Notice: get_settings is deprecated since version 2.1! Use get_option() instead. in /home/comman/www/new/wp-includes/functions.php on line 3467

    Notice: get_settings is deprecated since version 2.1! Use get_option() instead. in /home/comman/www/new/wp-includes/functions.php on line 3467

    Notice: get_settings is deprecated since version 2.1! Use get_option() instead. in /home/comman/www/new/wp-includes/functions.php on line 3467

    Notice: get_settings is deprecated since version 2.1! Use get_option() instead. in /home/comman/www/new/wp-includes/functions.php on line 3467

    Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/comman/www/new/wp-includes/functions.php on line 3587

    Notice: load_plugin_textdomain was called with an argument that is deprecated since version 2.7 with no alternative available. in /home/comman/www/new/wp-includes/functions.php on line 3553″

    What can I do to fix this issue? I would deeply appreciate your help, thanks in advance!

Viewing 3 replies - 1 through 3 (of 3 total)
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘An Unexpected HTTP Error – to be fixed’ is closed to new replies.