Boxtal Connect 1.2.10
Does Boxtal Connect work with WordPress 5.8.1 and PHP 7.4.8? A smoke test was performed on .
Summary
Errors
| 14 | PHP notices |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Performance
Memory usage: 24.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.8.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/boxtal-connect/ |
| Badges |
|
Pages 2
Plugins ‹ Test site — WordPress
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=boxtal-connect%2Fboxtal-connect.php&plugin_status=all&paged=1&s&_wpnonce=06acf521c5 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.608 s |
| Memory usage | 3.08 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.257 s |
| Memory usage | 2.93 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.284 s | 0.266 s | -0.018 s | 3.08 MiB | 3.1 MiB | + 18.71 KiB |
| /wp-admin/edit.php | 0.162 s | 0.232 s | +0.070 s | 3.11 MiB | 3.2 MiB | + 85.73 KiB |
| /wp-admin/post-new.php | 0.818 s | 0.658 s | -0.160 s | 5.27 MiB | 5.29 MiB | + 23.5 KiB |
| /wp-admin/upload.php | 0.511 s | 0.336 s | -0.175 s | 3.03 MiB | 3.05 MiB | + 18.49 KiB |
| /wp-admin/options-writing.php | 0.162 s | 0.178 s | +0.016 s | 3.02 MiB | 3.03 MiB | + 3.41 KiB |
| /wp-admin/media-new.php | 0.207 s | 0.212 s | +0.005 s | 3.01 MiB | 3.03 MiB | + 18.98 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.169 s | 0.196 s | +0.027 s | 3.04 MiB | 3.06 MiB | + 19.57 KiB |
| /wp-admin/post-new.php?post_type=page | 0.604 s | 0.683 s | +0.079 s | 5.26 MiB | 5.28 MiB | + 23.42 KiB |
| /wp-admin/options-discussion.php | 0.201 s | 0.295 s | +0.094 s | 3 MiB | 3.02 MiB | + 20.23 KiB |
| /wp-admin/edit-comments.php | 0.186 s | 0.241 s | +0.055 s | 3.04 MiB | 3.06 MiB | + 17.56 KiB |
| / | 0.277 s | 0.343 s | +0.066 s | 2.91 MiB | 2.93 MiB | + 18.14 KiB |
| Average | 0.326 s | 0.331 s | +0.005 s | 3.43 MiB | 3.46 MiB | + 24.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 | |
|---|---|---|---|---|---|
| PHP | 82.8% | 3,904 | 2,959 | 66 | |
| CSS | 17.1% | 807 | 19 | 8 | |
| JSON | 0.1% | 3 | 0 | 1 | |
| Total | 4,714 | 2,978 | 75 | ||
PHP Code Analysis | More results »
| Lines of code | 3,371 |
|---|---|
| Total complexity | 855 |
| Median class complexity | 10.0 |
| Median method complexity | 2.0 |
| Most complex class | Boxtal\BoxtalConnectWoocommerce\Util\Order_Util |
| Most complex function | Boxtal\BoxtalConnectWoocommerce\Util\Parcelpoint_Util::normalize_parcelpoint() |
| Classes | 45 |
|---|---|
| Methods | 292 |
| Functions | 26 |
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.
Database Tables 1
- wp_bw_pricing_items
Options wp_options 2
- BW_NOTICE_environment-warning
- BW_NOTICES
PHP Error Log 14 lines
[10-Sep-2021 06:05:21 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[10-Sep-2021 06:05:21 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[10-Sep-2021 06:05:22 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[10-Sep-2021 06:05:23 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[10-Sep-2021 06:05:23 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[10-Sep-2021 06:05:25 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[10-Sep-2021 06:05:25 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[10-Sep-2021 06:05:25 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[10-Sep-2021 06:05:26 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[10-Sep-2021 06:05:26 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[10-Sep-2021 06:05:27 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[10-Sep-2021 06:05:27 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[10-Sep-2021 06:05:28 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[10-Sep-2021 06:05:29 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
See also: All tests for this plugin