1. Home
2. WP Adsterra Dashboard
3. 1.2.4

WP Adsterra Dashboard 1.2.4

Does WP Adsterra Dashboard work with WordPress 6.5.4 and PHP 8.1.12? A smoke test was performed on 2024-06-09 11:43:20 UTC.

Summary

Pages 4

Plugins ‹ Test site — WordPress

Settings → Adsterra Settings

Test site – Just another WordPress site

Dashboard ‹ Test site — WordPress

Benchmark

URL	Load time			Memory usage
	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/index.php	0.371 s	0.321 s	-0.050 s	3.44 MiB	3.46 MiB	+ 27.81 KiB
/wp-admin/edit.php	0.219 s	0.175 s	-0.044 s	3.46 MiB	3.48 MiB	+ 20.65 KiB
/wp-admin/post-new.php	0.868 s	0.563 s	-0.305 s	5.59 MiB	5.61 MiB	+ 24.16 KiB
/wp-admin/upload.php	0.591 s	0.487 s	-0.104 s	3.38 MiB	3.38 MiB	+ 3.28 KiB
/wp-admin/options-writing.php	0.211 s	0.192 s	-0.019 s	3.37 MiB	3.37 MiB	- 2.63 KiB
/wp-admin/media-new.php	0.286 s	0.221 s	-0.065 s	3.35 MiB	3.37 MiB	+ 17.6 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.181 s	0.174 s	-0.007 s	3.37 MiB	3.39 MiB	+ 20.64 KiB
/wp-admin/post-new.php?post_type=page	0.521 s	0.547 s	+0.026 s	5.58 MiB	5.6 MiB	+ 19.75 KiB
/wp-admin/options-discussion.php	0.262 s	0.308 s	+0.046 s	3.36 MiB	3.36 MiB	+ 5.91 KiB
/wp-admin/edit-comments.php	0.215 s	0.220 s	+0.005 s	3.39 MiB	3.39 MiB	+ 3.27 KiB
/	0.287 s	0.182 s	-0.105 s	3.42 MiB	3.38 MiB	- 37.82 KiB
Average	0.365 s	0.308 s	-0.057 s	3.79 MiB	3.8 MiB	+ 9.33 KiB

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	88.0%	411	23	2
	CSS	7.7%	36	2	1
	JavaScript	4.3%	20	6	2
Total			467	31	5

PHP Code Analysis | More results »

Additions

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.

Meta Boxes

{
    "dashboard": {
        "adsterra_dashboard_widget": {
            "title": "Earnings Dashboard for Adsterra",
            "context": "normal"
        }
    }
}

PHP Error Log 4 lines

[09-Jun-2024 11:43:39 UTC] PHP Notice:  Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6078
[09-Jun-2024 11:43:41 UTC] PHP Notice:  Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6078
[09-Jun-2024 11:43:50 UTC] PHP Notice:  Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6078
[09-Jun-2024 11:43:50 UTC] PHP Notice:  Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see <a>Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6078

---