Planaday API 1.7.0

Does Planaday API work with WordPress 5.1.1 and PHP 7.0.16? A smoke test was performed on .

Summary

Errors
26PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 83.52 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 version5.1.1
PHP version7.0.16
MySQL version5.7.17
PHP memory limit256M
Plugin Info
Last updated
Active installs <10
WordPress.org page https://wordpress.org/plugins/planaday-api/
Badges

Get badge code

Pages 4

Plugins ‹ Test site — WordPress

Page screenshot: Plugins ‹ Test site — WordPress
URL /wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL /wp-admin/plugins.php?action=activate&plugin=planaday-api%2Findex.php&plugin_status=all&paged=1&s&_wpnonce=4afd0f6ba4
Aspect after-activation
HTTP status 200
Load time 0.238 s
Memory usage 3.27 MiB
JS errors None
Resource errors None

Planaday

Page screenshot: Planaday
URL /wp-admin/admin.php?page=planaday-api%2Findex.php
Requested URL /wp-admin/admin.php?page=planaday-api/index.php
Aspect menu-item
HTTP status 200
Load time 0.153 s
Memory usage 3.24 MiB
JS errors None
Resource errors None

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.524 s
Memory usage 3.01 MiB
JS errors None
Resource errors None

Widgets ‹ Test site — WordPress

Page screenshot: Widgets ‹ Test site — WordPress
URL /wp-admin/widgets.php
Aspect new-sidebar-widgets
HTTP status 200
Load time 0.706 s
Memory usage 3.34 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.289 s0.210 s-0.079 s3.29 MiB3.33 MiB+ 49.37 KiB
/wp-admin/edit.php0.168 s0.187 s+0.019 s3.32 MiB3.36 MiB+ 43.01 KiB
/wp-admin/post-new.php1.075 s0.968 s-0.107 s4.92 MiB5.03 MiB+ 111.73 KiB
/wp-admin/upload.php0.507 s0.483 s-0.024 s3.15 MiB3.25 MiB+ 105.85 KiB
/wp-admin/options-writing.php0.205 s0.167 s-0.038 s3.14 MiB3.25 MiB+ 106.48 KiB
/wp-admin/media-new.php0.217 s0.206 s-0.011 s3.13 MiB3.24 MiB+ 108.04 KiB
/wp-admin/edit-tags.php?taxonomy=category0.187 s0.199 s+0.012 s3.17 MiB3.28 MiB+ 107.41 KiB
/wp-admin/post-new.php?post_type=page0.959 s0.848 s-0.111 s4.91 MiB5.01 MiB+ 104.47 KiB
/wp-admin/options-discussion.php0.232 s0.181 s-0.051 s3.14 MiB3.24 MiB+ 106.48 KiB
/wp-admin/edit-comments.php0.210 s0.176 s-0.034 s3.24 MiB3.28 MiB+ 41.6 KiB
/0.271 s0.257 s-0.014 s2.98 MiB3.01 MiB+ 34.31 KiB
Average 0.393 s0.353 s-0.040 s3.49 MiB3.57 MiB+ 83.52 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 2

Sidebar Widgets 2

ID Name
planaday_widget_cursusdetailsPlanaday cursusdetails
planaday_search_widgetPlanaday zoeken

PHP Error Log 26 lines

[15-Apr-2019 12:11:07 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:07 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:08 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:09 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:10 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:10 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:10 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:11 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:11 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:11 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:11 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:11 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:12 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:12 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:13 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:13 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:13 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:13 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:14 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:14 UTC] PHP Notice:  Undefined variable: available in /wp-content/plugins/planaday-api/includes/widget.php on line 38
[15-Apr-2019 12:11:14 UTC] PHP Notice:  Undefined variable: costs in /wp-content/plugins/planaday-api/includes/widget.php on line 44
[15-Apr-2019 12:11:14 UTC] PHP Notice:  Undefined variable: location in /wp-content/plugins/planaday-api/includes/widget.php on line 50
[15-Apr-2019 12:11:14 UTC] PHP Notice:  Undefined variable: daypartsamount in /wp-content/plugins/planaday-api/includes/widget.php on line 56
[15-Apr-2019 12:11:14 UTC] PHP Notice:  Undefined variable: startdate in /wp-content/plugins/planaday-api/includes/widget.php on line 62
[15-Apr-2019 12:11:15 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
[15-Apr-2019 12:11:15 UTC] PHP Notice:  wp_deregister_script was called <strong>incorrectly</strong>. Do not deregister the <code>jquery</code> script in the administration area. To target the front-end theme, use the <code>wp_enqueue_scripts</code> hook. 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.6.0.) in /wp-includes/functions.php on line 4667
See also: All tests for this plugin, How to Hide the "Planaday" Admin Menu