Planaday API 1.1.0
Does Planaday API work with WordPress 5.0.3 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: 43.66 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.0.3 |
|---|---|
| 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=0da9a8ade3 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.328 s |
| Memory usage | 3.21 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.233 s |
| Memory usage | 3.17 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.372 s |
| Memory usage | 2.95 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.770 s |
| Memory usage | 3.27 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.248 s | 0.296 s | +0.048 s | 3.22 MiB | 3.26 MiB | + 43.87 KiB |
| /wp-admin/edit.php | 0.184 s | 0.222 s | +0.038 s | 3.25 MiB | 3.29 MiB | + 43.01 KiB |
| /wp-admin/post-new.php | 1.050 s | 0.925 s | -0.125 s | 4.92 MiB | 4.96 MiB | + 47.73 KiB |
| /wp-admin/upload.php | 0.418 s | 0.369 s | -0.049 s | 3.15 MiB | 3.19 MiB | + 40.77 KiB |
| /wp-admin/options-writing.php | 0.188 s | 0.178 s | -0.010 s | 3.17 MiB | 3.18 MiB | + 12.18 KiB |
| /wp-admin/media-new.php | 0.198 s | 0.270 s | +0.072 s | 3.07 MiB | 3.17 MiB | + 107.13 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.173 s | 0.238 s | +0.065 s | 3.17 MiB | 3.21 MiB | + 43.41 KiB |
| /wp-admin/post-new.php?post_type=page | 0.956 s | 0.868 s | -0.088 s | 4.9 MiB | 4.94 MiB | + 40.47 KiB |
| /wp-admin/options-discussion.php | 0.226 s | 0.240 s | +0.014 s | 3.07 MiB | 3.18 MiB | + 105.88 KiB |
| /wp-admin/edit-comments.php | 0.206 s | 0.220 s | +0.014 s | 3.18 MiB | 3.22 MiB | + 40.51 KiB |
| / | 0.280 s | 0.229 s | -0.051 s | 3 MiB | 2.96 MiB | - 44.74 KiB |
| Average | 0.375 s | 0.369 s | -0.007 s | 3.46 MiB | 3.51 MiB | + 43.66 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
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32:15 UTC] PHP Notice: Undefined variable: available in /wp-content/plugins/planaday-api/includes/widget.php on line 38
[26-Jan-2019 01:32:15 UTC] PHP Notice: Undefined variable: costs in /wp-content/plugins/planaday-api/includes/widget.php on line 44
[26-Jan-2019 01:32:15 UTC] PHP Notice: Undefined variable: location in /wp-content/plugins/planaday-api/includes/widget.php on line 50
[26-Jan-2019 01:32:15 UTC] PHP Notice: Undefined variable: daypartsamount in /wp-content/plugins/planaday-api/includes/widget.php on line 56
[26-Jan-2019 01:32:15 UTC] PHP Notice: Undefined variable: startdate in /wp-content/plugins/planaday-api/includes/widget.php on line 62
[26-Jan-2019 01:32: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 4231
[26-Jan-2019 01:32: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 4231