Planaday API 1.8.2

Does Planaday API work with WordPress 5.2.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: 66.07 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: 0.032 seconds
The average page load time increased by this amount after activating the plugin.

Environment
WordPress version5.2.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=c1d6e17aac
Aspect after-activation
HTTP status 200
Load time 0.630 s
Memory usage 3.46 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.229 s
Memory usage 3.42 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.553 s
Memory usage 3.2 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 1.017 s
Memory usage 3.52 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.312 s0.391 s+0.079 s3.47 MiB3.52 MiB+ 49.37 KiB
/wp-admin/edit.php0.242 s0.287 s+0.045 s3.5 MiB3.54 MiB+ 43.01 KiB
/wp-admin/post-new.php1.282 s1.413 s+0.131 s5.26 MiB5.3 MiB+ 47.73 KiB
/wp-admin/upload.php0.536 s0.420 s-0.116 s3.33 MiB3.44 MiB+ 105.85 KiB
/wp-admin/options-writing.php0.185 s0.200 s+0.015 s3.32 MiB3.43 MiB+ 106.48 KiB
/wp-admin/media-new.php0.205 s0.242 s+0.037 s3.32 MiB3.42 MiB+ 108.04 KiB
/wp-admin/edit-tags.php?taxonomy=category0.189 s0.246 s+0.057 s3.42 MiB3.46 MiB+ 43.41 KiB
/wp-admin/post-new.php?post_type=page1.040 s1.178 s+0.138 s5.24 MiB5.28 MiB+ 40.47 KiB
/wp-admin/options-discussion.php0.289 s0.284 s-0.005 s3.32 MiB3.42 MiB+ 106.48 KiB
/wp-admin/edit-comments.php0.276 s0.288 s+0.012 s3.42 MiB3.47 MiB+ 41.6 KiB
/0.366 s0.320 s-0.046 s3.17 MiB3.2 MiB+ 34.31 KiB
Average 0.447 s0.479 s+0.032 s3.71 MiB3.77 MiB+ 66.07 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

[10-Jun-2019 04:03:25 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 4773
[10-Jun-2019 04:03:26 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 4773
[10-Jun-2019 04:03:26 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 4773
[10-Jun-2019 04:03:28 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 4773
[10-Jun-2019 04:03:29 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 4773
[10-Jun-2019 04:03:29 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 4773
[10-Jun-2019 04:03:29 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 4773
[10-Jun-2019 04:03:31 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 4773
[10-Jun-2019 04:03:31 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 4773
[10-Jun-2019 04:03:31 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 4773
[10-Jun-2019 04:03:31 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 4773
[10-Jun-2019 04:03:31 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 4773
[10-Jun-2019 04:03:32 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 4773
[10-Jun-2019 04:03:32 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 4773
[10-Jun-2019 04:03:33 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 4773
[10-Jun-2019 04:03:33 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 4773
[10-Jun-2019 04:03:33 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 4773
[10-Jun-2019 04:03:34 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 4773
[10-Jun-2019 04:03:34 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 4773
[10-Jun-2019 04:03:34 UTC] PHP Notice:  Undefined variable: available in /wp-content/plugins/planaday-api/includes/widget.php on line 38
[10-Jun-2019 04:03:34 UTC] PHP Notice:  Undefined variable: costs in /wp-content/plugins/planaday-api/includes/widget.php on line 44
[10-Jun-2019 04:03:34 UTC] PHP Notice:  Undefined variable: location in /wp-content/plugins/planaday-api/includes/widget.php on line 50
[10-Jun-2019 04:03:34 UTC] PHP Notice:  Undefined variable: daypartsamount in /wp-content/plugins/planaday-api/includes/widget.php on line 56
[10-Jun-2019 04:03:34 UTC] PHP Notice:  Undefined variable: startdate in /wp-content/plugins/planaday-api/includes/widget.php on line 62
[10-Jun-2019 04:03:36 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 4773
[10-Jun-2019 04:03:36 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 4773
See also: All tests for this plugin, How to Hide the "Planaday" Admin Menu