Does Parse.ly work with WordPress 6.1.1 and PHP 8.1.12? A smoke test was performed on .
1 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 59.35 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.
WordPress version | 6.1.1 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 1,000+ |
WordPress.org page | https://wordpress.org/plugins/wp-parsely/ |
Badges |
|
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=wp-parsely%2Fwp-parsely.php&plugin_status=all&paged=1&s&_wpnonce=5cf3911ddf |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.251 s |
Memory usage | 3.07 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/options-general.php?page=parsely |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.433 s |
Memory usage | 3.1 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.179 s |
Memory usage | 2.98 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/index.php |
---|---|
Aspect | new-meta-boxes |
HTTP status | 200 |
Load time | 0.466 s |
Memory usage | 3.12 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/widgets.php |
---|---|
Aspect | new-sidebar-widgets |
HTTP status | 200 |
Load time | 2.721 s |
Memory usage | 4.92 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.299 s | 0.301 s | +0.002 s | 3.05 MiB | 3.12 MiB | + 80.67 KiB |
/wp-admin/edit.php | 0.191 s | 0.210 s | +0.019 s | 3.07 MiB | 3.15 MiB | + 79.28 KiB |
/wp-admin/post-new.php | 0.803 s | 0.686 s | -0.117 s | 4.97 MiB | 5.01 MiB | + 39.79 KiB |
/wp-admin/upload.php | 0.663 s | 0.255 s | -0.408 s | 2.99 MiB | 3.05 MiB | + 60.27 KiB |
/wp-admin/options-writing.php | 0.175 s | 0.143 s | -0.032 s | 2.99 MiB | 3.03 MiB | + 46.85 KiB |
/wp-admin/media-new.php | 0.286 s | 0.210 s | -0.076 s | 2.97 MiB | 3.04 MiB | + 72.45 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.200 s | 0.327 s | +0.127 s | 2.98 MiB | 3.06 MiB | + 76.8 KiB |
/wp-admin/post-new.php?post_type=page | 0.619 s | 0.664 s | +0.045 s | 4.96 MiB | 4.99 MiB | + 34.38 KiB |
/wp-admin/options-discussion.php | 0.204 s | 0.298 s | +0.094 s | 2.97 MiB | 3.03 MiB | + 60.7 KiB |
/wp-admin/edit-comments.php | 0.207 s | 0.329 s | +0.122 s | 3 MiB | 3.06 MiB | + 59.43 KiB |
/ | 0.283 s | 0.338 s | +0.055 s | 2.94 MiB | 2.99 MiB | + 42.27 KiB |
Average | 0.357 s | 0.342 s | -0.015 s | 3.35 MiB | 3.41 MiB | + 59.35 KiB |
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 | |
---|---|---|---|---|---|
PHP | 58.1% | 3,731 | 3,345 | 62 | |
TypeScript | 30.0% | 1,925 | 430 | 42 | |
Sass | 8.4% | 537 | 31 | 9 | |
JSON | 1.7% | 112 | 0 | 3 | |
Markdown | 1.5% | 96 | 0 | 2 | |
JavaScript | 0.3% | 18 | 9 | 8 | |
CSS | 0.1% | 7 | 0 | 7 | |
Total | 6,426 | 3,815 | 133 |
Lines of code | 3,578 |
---|---|
Total complexity | 608 |
Median class complexity | 5.0 |
Median method complexity | 2.0 |
Most complex class | Parsely\UI\Settings_Page |
Most complex function | Parsely\UI\Settings_Page::validate_options() |
Classes | 47 |
---|---|
Methods | 226 |
Functions | 22 |
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.
wp_options
2ID | Name |
---|---|
parsely_recommended_widget | Parse.ly Recommended Widget |
{
"dashboard": {
"wp-parsely-dashboard-widget": {
"title": "Parse.ly Top Posts (Last 7 Days)",
"context": "normal"
}
}
}
[27-Feb-2023 12:41:08 UTC] PHP Notice: Function wp_enqueue_script() was called <strong>incorrectly</strong>. "wp-editor" script should not be enqueued together with the new widgets editor (wp-edit-widgets or wp-customize-widgets). Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.8.0.) in /wp-includes/functions.php on line 5835