WPIntell

Source evidence

Fatal error

Search Everything · support · 2018-11-09T17:48:00+00:00

complaintsentiment
highseverity
1.0relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

3 / 22 rows with source links

13.6% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

19 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Adam Nowak unresolved
When you try to publish a post you get a white page and this fatal error. Fatal error: Uncaught Error: Cannot use object of type WP_Error as array in /home/caseyind/public_html/wp-content/plugins/search-everything/search-everything.php:927 Stack trace: #0 /home/caseyind/public_html/wp-includes/class-wp-hook.php(288): se_post_publish_ping(4227) #1 /home/caseyind/public_html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array) #2 /home/caseyind/public_html/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #3 /home/caseyind/public_html/wp-includes/post.php(4161): do_action(‘publish_post’, 4227, Object(WP_Post)) #4 /home/caseyind/public_html/wp-includes/post.php(3588): wp_transition_post_status(‘publish’, ‘draft’, Object(WP_Post)) #5 /home/caseyind/public_html/wp-includes/post.php(3746): wp_insert_post(Array, false) #6 /home/caseyind/public_html/wp-admin/includes/post.php(377): wp_update_post(Array) #7 /home/caseyind/public_html/wp-admin/post.php(194): edit_post() #8 {main} thrown in /home/caseyind/public_html/wp-content/plugins/search-everything/search-everything.php on line 927 Have experienced this issue on an old site we are updating. To add a little more details to the issue. The post is still created in the database/admin even though the user is shown a blank page. Opening and updating the post works as expected. A little more debugging shows that there is an API call made in sa_api() to http://api.zemanta.com/services/rest/0.0/ – which is an invalid page. Resulting in the function returning a WP Error. Thus the page not being able to redirect to the edit page. I’ve had the same problem on one of my sites. line 927 in search-everything.php calls sa_api() , which returns as Michael described an WP Error object. The site is 3-4 year old one, the last update to the plugin brought the problem (on the local dev site and the live site on the server). Research Everything compose-screen widget setting are both disabled and no Zemanta API key is given. Thanks you! Another topic with a solution can be found here: https://wordpress.org/support/topic/solution-resolve-the-500-server-error-when-publishing-new-posts/

Comments

3 shown
Michael Bragg 2018-11-16T10:00:00+00:00

Have experienced this issue on an old site we are updating. To add a little more details to the issue. The post is still created in the database/admin even though the user is shown a blank page. Opening and updating the post works as expected. A little more debugging shows that there is an API call made in sa_api() to http://api.zemanta.com/services/rest/0.0/ – which is an invalid page. Resulting in the function returning a WP Error. Thus the page not being able to redirect to the edit page.

novazembla 2018-11-24T16:31:00+00:00

I’ve had the same problem on one of my sites. line 927 in search-everything.php calls sa_api() , which returns as Michael described an WP Error object. The site is 3-4 year old one, the last update to the plugin brought the problem (on the local dev site and the live site on the server). Research Everything compose-screen widget setting are both disabled and no Zemanta API key is given. Thanks you!

Surbma 2018-12-14T16:10:00+00:00

Another topic with a solution can be found here: https://wordpress.org/support/topic/solution-resolve-the-500-server-error-when-publishing-new-posts/