WooCommerce Visma integration 2.5.0

Does WooCommerce Visma integration work with WordPress 6.7.2 and PHP 8.1.12? A smoke test was performed on .

Summary

Errors
14PHP fatal errors
16PHP notices
No JavaScript exceptions
1Page failed to load
  • 1 500 Internal Server Error
No resource errors
Performance

Memory usage: -33.51 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 version6.7.2
PHP version8.1.12
MySQL version10.6.10
PHP memory limit512M
Plugin Info
Last updated
Active installs 70+
WordPress.org page https://wordpress.org/plugins/woo-visma-integration/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 2

Plugins ‹ Test site — WordPress

Page screenshot: Plugins ‹ Test site — WordPress
URL /wp-admin/plugins.php?activate=true&plugin_status=all&paged=1&s=
Requested URL /wp-admin/plugins.php?action=activate&plugin=woo-visma-integration%2Fplugin.php&plugin_status=all&paged=1&s&_wpnonce=e8f4b37081
Aspect after-activation
HTTP status 500
Load time 0.432 s
Memory usage N/A
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.225 s
Memory usage 3.45 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/0.321 s0.167 s-0.154 s3.48 MiB3.45 MiB- 33.51 KiB
Average 0.321 s0.167 s-0.154 s3.48 MiB3.45 MiB- 33.51 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.

PHP
SVG
Language % Lines of code Comment lines Files
PHP52.5%5,0841,66644
SVG27.7%2,68502
JavaScript7.8%751473
PO File6.8%6574301
CSS3.8%372162
JSON1.4%14001
Total 9,689 2,159 53

PHP Code Analysis | More results »

Lines of code 4,947
Total complexity 931
Median class complexity 18.0
Median method complexity 2.0
Most complex class includes\api\WTV_Orders
Most complex function includes\views\WTV_Accounting_Settings_View::render_settings()
Classes 41
Methods 287
Functions 3

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.

No new entries found.

PHP Error Log 144 lines

[17-Feb-2025 06:40:44 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function includes\WC() in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php:153
Stack trace:
#0 /wp-includes/class-wp-hook.php(324): includes\WTV_Plugin::add_admin_scripts()
#1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-admin/admin-header.php(118): do_action()
#4 /wp-admin/plugins.php(637): require_once('...')
#5 {main}
  thrown in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php on line 153
[17-Feb-2025 06:40:45 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function includes\WC() in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php:153
Stack trace:
#0 /wp-includes/class-wp-hook.php(324): includes\WTV_Plugin::add_admin_scripts()
#1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-admin/admin-header.php(118): do_action()
#4 /wp-admin/index.php(137): require_once('...')
#5 {main}
  thrown in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php on line 153
[17-Feb-2025 06:40:46 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function includes\WC() in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php:153
Stack trace:
#0 /wp-includes/class-wp-hook.php(324): includes\WTV_Plugin::add_admin_scripts()
#1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-admin/admin-header.php(118): do_action()
#4 /wp-admin/index.php(137): require_once('...')
#5 {main}
  thrown in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php on line 153
[17-Feb-2025 06:40:46 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function includes\WC() in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php:153
Stack trace:
#0 /wp-includes/class-wp-hook.php(324): includes\WTV_Plugin::add_admin_scripts()
#1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-admin/admin-header.php(118): do_action()
#4 /wp-admin/edit.php(411): require_once('...')
#5 {main}
  thrown in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php on line 153
[17-Feb-2025 06:40:46 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. Instead namespace '<code>visma/</code>' for route '<code>/callback/</code>' seems to contain a slash. 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.4.2.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:46 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>visma/callback</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:46 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. Instead namespace '<code>visma/</code>' for route '<code>/pull_sync/</code>' seems to contain a slash. 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.4.2.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:46 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>visma/pull_sync</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:46 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. Instead namespace '<code>visma/</code>' for route '<code>/match_skus/</code>' seems to contain a slash. 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.4.2.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:46 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>visma/match_skus</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:46 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. Instead namespace '<code>visma/</code>' for route '<code>/compare_skus/</code>' seems to contain a slash. 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.4.2.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:46 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>visma/compare_skus</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:47 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function includes\views\wc_get_order() in /wp-content/plugins/woo-visma-integration/includes/views/class-wtv-visma-invoice-widget.php:76
Stack trace:
#0 /wp-includes/class-wp-hook.php(324): includes\views\WTV_Visma_Invoice_Widget::render_widget()
#1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-admin/includes/meta-boxes.php(1716): do_action()
#4 /wp-admin/edit-form-blocks.php(306): register_and_do_post_meta_boxes()
#5 /wp-admin/post-new.php(72): require('...')
#6 {main}
  thrown in /wp-content/plugins/woo-visma-integration/includes/views/class-wtv-visma-invoice-widget.php on line 76
[17-Feb-2025 06:40:47 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function includes\WC() in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php:153
Stack trace:
#0 /wp-includes/class-wp-hook.php(324): includes\WTV_Plugin::add_admin_scripts()
#1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-admin/admin-header.php(118): do_action()
#4 /wp-admin/upload.php(207): require_once('...')
#5 {main}
  thrown in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php on line 153
[17-Feb-2025 06:40:47 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function includes\WC() in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php:153
Stack trace:
#0 /wp-includes/class-wp-hook.php(324): includes\WTV_Plugin::add_admin_scripts()
#1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-admin/admin-header.php(118): do_action()
#4 /wp-admin/options-writing.php(59): require_once('...')
#5 {main}
  thrown in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php on line 153
[17-Feb-2025 06:40:47 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function includes\WC() in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php:153
Stack trace:
#0 /wp-includes/class-wp-hook.php(324): includes\WTV_Plugin::add_admin_scripts()
#1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-admin/admin-header.php(118): do_action()
#4 /wp-admin/media-new.php(65): require_once('...')
#5 {main}
  thrown in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php on line 153
[17-Feb-2025 06:40:47 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function includes\WC() in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php:153
Stack trace:
#0 /wp-includes/class-wp-hook.php(324): includes\WTV_Plugin::add_admin_scripts()
#1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-admin/admin-header.php(118): do_action()
#4 /wp-admin/edit-tags.php(322): require_once('...')
#5 {main}
  thrown in /wp-content/plugins/woo-visma-integration/includes/class-wtv-plugin.php on line 153
[17-Feb-2025 06:40:47 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. Instead namespace '<code>visma/</code>' for route '<code>/callback/</code>' seems to contain a slash. 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.4.2.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:47 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>visma/callback</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:47 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. Instead namespace '<code>visma/</code>' for route '<code>/pull_sync/</code>' seems to contain a slash. 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.4.2.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:47 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>visma/pull_sync</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:47 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. Instead namespace '<code>visma/</code>' for route '<code>/match_skus/</code>' seems to contain a slash. 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.4.2.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:47 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>visma/match_skus</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:47 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. Instead namespace '<code>visma/</code>' for route '<code>/compare_skus/</code>' seems to contain a slash. 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.4.2.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:47 UTC] PHP Notice:  Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>visma/compare_skus</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. 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.5.0.) in /wp-includes/functions.php on line 6114
[17-Feb-2025 06:40:47 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function includes\views\wc_get_order() in /wp-content/plugins/woo-visma-integration/includes/views/class-wtv-visma-invoice-widget.php:76
Stack trace:

(+44 more lines)
See also: All tests for this plugin