Home
WebFacing™ – Email Accounts management for cPanel®
3.2
Does "WebFacing - Email Accounts in cPanel®" work with WordPress 6.0.1 and PHP 7.4.8? A smoke test was performed on 2022-07-19 08:55:22 UTC .
Summary
Errors
The plugin could not be activated
3 PHP fatal errors
No JavaScript exceptions
No resource errors
Environment
WordPress version 6.0.1 PHP version 7.4.8 MySQL version 8.0.21 PHP memory limit 256M
Pages 1 Plugins ‹ Test site — WordPress
URL
/wp-admin/plugins.php?plugin=wf-cpanel-email-accounts%2Findex.php
Requested URL
/wp-admin/plugins.php?action=activate&plugin=wf-cpanel-email-accounts%2Findex.php&plugin_status=all&paged=1&s&_wpnonce=9d6c22d901
Aspect
after-activation
HTTP status
200
Load time
0.319 s
Memory usage
3.69 MiB
JS errors
None
Resource errors
None
Benchmark No benchmark data available.
Code Statistics
Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where
possible, so the numbers you see here may be lower than those reported by other tools.
Language
%
Lines of code
Comment lines
Files
PHP 100.0% 2,691 240 12
Total
2,691
240
12
Lines of code
2,675
Total complexity
478
Median class complexity
35.0
Median method complexity
2.5
Most complex class
WebFacing\cPanel\UAPI
Most complex function
WebFacing\cPanel\Email\New_Email::admin()
Classes
9
Methods
82
Functions
16
Additions
No data available.
PHP Error Log 30 lines [19-Jul-2022 08:55:37 UTC] PHP Fatal error: Uncaught TypeError: json_decode() expects parameter 1 to be string, null given in /wp-content/plugins/wf-cpanel-email-accounts/includes/UAPI.php:39
Stack trace:
#0 /wp-content/plugins/wf-cpanel-email-accounts/includes/UAPI.php(39): json_decode()
#1 /wp-content/plugins/wf-cpanel-email-accounts/includes/UAPI.php(52): WebFacing\cPanel\UAPI::result()
#2 /wp-content/plugins/wf-cpanel-email-accounts/includes/Main.php(78): WebFacing\cPanel\UAPI::has_features()
#3 /wp-content/plugins/wf-cpanel-email-accounts/index.php(60): WebFacing\cPanel\Email\Main::admin()
#4 /wp-admin/includes/plugin.php(2313): include_once('/opt/bitnami/ap...')
#5 /wp-admin/includes/plugin.php(661): plugin_sandbox_scrape()
#6 /wp-admin/plugins.php(58): activate_plugin()
#7 {main in /wp-content/plugins/wf-cpanel-email-accounts/includes/UAPI.php on line 39
[19-Jul-2022 08:55:38 UTC] PHP Fatal error: Uncaught TypeError: json_decode() expects parameter 1 to be string, null given in /wp-content/plugins/wf-cpanel-email-accounts/includes/UAPI.php:39
Stack trace:
#0 /wp-content/plugins/wf-cpanel-email-accounts/includes/UAPI.php(39): json_decode()
#1 /wp-content/plugins/wf-cpanel-email-accounts/includes/UAPI.php(52): WebFacing\cPanel\UAPI::result()
#2 /wp-content/plugins/wf-cpanel-email-accounts/includes/Main.php(78): WebFacing\cPanel\UAPI::has_features()
#3 /wp-content/plugins/wf-cpanel-email-accounts/index.php(60): WebFacing\cPanel\Email\Main::admin()
#4 /wp-admin/includes/plugin.php(2313): include_once('/opt/bitnami/ap...')
#5 /wp-admin/plugins.php(192): plugin_sandbox_scrape()
#6 {main}
thrown in /wp-content/plugins/wf-cpanel-email-accounts/includes/UAPI.php on line 39
[19-Jul-2022 08:55:38 UTC] PHP Fatal error: Uncaught TypeError: json_decode() expects parameter 1 to be string, null given in /wp-content/plugins/wf-cpanel-email-accounts/includes/UAPI.php:39
Stack trace:
#0 /wp-content/plugins/wf-cpanel-email-accounts/includes/UAPI.php(39): json_decode()
#1 /wp-content/plugins/wf-cpanel-email-accounts/includes/UAPI.php(52): WebFacing\cPanel\UAPI::result()
#2 /wp-content/plugins/wf-cpanel-email-accounts/includes/Main.php(78): WebFacing\cPanel\UAPI::has_features()
#3 /wp-content/plugins/wf-cpanel-email-accounts/index.php(60): WebFacing\cPanel\Email\Main::admin()
#4 /wp-admin/includes/plugin.php(2313): include_once('/opt/bitnami/ap...')
#5 /wp-admin/plugins.php(192): plugin_sandbox_scrape()
#6 {main}
thrown in /wp-content/plugins/wf-cpanel-email-accounts/includes/UAPI.php on line 39