1. Home
  2. BigCommerce For WordPress
  3. 4.33.0

BigCommerce for WordPress 4.33.0

Does BigCommerce for WordPress work with WordPress 6.0.2 and PHP 7.4.8? A smoke test was performed on .

Summary

Errors
1PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 2.26 MiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: 0.065 seconds
The average page load time increased by this amount after activating the plugin.

Environment
WordPress version6.0.2
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 500+
WordPress.org page https://wordpress.org/plugins/bigcommerce/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 8

BigCommerce for WordPress ‹ Test site — WordPress

Page screenshot: BigCommerce for WordPress ‹ Test site — WordPress
URL /wp-admin/edit.php?page=bigcommerce_welcome&post_type=bigcommerce_product
Requested URL /wp-admin/plugins.php?action=activate&plugin=bigcommerce%2Fbigcommerce.php&plugin_status=all&paged=1&s&_wpnonce=a35fd69165
Aspect after-activation
HTTP status 200
Load time 2.817 s
Memory usage 5.99 MiB
JS errors None
Resource errors None

BigCommerce

Page screenshot: BigCommerce
URL /wp-admin/edit.php?post_type=bigcommerce_product
Aspect menu-item
HTTP status 200
Load time 0.309 s
Memory usage 6.01 MiB
JS errors None
Resource errors None

BigCommerce → Categories

Page screenshot: BigCommerce → Categories
URL /wp-admin/edit-tags.php?taxonomy=bigcommerce_category&post_type=bigcommerce_product
Aspect menu-item
HTTP status 200
Load time 0.245 s
Memory usage 5.9 MiB
JS errors None
Resource errors None

BigCommerce → Brands

Page screenshot: BigCommerce → Brands
URL /wp-admin/edit-tags.php?taxonomy=bigcommerce_brand&post_type=bigcommerce_product
Aspect menu-item
HTTP status 200
Load time 0.308 s
Memory usage 5.9 MiB
JS errors None
Resource errors None

BigCommerce → Welcome

Page screenshot: BigCommerce → Welcome
URL /wp-admin/edit.php?post_type=bigcommerce_product&page=bigcommerce_welcome
Aspect menu-item
HTTP status 200
Load time 0.569 s
Memory usage 5.82 MiB
JS errors None
Resource errors None

BigCommerce → Resources

Page screenshot: BigCommerce → Resources
URL /wp-admin/edit.php?post_type=bigcommerce_product&page=bigcommerce_resources
Aspect menu-item
HTTP status 200
Load time 0.848 s
Memory usage 6.19 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.612 s
Memory usage 5.88 MiB
JS errors None
Resource errors None

Widgets ‹ Test site — WordPress

Page screenshot: Widgets ‹ Test site — WordPress
URL /wp-admin/widgets.php
Aspect new-sidebar-widgets
HTTP status 200
Load time 1.628 s
Memory usage 7.98 MiB
JS errors
External errors: The following JavaScript errors were probably triggered by WordPress itself, or by compatibility issues in the test runner. They are not related to the plugin. 
[
    {
        "message": "TypeError: Cannot read properties of null (reading 'offsetHeight')\n    at t (/wp-includes/js/dist/widgets.min.js?ver=80e98954519d1dad7a91a2248dbc2cc9:7:10419)\n    at IntersectionObserver.n.threshold (/wp-includes/js/dist/widgets.min.js?ver=80e98954519d1dad7a91a2248dbc2cc9:7:10591)",
        "trace": null,
        "code": null
    }
]
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.347 s0.479 s+0.132 s3.72 MiB5.95 MiB+ 2.22 MiB
/wp-admin/edit.php0.217 s0.311 s+0.094 s3.76 MiB6 MiB+ 2.25 MiB
/wp-admin/post-new.php0.893 s1.202 s+0.309 s5.55 MiB8.02 MiB+ 2.47 MiB
/wp-admin/upload.php0.432 s0.414 s-0.018 s3.69 MiB5.9 MiB+ 2.22 MiB
/wp-admin/options-writing.php0.155 s0.225 s+0.070 s3.62 MiB5.82 MiB+ 2.2 MiB
/wp-admin/media-new.php0.441 s0.244 s-0.197 s3.66 MiB5.88 MiB+ 2.22 MiB
/wp-admin/edit-tags.php?taxonomy=category0.235 s0.261 s+0.026 s3.69 MiB5.91 MiB+ 2.22 MiB
/wp-admin/post-new.php?post_type=page0.743 s0.887 s+0.144 s5.54 MiB8 MiB+ 2.46 MiB
/wp-admin/options-discussion.php0.228 s0.662 s+0.434 s3.6 MiB5.81 MiB+ 2.22 MiB
/wp-admin/edit-comments.php0.249 s0.325 s+0.076 s3.7 MiB5.92 MiB+ 2.22 MiB
/0.752 s0.397 s-0.355 s3.6 MiB5.81 MiB+ 2.2 MiB
Average 0.427 s0.492 s+0.065 s4.01 MiB6.28 MiB+ 2.26 MiB

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.

PHP
CSS
JavaScript
Language % Lines of code Comment lines Files
PHP56.2%41,27111,993711
CSS28.0%20,5581,0738
JavaScript10.3%7,5942,251154
HTML2.8%2,071011
Markdown2.5%1,82405
SVG0.2%14246
JSON0.0%702
Total 73,467 15,321 897

PHP Code Analysis | More results »

Lines of code 37,585
Total complexity 5,748
Median class complexity 6.0
Median method complexity 1.0
Most complex class BigCommerce\Post_Types\Product\Product
Most complex function BigCommerce\Post_Types\Product\Query::filter_queries()
Classes 540
Methods 2,509
Functions 39

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.

Options wp_options 15

Custom Post Types 3

ID Name
bigcommerce_productProducts
bigcommerce_taskQueue Tasks
bigcommerce_sync_logSync Logs

Sidebar Widgets 2

ID Name
bigcommerce_product_categoriesProduct Categories
bigcommerce_mini_cartMini-Cart

Roles 1

ID Name
customerCustomer

PHP Error Log 1 lines

[02-Sep-2022 18:09:02 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 5831
See also: All tests for this plugin