Title: HTTP ERROR 500
Last modified: April 17, 2018

---

# HTTP ERROR 500

 *  [pivovody](https://wordpress.org/support/users/pivovody/)
 * (@pivovody)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/http-error-500-96/)
 * The plugin after the update began to give an error HTTP ERROR 500… An error appears
   after adding a post. I deactivated it ..

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [juanpasolano](https://wordpress.org/support/users/juanpasolano/)
 * (@juanpasolano)
 * [8 years ago](https://wordpress.org/support/topic/http-error-500-96/#post-10287980)
 * I’m facing the same issue…
    The error im getting is
 * `[Wed May 16 18:46:01.105312 2018] [:error] [pid 7647] [client 181.57.251.93:
   61574] PHP Fatal error: Cannot use object of type WP_Error as array in /nas/content/
   live/cozensage/wp-content/plugins/search-everything/search-everything.php on 
   line 927, referer: https://stateagelections.com/wp-admin/post-new.php?wp-post-
   new-reload=true&wp-post-new-reload=true`
 *  [mrogers5stones](https://wordpress.org/support/users/mrogers5stones/)
 * (@mrogers5stones)
 * [7 years, 12 months ago](https://wordpress.org/support/topic/http-error-500-96/#post-10366806)
 * I found this same problem. Normally I’d advise against editing a plugin, but 
   since this one hasn’t been updated for a year, it may not be a bad idea in this
   case.
 * This error is caused by an event that fires when a new post is published (The
   actual post publishes with no issue, but the event causes an error when WP redirects
   back to the post editor).
 * If you look on **Line 927** you’ll see something similar to the following:
 *     ```
           $response = json_decode($zemanta_response['body']);
           if (isset($response->status) !is_wp_error($zemanta_response)) {
               $status = $response->status;
           }
       ```
   
 * That `$zemata_response['body']`); is what’s causing the error. You’ll see on 
   the next line that the plugin developer actually excepted that variable to be
   a `WP_Error` sometimes, because they actually check to make sure that it’s **
   not**. The problem is, they are trying to access a value from an array before
   making sure that it <string>is.
 * If you change that chunk of code to the following:
 *     ```
           if (!is_wp_error($zemanta_response) && isset($response->status)) {
               $response = json_decode($zemanta_response['body']);
               $status = $response->status;
           }
       ```
   
 * The plugin will check to make sure the variable is not a `WP_Error` **first**,
   and then it will continue processing. If it is an error, the event will stop,
   and you will no longer see the error on publishing the post.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘HTTP ERROR 500’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/search-everything_242529.svg)
 * [Search Everything](https://wordpress.org/plugins/search-everything/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/search-everything/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/search-everything/)
 * [Active Topics](https://wordpress.org/support/plugin/search-everything/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/search-everything/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/search-everything/reviews/)

## Tags

 * [HTTP error 500](https://wordpress.org/support/topic-tag/http-error-500/)

 * 2 replies
 * 3 participants
 * Last reply from: [mrogers5stones](https://wordpress.org/support/users/mrogers5stones/)
 * Last activity: [7 years, 12 months ago](https://wordpress.org/support/topic/http-error-500-96/#post-10366806)
 * Status: not resolved