Does WP Adsterra Dashboard work with WordPress 5.9 and PHP 7.4.8? A smoke test was performed on .
4 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 18.8 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
insignificant.
The plugin didn't make the site noticeably slower.
WordPress version | 5.9 |
---|---|
PHP version | 7.4.8 |
MySQL version | 8.0.21 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 600+ |
WordPress.org page | https://wordpress.org/plugins/wp-adsterra-dashboard/ |
Badges |
|
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=wp-adsterra-dashboard%2Findex.php&plugin_status=all&paged=1&s&_wpnonce=b178d4691a |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.234 s |
Memory usage | 3.28 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/options-general.php?page=wp-adsterra-dashboard%2Findex.php |
---|---|
Requested URL | /wp-admin/options-general.php?page=wp-adsterra-dashboard/index.php |
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.240 s |
Memory usage | 3.24 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.242 s |
Memory usage | 3.36 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/index.php |
---|---|
Aspect | new-meta-boxes |
HTTP status | 200 |
Load time | 0.263 s |
Memory usage | 3.38 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.323 s | 0.261 s | -0.062 s | 3.36 MiB | 3.38 MiB | + 20.51 KiB |
/wp-admin/edit.php | 0.172 s | 0.178 s | +0.006 s | 3.39 MiB | 3.41 MiB | + 17.05 KiB |
/wp-admin/post-new.php | 0.784 s | 0.954 s | +0.170 s | 6.14 MiB | 6.17 MiB | + 20.93 KiB |
/wp-admin/upload.php | 0.339 s | 0.299 s | -0.040 s | 3.24 MiB | 3.26 MiB | + 18.05 KiB |
/wp-admin/options-writing.php | 0.221 s | 0.138 s | -0.083 s | 3.24 MiB | 3.25 MiB | + 9.91 KiB |
/wp-admin/media-new.php | 0.278 s | 0.181 s | -0.097 s | 3.22 MiB | 3.25 MiB | + 26.23 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.182 s | 0.172 s | -0.010 s | 3.25 MiB | 3.28 MiB | + 25 KiB |
/wp-admin/post-new.php?post_type=page | 0.887 s | 0.643 s | -0.244 s | 6.14 MiB | 6.16 MiB | + 16.52 KiB |
/wp-admin/options-discussion.php | 0.260 s | 0.266 s | +0.006 s | 3.22 MiB | 3.24 MiB | + 26.54 KiB |
/wp-admin/edit-comments.php | 0.292 s | 0.184 s | -0.108 s | 3.26 MiB | 3.28 MiB | + 15.91 KiB |
/ | 0.259 s | 0.199 s | -0.060 s | 3.35 MiB | 3.36 MiB | + 10.18 KiB |
Average | 0.363 s | 0.316 s | -0.047 s | 3.8 MiB | 3.82 MiB | + 18.8 KiB |
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 | 88.0% | 411 | 23 | 2 | |
CSS | 7.7% | 36 | 2 | 1 | |
JavaScript | 4.3% | 20 | 6 | 2 | |
Total | 467 | 31 | 5 |
Lines of code | 432 |
---|---|
Total complexity | 60 |
Median class complexity | 30.0 |
Median method complexity | 2.0 |
Most complex class | WPAdsterraDashboard |
Most complex function | WPAdsterraDashboard::adsterra_dashboard_widget() |
Classes | 2 |
---|---|
Methods | 16 |
Functions | 0 |
Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.
{
"dashboard": {
"adsterra_dashboard_widget": {
"title": "Earnings Dashboard for Adsterra",
"context": "normal"
}
}
}
[30-Jan-2022 11:42:01 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5768
[30-Jan-2022 11:42:02 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5768
[30-Jan-2022 11:42:09 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5768
[30-Jan-2022 11:42:09 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5768