Tockify Events Calendar 2.0.0
Does Tockify Events Calendar work with WordPress 4.9.8 and PHP 7.0.16? A smoke test was performed on .
Summary
Errors
| 21 | PHP notices |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Performance
Memory usage: 22.91 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.
Environment
| WordPress version | 4.9.8 |
|---|---|
| PHP version | 7.0.16 |
| MySQL version | 5.7.17 |
| PHP memory limit | 256M |
Plugin Info
| Last updated | |
|---|---|
| Active installs | 2,000+ |
| WordPress.org page | https://wordpress.org/plugins/tockify-events-calendar/ |
| Badges |
|
Pages 4
Plugins ‹ Test site — WordPress
| URL | /wp-admin/plugins.php?activate=true&plugin_status=all&paged=1&s= |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=tockify-events-calendar%2Ftockify.php&plugin_status=all&paged=1&s&_wpnonce=0c6e734c12 |
| Aspect | after-activation |
| HTTP status | 200 OK |
| Load time | 0.132 s |
| Memory usage | 3.03 MiB |
| JS errors | None |
| Resource errors | None |
Tockify Calendar
| URL | /wp-admin/admin.php?page=tockify_calendar |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 OK |
| Load time | 0.078 s |
| Memory usage | 2.99 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 OK |
| Load time | 0.086 s |
| Memory usage | 2.77 MiB |
| JS errors | None |
| Resource errors | None |
Widgets ‹ Test site — WordPress
| URL | /wp-admin/widgets.php |
|---|---|
| Aspect | new-sidebar-widgets |
| HTTP status | 200 OK |
| Load time | 0.126 s |
| Memory usage | 3.06 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.120 s | 0.106 s | -0.014 s | 3.12 MiB | 3.14 MiB | + 19.67 KiB |
| /wp-admin/edit.php | 0.107 s | 0.108 s | +0.001 s | 3.14 MiB | 3.16 MiB | + 19.64 KiB |
| /wp-admin/post-new.php | 0.183 s | 0.203 s | +0.020 s | 3.21 MiB | 3.24 MiB | + 26.81 KiB |
| /wp-admin/upload.php | 0.092 s | 0.135 s | +0.043 s | 2.99 MiB | 3.01 MiB | + 20.16 KiB |
| /wp-admin/options-writing.php | 0.075 s | 0.096 s | +0.021 s | 2.98 MiB | 3 MiB | + 20.11 KiB |
| /wp-admin/media-new.php | 0.042 s | 0.068 s | +0.026 s | 2.97 MiB | 2.99 MiB | + 20.16 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.076 s | 0.101 s | +0.025 s | 3.01 MiB | 3.03 MiB | + 20.16 KiB |
| /wp-admin/post-new.php?post_type=page | 0.143 s | 0.161 s | +0.018 s | 3.22 MiB | 3.24 MiB | + 19.55 KiB |
| /wp-admin/options-discussion.php | 0.078 s | 0.085 s | +0.007 s | 2.97 MiB | 2.99 MiB | + 20.11 KiB |
| /wp-admin/edit-comments.php | 0.102 s | 0.098 s | -0.004 s | 3.01 MiB | 3.06 MiB | + 45.58 KiB |
| / | 0.085 s | 0.089 s | +0.004 s | 2.76 MiB | 2.78 MiB | + 20.11 KiB |
| Average | 0.100 s | 0.114 s | +0.013 s | 3.03 MiB | 3.06 MiB | + 22.91 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.
Options wp_options 1
- widget_register_minical_widget
Sidebar Widgets 1
| ID | Name |
|---|---|
| register_minical_widget | Tockify Mini Calendar |
PHP Error Log 21 lines
[22-Nov-2018 23:39:10 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:10 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:10 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:11 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:12 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:12 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:12 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:12 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:12 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:13 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:13 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:13 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:13 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:13 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:13 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:14 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:14 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:14 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:14 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:15 UTC] PHP Notice: wp_register_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 4161
[22-Nov-2018 23:39:15 UTC] PHP Notice: wp_register_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 4161