WP Datepicker 1.9.0
Does WP Datepicker work with WordPress 5.7.1 and PHP 7.4.8? A smoke test was performed on .
Summary
Errors
| 5 | PHP warnings |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Performance
Memory usage: 89.34 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.7.1 |
|---|---|
| PHP version | 7.4.8 |
| MySQL version | 8.0.21 |
| PHP memory limit | 256M |
Plugin Info
| Last updated | |
|---|---|
| Active installs | 9,000+ |
| WordPress.org page | https://wordpress.org/plugins/wp-datepicker/ |
| Badges |
|
Pages 7
Plugins ‹ Test site — WordPress
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=wp-datepicker%2Findex.php&plugin_status=all&paged=1&s&_wpnonce=b7ac7d320c |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.387 s |
| Memory usage | 2.81 MiB |
| JS errors | None |
| Resource errors | None |
Settings → WP Datepicker
| URL | /wp-admin/options-general.php?page=wp_dp |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 2.541 s |
| Memory usage | 3.08 MiB |
| JS errors | None |
| Resource errors | None |
Settings → WP Datepicker → Date Range
| URL | /wp-admin/options-general.php?page=wp_dp |
|---|---|
| Aspect | menu-item-tab |
| HTTP status | 200 |
| Load time | 1.506 s |
| Memory usage | 2.93 MiB |
| JS errors | None |
| Resource errors | None |
Settings → WP Datepicker → Speed Optimization
| URL | /wp-admin/options-general.php?page=wp_dp |
|---|---|
| Aspect | menu-item-tab |
| HTTP status | 200 |
| Load time | 1.876 s |
| Memory usage | 2.93 MiB |
| JS errors | None |
| Resource errors | None |
Settings → WP Datepicker → Add-ons
| URL | /wp-admin/options-general.php?page=wp_dp |
|---|---|
| Aspect | menu-item-tab |
| HTTP status | 200 |
| Load time | 1.903 s |
| Memory usage | 2.93 MiB |
| JS errors | None |
| Resource errors | None |
Settings → WP Datepicker → Developer
| URL | /wp-admin/options-general.php?page=wp_dp |
|---|---|
| Aspect | menu-item-tab |
| HTTP status | 200 |
| Load time | 1.721 s |
| Memory usage | 2.93 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.664 s |
| Memory usage | 2.79 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.277 s | 0.382 s | +0.105 s | 2.82 MiB | 2.86 MiB | + 36.69 KiB |
| /wp-admin/edit.php | 0.185 s | 0.206 s | +0.021 s | 2.86 MiB | 2.9 MiB | + 37 KiB |
| /wp-admin/post-new.php | 0.867 s | 0.900 s | +0.033 s | 5.02 MiB | 5.19 MiB | + 167.45 KiB |
| /wp-admin/upload.php | 0.475 s | 0.270 s | -0.205 s | 2.7 MiB | 2.8 MiB | + 102.64 KiB |
| /wp-admin/options-writing.php | 0.256 s | 0.162 s | -0.094 s | 2.71 MiB | 2.78 MiB | + 71.59 KiB |
| /wp-admin/media-new.php | 0.222 s | 0.203 s | -0.019 s | 2.67 MiB | 2.77 MiB | + 102.81 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.179 s | 0.308 s | +0.129 s | 2.77 MiB | 2.81 MiB | + 38.87 KiB |
| /wp-admin/post-new.php?post_type=page | 1.107 s | 1.298 s | +0.191 s | 5.01 MiB | 5.17 MiB | + 167.05 KiB |
| /wp-admin/options-discussion.php | 0.287 s | 0.341 s | +0.054 s | 2.67 MiB | 2.76 MiB | + 83.77 KiB |
| /wp-admin/edit-comments.php | 0.241 s | 0.234 s | -0.007 s | 2.78 MiB | 2.81 MiB | + 36.23 KiB |
| / | 0.283 s | 0.248 s | -0.035 s | 2.65 MiB | 2.79 MiB | + 138.66 KiB |
| Average | 0.398 s | 0.414 s | +0.016 s | 3.15 MiB | 3.24 MiB | + 89.34 KiB |
Code Statistics
Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.
| Language | % | Lines of code | Comment lines | Files | |
|---|---|---|---|---|---|
| SVG | 53.0% | 9,517 | 9 | 4 | |
| PHP | 22.5% | 4,031 | 649 | 8 | |
| JavaScript | 15.9% | 2,860 | 356 | 78 | |
| PO File | 5.3% | 946 | 396 | 4 | |
| CSS | 3.3% | 601 | 12 | 3 | |
| Total | 17,955 | 1,422 | 97 | ||
PHP Code Analysis | More results »
| Lines of code | 3,703 |
|---|---|
| Total complexity | 758 |
| Median class complexity | 21.0 |
| Median method complexity | 2.0 |
| Most complex class | QRinput |
| Most complex function | wpdp_footer_scripts() |
| Classes | 21 |
|---|---|
| Methods | 169 |
| Functions | 25 |
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
- wp_datepicker_option-1
- wpdp_previous_version_compatible
PHP Error Log 5 lines
[15-Apr-2021 18:17:40 UTC] PHP Warning: extract() expects parameter 1 to be array, string given in /wp-content/plugins/wp-datepicker/inc/functions.php on line 814
[15-Apr-2021 18:17:43 UTC] PHP Warning: extract() expects parameter 1 to be array, string given in /wp-content/plugins/wp-datepicker/inc/functions.php on line 814
[15-Apr-2021 18:17:46 UTC] PHP Warning: extract() expects parameter 1 to be array, string given in /wp-content/plugins/wp-datepicker/inc/functions.php on line 814
[15-Apr-2021 18:17:48 UTC] PHP Warning: extract() expects parameter 1 to be array, string given in /wp-content/plugins/wp-datepicker/inc/functions.php on line 814
[15-Apr-2021 18:17:51 UTC] PHP Warning: extract() expects parameter 1 to be array, string given in /wp-content/plugins/wp-datepicker/inc/functions.php on line 814