Hi indental,
Thanks for getting in touch. This is actually quite strange! By looking at our registers, I can tell that several users started using the free version during the last few days, which means that the API was accessible.
Since the request can’t access the API, I don’t have any information about the our plugin’s attempts at connecting with the API and I need your help to determine what’s amiss.
Please, edit the file includes/utils/nelio-content-api-errors.php line 83. You’ll see this:
function nc_maybe_send_error_json( $response ) {
if ( nc_is_response_valid( $response ) ) {
return;
}//end if
if ( is_wp_error( $response ) ) {
header( 'HTTP/1.1 500 Internal Server Error' );
wp_send_json( _x( 'Unable to access Nelio Content\'s API.', 'error', 'nelio-content' ) );
}//end if
// ...
As you can see, it contains the error message you see in the plugin: “Unable to access Nelio Content’s API.” So, instead of sending this message, let’s change it to something that gives us more information:
function nc_maybe_send_error_json( $response ) {
if ( nc_is_response_valid( $response ) ) {
return;
}//end if
if ( is_wp_error( $response ) ) {
header( 'HTTP/1.1 500 Internal Server Error' );
wp_send_json( print_r( $response, true ) );
}//end if
if ( is_wp_error( $response ) ) {
header( 'HTTP/1.1 500 Internal Server Error' );
wp_send_json( _x( 'Unable to access Nelio Content\'s API.', 'error', 'nelio-content' ) );
}//end if
// ...
As you can see, we’ve added a new block right after the first if (the one which checks if the response is valid) and the second if (where we checked if the response is_wp_error and sent the error message you saw).
After this tweak, just try to start the free trial again and let me know what message appears now.
Thanks for your help and let’s see if we can fix it quickly!
Regards,
David
