1. Home
2. PJ News Ticker
3. 1.2.1

PJ News Ticker 1.2.1

Does PJ News Ticker work with WordPress 4.9.6 and PHP 7.0.16? A smoke test was performed on 2018-06-19 10:57:35 UTC.

Summary

Pages 3

Plugins ‹ Test site — WordPress

Settings → PJ News Ticker

Test site – Just another WordPress site

Benchmark

URL	Load time			Memory usage
	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/index.php	0.116 s	0.094 s	-0.022 s	3.1 MiB	3.13 MiB	+ 25.3 KiB
/wp-admin/edit.php	0.099 s	0.079 s	-0.020 s	3.13 MiB	3.15 MiB	+ 23.08 KiB
/wp-admin/post-new.php	0.178 s	0.078 s	-0.100 s	3.19 MiB	3.22 MiB	+ 29.94 KiB
/wp-admin/upload.php	0.106 s	0.061 s	-0.045 s	2.96 MiB	2.98 MiB	+ 22.99 KiB
/wp-admin/options-writing.php	0.093 s	0.111 s	+0.018 s	2.95 MiB	2.98 MiB	+ 23.88 KiB
/wp-admin/media-new.php	0.044 s	0.045 s	+0.001 s	2.94 MiB	2.97 MiB	+ 23.93 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.091 s	0.084 s	-0.007 s	2.98 MiB	3.01 MiB	+ 24.24 KiB
/wp-admin/post-new.php?post_type=page	0.191 s	0.192 s	+0.001 s	3.2 MiB	3.22 MiB	+ 22.68 KiB
/wp-admin/options-discussion.php	0.074 s	0.081 s	+0.007 s	2.95 MiB	2.97 MiB	+ 23.88 KiB
/wp-admin/edit-comments.php	0.076 s	0.090 s	+0.014 s	2.99 MiB	3.04 MiB	+ 57.44 KiB
/	0.093 s	0.115 s	+0.022 s	2.73 MiB	2.74 MiB	+ 9.01 KiB
Average	0.106 s	0.094 s	-0.012 s	3.01 MiB	3.04 MiB	+ 26.03 KiB

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.

No new entries found.

PHP Error Log 4 lines

[19-Jun-2018 10:57:42 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4148
[19-Jun-2018 10:57:42 UTC] PHP Notice:  wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4148
[19-Jun-2018 10:57:45 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4148
[19-Jun-2018 10:57:45 UTC] PHP Notice:  wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4148

---