Does WP Legal Pages work with WordPress 6.7.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: 194.86 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.7.1 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 10,000+ |
WordPress.org page | https://wordpress.org/plugins/wplegalpages/ |
Badges |
|
URL | /wp-admin/admin.php?page=legal-pages |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=wplegalpages%2Fwplegalpages.php&plugin_status=all&paged=1&s&_wpnonce=0bc4050056 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 1.536 s |
Memory usage | 3.96 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=legal-pages |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.709 s |
Memory usage | 3.95 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=gdpr-cookie-consent |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.561 s |
Memory usage | 3.66 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.214 s |
Memory usage | 3.52 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/widgets.php |
---|---|
Aspect | new-sidebar-widgets |
HTTP status | 200 |
Load time | 1.478 s |
Memory usage | 6.02 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.270 s | 0.374 s | +0.104 s | 3.48 MiB | 3.68 MiB | + 203.65 KiB |
/wp-admin/edit.php | 0.186 s | 0.185 s | -0.001 s | 3.54 MiB | 3.74 MiB | + 203.72 KiB |
/wp-admin/post-new.php | 0.730 s | 0.840 s | +0.110 s | 5.92 MiB | 6.19 MiB | + 269.59 KiB |
/wp-admin/upload.php | 0.521 s | 0.306 s | -0.215 s | 3.49 MiB | 3.68 MiB | + 187.25 KiB |
/wp-admin/options-writing.php | 0.208 s | 0.172 s | -0.036 s | 3.47 MiB | 3.66 MiB | + 190.3 KiB |
/wp-admin/media-new.php | 0.251 s | 0.207 s | -0.044 s | 3.46 MiB | 3.66 MiB | + 198.5 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.184 s | 0.174 s | -0.010 s | 3.48 MiB | 3.68 MiB | + 209.17 KiB |
/wp-admin/post-new.php?post_type=page | 0.519 s | 0.832 s | +0.313 s | 5.92 MiB | 6.18 MiB | + 264.49 KiB |
/wp-admin/options-discussion.php | 0.274 s | 0.250 s | -0.024 s | 3.47 MiB | 3.66 MiB | + 186.8 KiB |
/wp-admin/edit-comments.php | 0.188 s | 0.184 s | -0.004 s | 3.49 MiB | 3.68 MiB | + 186.3 KiB |
/ | 0.272 s | 0.193 s | -0.079 s | 3.48 MiB | 3.52 MiB | + 43.64 KiB |
Average | 0.328 s | 0.338 s | +0.010 s | 3.93 MiB | 4.12 MiB | + 194.86 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 | |
---|---|---|---|---|---|
JavaScript | 39.4% | 15,279 | 2,049 | 29 | |
PHP | 36.4% | 14,146 | 2,950 | 42 | |
CSS | 13.8% | 5,342 | 69 | 18 | |
JSON | 4.5% | 1,745 | 0 | 1 | |
HTML | 2.7% | 1,050 | 0 | 41 | |
SVG | 2.2% | 869 | 0 | 70 | |
PO File | 1.0% | 371 | 191 | 1 | |
XML | 0.0% | 18 | 0 | 1 | |
Total | 38,820 | 5,259 | 203 |
Lines of code | 10,515 |
---|---|
Total complexity | 1,940 |
Median class complexity | 25.0 |
Median method complexity | 3.0 |
Most complex class | WP_Legal_Pages_Admin |
Most complex function | WP_Legal_Pages_Wizard_Page::get_page_preview_text() |
Classes | 18 |
---|---|
Methods | 243 |
Functions | 34 |
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
23ID | Name |
---|---|
legal_pages | WPLegalPages |
[24-Dec-2024 10:18:45 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://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.8.0.) in /wp-includes/functions.php on line 6114