WPIntell

Source evidence

Critical error after activate

Newsletter SMS – SMSAPI · support · 2022-03-07T08:34:00+00:00

Newsletter SMS – SMSAPI plugin evidence original source source API
complaintsentiment
highseverity
0.97relevance
0replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 23 rows with source links

17.4% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

19 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
studioam2 unresolved
Używamy najnowszej wersji wordpressa oraz wtyczki. Po aktywacji wtyczki oraz wprowadzeniu poprawnie skonfigurowanego API KEY otrzymujemy błąd krytyczny. API KEY się nie zapisuje. Szczegóły błędu =================== Błąd typu E_ERROR został spowodowany w linii 62 pliku /wp-content/plugins/newsletter-sms-smsapi/classes/SmsapiUtils.php. Komunikat błędu: Uncaught TypeError: Return value of SmsapiUtils::ping() must be of the type bool, null returned in /wp-content/plugins/newsletter-sms-smsapi/classes/SmsapiUtils.php:62 Stack trace: #0 /wp-content/plugins/newsletter-sms-smsapi/settings.php(31): SmsapiUtils::ping(‘6v0CeS55drRVUbX…’) #1 /wp-content/plugins/newsletter-sms-smsapi/settings.php(9): action_smsapi_settings_general_login_post() #2 /wp-content/plugins/newsletter-sms-smsapi/routing.php(57): action_smsapi_settings_general() #3 /wp-includes/class-wp-hook.php(307): smsapi_settings_routing(”) #4 /wp-includes/class-wp-hook.php(331): WP_Hook->ap

Comments

0 shown

No comments were stored for this source.