Visual Products Configurator - Free 3.3.8

Does "Visual Products Configurator - Free" work with WordPress 5.8.1 and PHP 7.4.8? A smoke test was performed on .

Summary

Errors
2PHP fatal errors
16PHP notices
No JavaScript exceptions
1Page failed to load
  • 1 403 Forbidden
No resource errors
Performance

Memory usage: 117.45 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 version5.8.1
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 300+
WordPress.org page https://wordpress.org/plugins/visual-products-configurator-for-woocommerce/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 4

WordPress › Error

Page screenshot: WordPress › Error
URL /wp-admin/edit.php?post_type=vpc-config&page=vpc-getting-started
Requested URL /wp-admin/plugins.php?action=activate&plugin=visual-products-configurator-for-woocommerce%2Fvpc.php&plugin_status=all&paged=1&s&_wpnonce=5aea9f43e8
Aspect after-activation
HTTP status 403
Load time 0.329 s
Memory usage N/A
JS errors None
Resource errors None

Product Builder

Page screenshot: Product Builder
URL /wp-admin/edit.php?post_type=vpc-config
Aspect menu-item
HTTP status 200
Load time 0.187 s
Memory usage 3.18 MiB
JS errors None
Resource errors None

Product Builder → New configuration

Page screenshot: Product Builder → New configuration
URL /wp-admin/post-new.php?post_type=vpc-config
Aspect menu-item
HTTP status 200
Load time 0.372 s
Memory usage 3.33 MiB
JS errors None
Resource errors None

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.252 s
Memory usage N/A
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.330 s0.297 s-0.033 s3.08 MiB3.19 MiB+ 113.62 KiB
/wp-admin/edit.php0.175 s0.191 s+0.016 s3.11 MiB3.29 MiB+ 179.51 KiB
/wp-admin/post-new.php1.072 s0.739 s-0.333 s5.27 MiB5.37 MiB+ 108.3 KiB
/wp-admin/upload.php0.560 s0.441 s-0.119 s3.03 MiB3.14 MiB+ 112.77 KiB
/wp-admin/options-writing.php0.158 s0.167 s+0.009 s3.02 MiB3.12 MiB+ 97.69 KiB
/wp-admin/media-new.php0.274 s0.347 s+0.073 s3.01 MiB3.12 MiB+ 114.2 KiB
/wp-admin/edit-tags.php?taxonomy=category0.202 s0.247 s+0.045 s3.04 MiB3.15 MiB+ 113.54 KiB
/wp-admin/post-new.php?post_type=page0.633 s0.654 s+0.021 s5.26 MiB5.36 MiB+ 108.3 KiB
/wp-admin/options-discussion.php0.223 s0.350 s+0.127 s3 MiB3.12 MiB+ 114.2 KiB
/wp-admin/edit-comments.php0.211 s0.384 s+0.173 s3.04 MiB3.15 MiB+ 112.41 KiB
/0.305 s0.165 s-0.140 s2.96 MiB
Average 0.377 s0.362 s-0.015 s3.44 MiB3.6 MiB+ 117.45 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.

CSS
PHP
JavaScript
Language % Lines of code Comment lines Files
CSS42.2%4,0483347
PHP31.4%3,01083515
JavaScript20.3%1,9483528
SVG6.1%58212
Total 9,588 1,522 32

PHP Code Analysis | More results »

Lines of code 3,074
Total complexity 531
Median class complexity 27.0
Median method complexity 2.0
Most complex class VPC_Public
Most complex function Orion_Library::o_admin_fields()
Classes 11
Methods 108
Functions 22

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.

Custom Post Types 1

ID Name
vpc-configConfiguration

Meta Boxes

{
    "vpc-config": {
        "vpc-config-preview-box": {
            "title": "Preview",
            "context": "advanced"
        },
        "vpc-config-settings-box": {
            "title": "Configuration settings",
            "context": "advanced"
        }
    }
}

PHP Error Log 36 lines

[12-Sep-2021 09:50:50 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
[12-Sep-2021 09:50:50 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
[12-Sep-2021 09:50:50 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
[12-Sep-2021 09:50:51 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
[12-Sep-2021 09:50:52 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function wc_get_product() in /wp-content/plugins/visual-products-configurator-for-woocommerce/includes/functions.php:268
Stack trace:
#0 /wp-content/plugins/visual-products-configurator-for-woocommerce/public/class-vpc-public.php(690): vpc_product_is_configurable()
#1 /wp-includes/class-wp-hook.php(305): VPC_Public->add_class_to_body()
#2 /wp-includes/plugin.php(189): WP_Hook->apply_filters()
#3 /wp-includes/post-template.php(836): apply_filters()
#4 /wp-includes/post-template.php(595): get_body_class()
#5 /wp-content/themes/twentyseventeen/header.php(25): body_class()
#6 /wp-includes/template.php(770): require_once('/opt/bitnami/ap...')
#7 /wp-includes/template.php(716): loa in /wp-content/plugins/visual-products-configurator-for-woocommerce/includes/functions.php on line 268
[12-Sep-2021 09:50:52 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
[12-Sep-2021 09:50:52 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
[12-Sep-2021 09:50:53 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
[12-Sep-2021 09:50:54 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
[12-Sep-2021 09:50:55 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
[12-Sep-2021 09:50:55 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
[12-Sep-2021 09:50:55 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
[12-Sep-2021 09:50:56 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
[12-Sep-2021 09:50:57 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
[12-Sep-2021 09:50:57 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
[12-Sep-2021 09:50:58 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function wc_get_product() in /wp-content/plugins/visual-products-configurator-for-woocommerce/includes/functions.php:268
Stack trace:
#0 /wp-content/plugins/visual-products-configurator-for-woocommerce/public/class-vpc-public.php(690): vpc_product_is_configurable()
#1 /wp-includes/class-wp-hook.php(305): VPC_Public->add_class_to_body()
#2 /wp-includes/plugin.php(189): WP_Hook->apply_filters()
#3 /wp-includes/post-template.php(836): apply_filters()
#4 /wp-includes/post-template.php(595): get_body_class()
#5 /wp-content/themes/twentyseventeen/header.php(25): body_class()
#6 /wp-includes/template.php(770): require_once('/opt/bitnami/ap...')
#7 /wp-includes/template.php(716): loa in /wp-content/plugins/visual-products-configurator-for-woocommerce/includes/functions.php on line 268
[12-Sep-2021 09:50:58 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
[12-Sep-2021 09:50:59 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