Does Pattern Wrangler work with WordPress 7.0.1 and PHP 8.1.12? A smoke test was performed on .
| 12 | PHP notices |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Memory usage: 185.63 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 | 7.0.1 |
|---|---|
| PHP version | 8.1.12 |
| MySQL version | 10.6.10 |
| PHP memory limit | 512M |
| Last updated | |
|---|---|
| Active installs | 400+ |
| WordPress.org page | https://wordpress.org/plugins/pattern-wrangler/ |
| Badges |
|
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=pattern-wrangler%2Fpattern-wrangler.php&plugin_status=all&paged=1&s&_wpnonce=4c16f50a3f |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.571 s |
| Memory usage | 4.11 MiB |
| JS errors | None |
| Resource errors | None |
| URL | /wp-admin/admin.php?page=pattern-wrangler-view |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.631 s |
| Memory usage | 4.02 MiB |
| JS errors | None |
| Resource errors | None |
| URL | /wp-admin/admin.php?page=pattern-wrangler-categories-view |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 1.159 s |
| Memory usage | 4.02 MiB |
| JS errors | None |
| Resource errors | None |
| URL | /wp-admin/admin.php?page=pattern-wrangler |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.766 s |
| Memory usage | 4.02 MiB |
| JS errors | None |
| Resource errors | None |
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.171 s |
| Memory usage | 4.36 MiB |
| JS errors | None |
| Resource errors | None |
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.766 s | 0.586 s | -0.180 s | 3.93 MiB | 4.09 MiB | + 172.34 KiB |
| /wp-admin/edit.php | 0.963 s | 0.531 s | -0.432 s | 3.98 MiB | 4.15 MiB | + 173.8 KiB |
| /wp-admin/post-new.php | 1.702 s | 1.461 s | -0.241 s | 6.56 MiB | 6.85 MiB | + 301.55 KiB |
| /wp-admin/upload.php | 1.400 s | 0.912 s | -0.488 s | 3.89 MiB | 4.04 MiB | + 154.9 KiB |
| /wp-admin/options-writing.php | 0.568 s | 0.481 s | -0.087 s | 3.86 MiB | 4.02 MiB | + 158.89 KiB |
| /wp-admin/media-new.php | 0.693 s | 0.536 s | -0.157 s | 3.85 MiB | 4.02 MiB | + 167.09 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.497 s | 0.518 s | +0.021 s | 3.86 MiB | 4.03 MiB | + 172.26 KiB |
| /wp-admin/post-new.php?post_type=page | 2.617 s | 1.893 s | -0.724 s | 6.55 MiB | 6.84 MiB | + 293.8 KiB |
| /wp-admin/options-discussion.php | 0.566 s | 0.601 s | +0.035 s | 3.86 MiB | 4.02 MiB | + 155.39 KiB |
| /wp-admin/edit-comments.php | 0.531 s | 0.521 s | -0.010 s | 3.89 MiB | 4.04 MiB | + 154.89 KiB |
| / | 0.283 s | 0.172 s | -0.111 s | 4.23 MiB | 4.36 MiB | + 136.98 KiB |
| Average | 0.962 s | 0.747 s | -0.216 s | 4.41 MiB | 4.59 MiB | + 185.63 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 | 97.5% | 5,108 | 1,988 | 29 | |
| JavaScript | 1.7% | 88 | 100 | 6 | |
| JSON | 0.6% | 33 | 0 | 2 | |
| CSS | 0.2% | 8 | 0 | 6 | |
| Total | 5,237 | 2,088 | 43 | ||
| Lines of code | 4,728 |
|---|---|
| Total complexity | 898 |
| Median class complexity | 28.0 |
| Median method complexity | 3.0 |
| Most complex class | DLXPlugins\PatternWrangler\Rest |
| Most complex function | DLXPlugins\PatternWrangler\Rest::rest_get_all_patterns() |
| Classes | 15 |
|---|---|
| Methods | 202 |
| Functions | 2 |
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 1| ID | Name |
|---|---|
| pw_versions | Pattern versions |
[15-Jul-2026 19:34:27 UTC] PHP Notice: Function wp_add_privacy_policy_content was called <strong>incorrectly</strong>. The suggested privacy policy content should be added only in wp-admin by using the <code>admin_init</code> (or later) action. 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 4.9.7.) in /wp-includes/functions.php on line 6170
[15-Jul-2026 19:34:27 UTC] PHP Notice: Function wp_add_privacy_policy_content was called <strong>incorrectly</strong>. The suggested privacy policy content should be added only in wp-admin by using the <code>admin_init</code> (or later) action. 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 4.9.7.) in /wp-includes/functions.php on line 6170
[15-Jul-2026 19:34:27 UTC] PHP Notice: Function wp_add_privacy_policy_content was called <strong>incorrectly</strong>. The suggested privacy policy content should be added only in wp-admin by using the <code>admin_init</code> (or later) action. 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 4.9.7.) in /wp-includes/functions.php on line 6170
[15-Jul-2026 19:34:27 UTC] PHP Notice: Function wp_add_privacy_policy_content was called <strong>incorrectly</strong>. The suggested privacy policy content should be added only in wp-admin by using the <code>admin_init</code> (or later) action. 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 4.9.7.) in /wp-includes/functions.php on line 6170
[15-Jul-2026 19:34:27 UTC] PHP Notice: Function wp_add_privacy_policy_content was called <strong>incorrectly</strong>. The suggested privacy policy content should be added only in wp-admin by using the <code>admin_init</code> (or later) action. 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 4.9.7.) in /wp-includes/functions.php on line 6170
[15-Jul-2026 19:34:27 UTC] PHP Notice: Function wp_add_privacy_policy_content was called <strong>incorrectly</strong>. The suggested privacy policy content should be added only in wp-admin by using the <code>admin_init</code> (or later) action. 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 4.9.7.) in /wp-includes/functions.php on line 6170
[15-Jul-2026 19:34:32 UTC] PHP Notice: Function wp_add_privacy_policy_content was called <strong>incorrectly</strong>. The suggested privacy policy content should be added only in wp-admin by using the <code>admin_init</code> (or later) action. 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 4.9.7.) in /wp-includes/functions.php on line 6170
[15-Jul-2026 19:34:32 UTC] PHP Notice: Function wp_add_privacy_policy_content was called <strong>incorrectly</strong>. The suggested privacy policy content should be added only in wp-admin by using the <code>admin_init</code> (or later) action. 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 4.9.7.) in /wp-includes/functions.php on line 6170
[15-Jul-2026 19:34:32 UTC] PHP Notice: Function wp_add_privacy_policy_content was called <strong>incorrectly</strong>. The suggested privacy policy content should be added only in wp-admin by using the <code>admin_init</code> (or later) action. 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 4.9.7.) in /wp-includes/functions.php on line 6170
[15-Jul-2026 19:34:32 UTC] PHP Notice: Function wp_add_privacy_policy_content was called <strong>incorrectly</strong>. The suggested privacy policy content should be added only in wp-admin by using the <code>admin_init</code> (or later) action. 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 4.9.7.) in /wp-includes/functions.php on line 6170
[15-Jul-2026 19:34:32 UTC] PHP Notice: Function WP_Script_Modules::register was called <strong>incorrectly</strong>. The script module with the ID "@wordpress/block-library/navigation/view" was enqueued with dependencies that are not registered: @wordpress/interactivity. 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 6.9.1.) in /wp-includes/functions.php on line 6170
[15-Jul-2026 19:34:32 UTC] PHP Notice: Function WP_Script_Modules::register was called <strong>incorrectly</strong>. The script module with the ID "@wordpress/block-library/navigation/view" was enqueued with dependencies that are not registered: @wordpress/interactivity. 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 6.9.1.) in /wp-includes/functions.php on line 6170