Planaday API 1.8.2
Does Planaday API work with WordPress 5.2.2 and PHP 7.2.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.77 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.2 |
|---|---|
| PHP version | 7.2.16 |
| MySQL version | 8.0.15 |
| 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=3e8d19e0e1 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.984 s |
| Memory usage | 3.53 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.287 s |
| Memory usage | 3.49 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.420 s |
| Memory usage | 3.27 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.838 s |
| Memory usage | 3.65 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.326 s | 0.290 s | -0.036 s | 3.6 MiB | 3.65 MiB | + 49.05 KiB |
| /wp-admin/edit.php | 0.259 s | 0.326 s | +0.067 s | 3.63 MiB | 3.67 MiB | + 42.73 KiB |
| /wp-admin/post-new.php | 1.182 s | 1.043 s | -0.139 s | 5.27 MiB | 5.38 MiB | + 111.01 KiB |
| /wp-admin/upload.php | 0.830 s | 0.474 s | -0.356 s | 3.46 MiB | 3.5 MiB | + 40.52 KiB |
| /wp-admin/options-writing.php | 0.200 s | 0.165 s | -0.035 s | 3.55 MiB | 3.49 MiB | - 52.25 KiB |
| /wp-admin/media-new.php | 0.278 s | 0.323 s | +0.045 s | 3.45 MiB | 3.49 MiB | + 42.85 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.218 s | 0.313 s | +0.095 s | 3.48 MiB | 3.58 MiB | + 97.7 KiB |
| /wp-admin/post-new.php?post_type=page | 0.983 s | 1.034 s | +0.051 s | 5.25 MiB | 5.35 MiB | + 104.22 KiB |
| /wp-admin/options-discussion.php | 0.523 s | 0.776 s | +0.253 s | 3.45 MiB | 3.49 MiB | + 41.63 KiB |
| /wp-admin/edit-comments.php | 0.232 s | 0.236 s | +0.004 s | 3.55 MiB | 3.59 MiB | + 40.26 KiB |
| / | 0.420 s | 0.379 s | -0.041 s | 3.3 MiB | 3.27 MiB | - 36.27 KiB |
| Average | 0.496 s | 0.487 s | -0.008 s | 3.82 MiB | 3.86 MiB | + 43.77 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
[28-Jun-2019 15:22: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
[28-Jun-2019 15:22: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
[28-Jun-2019 15:22: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
[28-Jun-2019 15:22: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
[28-Jun-2019 15:22: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
[28-Jun-2019 15:22: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
[28-Jun-2019 15:22: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
[28-Jun-2019 15:22:35 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
[28-Jun-2019 15:22:35 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
[28-Jun-2019 15:22: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
[28-Jun-2019 15:22: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
[28-Jun-2019 15:22: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
[28-Jun-2019 15:22: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
[28-Jun-2019 15:22:37 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
[28-Jun-2019 15:22:38 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
[28-Jun-2019 15:22:38 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
[28-Jun-2019 15:22:38 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
[28-Jun-2019 15:22:39 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
[28-Jun-2019 15:22:39 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
[28-Jun-2019 15:22:39 UTC] PHP Notice: Undefined variable: available in /wp-content/plugins/planaday-api/includes/widget.php on line 38
[28-Jun-2019 15:22:39 UTC] PHP Notice: Undefined variable: costs in /wp-content/plugins/planaday-api/includes/widget.php on line 44
[28-Jun-2019 15:22:39 UTC] PHP Notice: Undefined variable: location in /wp-content/plugins/planaday-api/includes/widget.php on line 50
[28-Jun-2019 15:22:39 UTC] PHP Notice: Undefined variable: daypartsamount in /wp-content/plugins/planaday-api/includes/widget.php on line 56
[28-Jun-2019 15:22:39 UTC] PHP Notice: Undefined variable: startdate in /wp-content/plugins/planaday-api/includes/widget.php on line 62
[28-Jun-2019 15:22:41 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
[28-Jun-2019 15:22:41 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