Fix appearance and logic of some key validation messages [MAILPOET-743]

This commit is contained in:
Alexey Stoletniy
2017-01-26 22:15:52 +03:00
parent 157725c300
commit 37017ef69d
2 changed files with 15 additions and 9 deletions

View File

@ -34,21 +34,25 @@ class Services extends APIEndpoint {
$state = !empty($result['state']) ? $result['state'] : null;
$success_message = null;
if($state == Bridge::MAILPOET_KEY_VALID) {
return $this->successResponse(null);
$success_message = __('Your MailPoet API key is valid!', 'mailpoet');
} elseif ($state == Bridge::MAILPOET_KEY_EXPIRING) {
$success_message = sprintf(
__('Your MailPoet key expires on %s!', 'mailpoet'),
Carbon::createFromTimestamp(strtotime($result['data']['expire_at']))
->format('Y-m-d')
);
}
if ($success_message) {
return $this->successResponse(array('message' => $success_message));
}
switch($state) {
case Bridge::MAILPOET_KEY_INVALID:
$error = __('Your MailPoet key is invalid!', 'mailpoet');
break;
case Bridge::MAILPOET_KEY_EXPIRING:
$error = sprintf(
__('Your MailPoet key expires on %s!', 'mailpoet'),
Carbon::createFromTimestamp(strtotime($result['data']['expire_at']))
->format('Y-m-d')
);
break;
default:
$code = !empty($result['code']) ? $result['code'] : Bridge::CHECK_ERROR_UNKNOWN;
$error = sprintf(