You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// See if a filter has disabled the content API, this may be done to override a specific use case.
if ( false === apply_filters( 'sailthru_content_api_enable', true ) ) {
return;
}
However, in the user login flow, the API credentials are not checked, and thus, the requests fail, and the error objects are logged to the error logs.
In non-production and local environments where these API credentials are not set, this keeps adding logs and making it difficult to debug actual errors.
In most of the places, the plugin checks if the API credentials are set or not and then makes requests to sailthru, for example -
sailthru-wordpress-plugin/classes/class-sailthru-content.php
Lines 595 to 606 in eb21493
However, in the user login flow, the API credentials are not checked, and thus, the requests fail, and the error objects are logged to the error logs.
In non-production and local environments where these API credentials are not set, this keeps adding logs and making it difficult to debug actual errors.
sailthru-wordpress-plugin/plugin.php
Lines 281 to 286 in eb21493
The text was updated successfully, but these errors were encountered: