Email about fatal error

  • jonesy1981

    (@jonesy1981)


    3 years, 10 months ago

    No update helps with this so here is the email i get,

    Howdy!

    Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

    In this case, WordPress caught an error with one of your plugins, Search Everything.

    First, visit your website (http://atlas.globusfamily.com/) and check for any visible issues. Next, visit the page where the error was caught (http://atlas.globusfamily.com/wp-admin/post.php) and check for any visible issues.

    Please contact your host for assistance with investigating this issue further.

    If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.

    http://atlas.globusfamily.com/wp-login.php?action=enter_recovery_mode&rm_token=m5aIXCbSMycyuVJ0WhjbSE&rm_key=GAExOLEnjQG02kKWI5mmNR

    To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 5.4.1
    Current theme: Woffice (version 1.8.3)
    Current plugin: Search Everything (version 8.1.9) PHP version 7.3.18-1+ubuntu18.04.1+deb.sury.org+1

    Error Details
    =============
    An error of type E_ERROR was caused in line 927 of the file /nas/content/live/globusfamily/wp-content/plugins/search-everything/search-everything.php. Error message: Uncaught Error: Cannot use object of type WP_Error as array in /nas/content/live/globusfamily/wp-content/plugins/search-everything/search-everything.php:927
    Stack trace:
    #0 /nas/content/live/globusfamily/wp-includes/class-wp-hook.php(289): se_post_publish_ping(11119)
    #1 /nas/content/live/globusfamily/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(true, Array)
    #2 /nas/content/live/globusfamily/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #3 /nas/content/live/globusfamily/wp-includes/post.php(4700): do_action(‘publish_post’, 11119, Object(WP_Post))
    #4 /nas/content/live/globusfamily/wp-includes/post.php(4054): wp_transition_post_status(‘publish’, ‘draft’, Object(WP_Post))
    #5 /nas/content/live/globusfamily/wp-includes/post.php(4244): wp_insert_post(Array, false)
    #6 /nas/content/live/globusfamily/wp-admin/includes/post.php(409): wp_update_post(Array)
    #7 /nas/content/live/globusfamily/wp-admin/post.php(227): edit_post()
    #8 {main}
    thrown

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter jonesy1981

    (@jonesy1981)

    3 years, 10 months ago

    Is anyone out there that has gotten this email error??

    Jeroen van der Rhee

    (@jeroenvdrhee)

    3 years, 10 months ago

    I am also facing the same issue.

    I have replaced the function se_post_publish_ping in /search-everything/search-everything.php for the function below. This worked for me:

    
function se_post_publish_ping($post_id) {
	//should happen only on first publish
	$status = false;
	if( !empty( $_POST['post_status'] ) && ( $_POST['post_status'] == 'publish' ) && ( $_POST['original_post_status'] != 'publish' ) ) {
		$permalink = get_permalink($post_id);
		$zemanta_response = se_api(array(
			'method' => 'zemanta.post_published_ping',
			'current_url' => $permalink,
			'post_url' => $permalink,
			'post_rid' => '',
			'interface' => 'wordpress-se',
			'deployment' => 'search-everything',
			'format' => 'json'
		));
               if (!is_wp_error($zemanta_response)) {
	         $response = json_decode($zemanta_response['body']);
		 if (isset($response->status)) {
			$status = $response->status;
		 }
             }
	}
	return $status;
}
    Tin Cabin Studio

    (@tincabin)

    3 years, 9 months ago

    We are getting the same error for the same line number. Hopefully someone is on this.

    Thread Starter jonesy1981

    (@jonesy1981)

    3 years, 8 months ago

    I was giving this a little time but ever since I did this fix we havent received the email so I highly recommend this fix. Thanks jeroenvdrhee for the solution!!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Email about fatal error’ is closed to new replies.