Plugin Fatal Error | Site Inaccessible

@wabrbhome I have the same issue.

Done a little more digging and it seems that https://www.facebook.net/ domain is currently with an error “ERR_NAME_NOT_RESOLVED”.

nslookup

returns:

** server can't find www.facebook.net: NXDOMAIN

Digging the code further it seems that this function in /facebook-for-woocommerce/includes/Events/AAMSettings.php:69 does not take into account that $response might not be a is_wp_error() but can be still empty. So “array_key_exists()” check fails cause there is no array there in the first place.

public static function build_from_pixel_id( $pixel_id ) {
		$url      = self::get_url( $pixel_id );
		$response = wp_remote_get( $url );
		if ( is_wp_error( $response ) ) {
			return null;
		} else {
			$response_body = json_decode( wp_remote_retrieve_body( $response ), true );
			if ( ! array_key_exists( 'errorMessage', $response_body ) ) {
				$response_body['matchingConfig']['pixelId'] = $pixel_id;
				return new AAMSettings( $response_body['matchingConfig'] );
			}
		}
		return null;
}

Here is the “quick fix” for this function (which will still through GET “API” response as its 500):

public static function build_from_pixel_id( $pixel_id ) {
        $url      = self::get_url( $pixel_id );
        $response = wp_remote_get( $url );

        if ( is_wp_error( $response ) ) {
            return null;
        }

        $response_body = json_decode( wp_remote_retrieve_body( $response ), true );

        if ( ! $response_body || array_key_exists( 'errorMessage', $response_body ) ) {
            return null;
        }

        $response_body['matchingConfig']['pixelId'] = $pixel_id;
        return new AAMSettings( $response_body['matchingConfig'] );
}

Hopefully we will get a fix in next release.

• This reply was modified 1 year, 1 month ago by evscoding.