Planaday API 1.7.0
Does Planaday API work with WordPress 5.2 and PHP 7.0.16? A smoke test was performed on .
Summary
Errors
| 26 | PHP 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:
insignificant.
The plugin didn't make the site noticeably slower.
Environment
| WordPress version | 5.2 |
|---|---|
| PHP version | 7.0.16 |
| MySQL version | 5.7.17 |
| PHP memory limit | 256M |
Plugin Info
| Last updated | |
|---|---|
| Active installs | 50+ |
| WordPress.org page | https://wordpress.org/plugins/planaday-api/ |
| Badges |
|
Pages 4
Screenshots are not available.
Old screenshots of less popular plugins are eventually deleted to save disk space.
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=d6838777cc |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.368 s |
| Memory usage | 3.46 MiB |
| JS errors | None |
| Resource errors | None |
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.258 s |
| Memory usage | 3.42 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.632 s |
| Memory usage | 3.2 MiB |
| JS errors | None |
| Resource errors | None |
Widgets ‹ Test site — WordPress
| URL | /wp-admin/widgets.php |
|---|---|
| Aspect | new-sidebar-widgets |
| HTTP status | 200 |
| Load time | 0.974 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.php | 0.351 s | 0.385 s | +0.034 s | 3.47 MiB | 3.52 MiB | + 49.37 KiB |
| /wp-admin/edit.php | 0.202 s | 0.262 s | +0.060 s | 3.5 MiB | 3.54 MiB | + 43.01 KiB |
| /wp-admin/post-new.php | 1.087 s | 1.328 s | +0.241 s | 5.26 MiB | 5.3 MiB | + 47.73 KiB |
| /wp-admin/upload.php | 0.450 s | 0.493 s | +0.043 s | 3.33 MiB | 3.44 MiB | + 105.85 KiB |
| /wp-admin/options-writing.php | 0.198 s | 0.224 s | +0.026 s | 3.32 MiB | 3.43 MiB | + 106.48 KiB |
| /wp-admin/media-new.php | 0.252 s | 0.266 s | +0.014 s | 3.32 MiB | 3.42 MiB | + 108.04 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.186 s | 0.238 s | +0.052 s | 3.42 MiB | 3.46 MiB | + 43.41 KiB |
| /wp-admin/post-new.php?post_type=page | 1.103 s | 1.051 s | -0.052 s | 5.24 MiB | 5.28 MiB | + 40.47 KiB |
| /wp-admin/options-discussion.php | 0.366 s | 0.322 s | -0.044 s | 3.32 MiB | 3.42 MiB | + 106.48 KiB |
| /wp-admin/edit-comments.php | 0.365 s | 0.239 s | -0.126 s | 3.42 MiB | 3.47 MiB | + 41.6 KiB |
| / | 0.430 s | 0.318 s | -0.112 s | 3.17 MiB | 3.2 MiB | + 34.31 KiB |
| Average | 0.454 s | 0.466 s | +0.012 s | 3.71 MiB | 3.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
- widget_planaday_search_widget
- widget_planaday_widget_cursusdetails
Sidebar Widgets 2
| ID | Name |
|---|---|
| planaday_widget_cursusdetails | Planaday cursusdetails |
| planaday_search_widget | Planaday zoeken |
PHP Error Log 26 lines
[15-May-2019 06:53:16 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
[15-May-2019 06:53:16 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
[15-May-2019 06:53:17 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
[15-May-2019 06:53:19 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
[15-May-2019 06:53:19 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
[15-May-2019 06:53:19 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
[15-May-2019 06:53:19 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
[15-May-2019 06:53:21 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
[15-May-2019 06:53:21 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
[15-May-2019 06:53:21 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
[15-May-2019 06:53:21 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
[15-May-2019 06:53:22 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
[15-May-2019 06:53:22 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
[15-May-2019 06:53:22 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
[15-May-2019 06:53:23 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
[15-May-2019 06:53:23 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
[15-May-2019 06:53:24 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
[15-May-2019 06:53:24 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
[15-May-2019 06:53:24 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
[15-May-2019 06:53:24 UTC] PHP Notice: Undefined variable: available in /wp-content/plugins/planaday-api/includes/widget.php on line 38
[15-May-2019 06:53:24 UTC] PHP Notice: Undefined variable: costs in /wp-content/plugins/planaday-api/includes/widget.php on line 44
[15-May-2019 06:53:24 UTC] PHP Notice: Undefined variable: location in /wp-content/plugins/planaday-api/includes/widget.php on line 50
[15-May-2019 06:53:24 UTC] PHP Notice: Undefined variable: daypartsamount in /wp-content/plugins/planaday-api/includes/widget.php on line 56
[15-May-2019 06:53:24 UTC] PHP Notice: Undefined variable: startdate in /wp-content/plugins/planaday-api/includes/widget.php on line 62
[15-May-2019 06:53: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
[15-May-2019 06:53: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