Report - TrustMate.io integration for WooCommerce 1.11.5

Does "TrustMate.io integration for WooCommerce" work with WordPress 6.1.1 and PHP 8.1.12? A smoke test was performed on 2023-02-03 14:38:42 UTC.

Summary

Errors

4	PHP fatal errors
24	PHP notices
	No JavaScript exceptions
	All test pages loaded successfully
	No resource errors

Performance

Memory usage: 31.6 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	6.1.1
PHP version	8.1.12
MySQL version	10.6.10
PHP memory limit	512M

Plugin Info

Last updated	2023-11-22T14:10:00+00:00
Active installs	3,000+
WordPress.org page	https://wordpress.org/plugins/trustmate-io-integration-for-woocommerce/
Badges	Get badge code

Pages 8

Plugins ‹ Test site — WordPress

URL	/wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL	/wp-admin/plugins.php?action=activate&plugin=trustmate-io-integration-for-woocommerce%2Ftrustmate-plugin.php&plugin_status=all&paged=1&s&_wpnonce=2d9775d415
Aspect	after-activation
HTTP status	200
Load time	0.479 s
Memory usage	3.03 MiB
JS errors	None
Resource errors	None

Settings → Plugin Menu

URL	/wp-admin/options-general.php?page=trustmate
Aspect	menu-item
HTTP status	200
Load time	0.286 s
Memory usage	N/A
JS errors	None
Resource errors	None

Settings → Plugin Menu → Settings

URL	/wp-admin/options-general.php?page=trustmate&action=setup_account
Aspect	menu-item-tab
HTTP status	200
Load time	0.249 s
Memory usage	3.04 MiB
JS errors	None
Resource errors	None

Settings → Plugin Menu → Widgets

URL	/wp-admin/options-general.php?page=trustmate&action=widgets
Aspect	menu-item-tab
HTTP status	200
Load time	0.476 s
Memory usage	3 MiB
JS errors	None
Resource errors	None

TrustMate.io

URL	/wp-admin/admin.php?page=trustmate
Aspect	menu-item
HTTP status	200
Load time	0.136 s
Memory usage	N/A
JS errors	None
Resource errors	None

TrustMate.io → Settings

URL	/wp-admin/admin.php?page=trustmate&action=setup_account
Aspect	menu-item-tab
HTTP status	200
Load time	0.156 s
Memory usage	3 MiB
JS errors	None
Resource errors	None

TrustMate.io → Widgets

URL	/wp-admin/admin.php?page=trustmate&action=widgets
Aspect	menu-item-tab
HTTP status	200
Load time	0.225 s
Memory usage	3 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.206 s
Memory usage	N/A
JS errors	None
Resource errors	None

Benchmark

URL	Load time			Memory usage
URL	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/index.php	0.303 s	0.290 s	-0.013 s	3.05 MiB	3.09 MiB	+ 41.77 KiB
/wp-admin/edit.php	0.198 s	0.198 s	+0.000 s	3.07 MiB	3.12 MiB	+ 41.77 KiB
/wp-admin/post-new.php	0.820 s	0.948 s	+0.128 s	4.97 MiB	5.01 MiB	+ 40.15 KiB
/wp-admin/upload.php	0.572 s	0.478 s	-0.094 s	2.99 MiB	3.01 MiB	+ 23.41 KiB
/wp-admin/options-writing.php	0.168 s	0.150 s	-0.018 s	2.99 MiB	3 MiB	+ 10.07 KiB
/wp-admin/media-new.php	0.358 s	0.278 s	-0.080 s	2.97 MiB	3 MiB	+ 35.61 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.174 s	0.205 s	+0.031 s	2.98 MiB	3.02 MiB	+ 40.78 KiB
/wp-admin/post-new.php?post_type=page	0.677 s	0.650 s	-0.027 s	4.96 MiB	4.99 MiB	+ 34.8 KiB
/wp-admin/options-discussion.php	0.230 s	0.207 s	-0.023 s	2.98 MiB	3 MiB	+ 24.23 KiB
/wp-admin/edit-comments.php	0.194 s	0.193 s	-0.001 s	3 MiB	3.02 MiB	+ 23.45 KiB
/	0.284 s	0.182 s	-0.102 s	2.94 MiB
Average	0.362 s	0.344 s	-0.018 s	3.35 MiB	3.43 MiB	+ 31.6 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.

PO File

PHP

Language		%	Lines of code	Comment lines	Files
	PO File	77.2%	6,909	244	21
	PHP	19.5%	1,745	35	21
	CSS	2.9%	263	0	4
	SVG	0.3%	31	0	1
Total			8,948	279	47

PHP Code Analysis | More results »

Lines of code	1,743
Total complexity	196
Median class complexity	0.0
Median method complexity	0.0
Most complex class	—
Most complex function	trustmate_create_invitation()

Classes	0
Methods	0
Functions	59

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 67 lines

[03-Feb-2023 14:38:59 UTC] PHP Notice:  Function wp_register_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:38:59 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:38:59 UTC] PHP Notice:  Function wp_register_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:38:59 UTC] PHP Notice:  Function wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:38:59 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function woocommerce_form_field() in /wp-content/plugins/trustmate-io-integration-for-woocommerce/install_form.php:59
Stack trace:
#0 /wp-content/plugins/trustmate-io-integration-for-woocommerce/trustmate-plugin.php(241): trustmate_render_setup_choice()
#1 /wp-includes/class-wp-hook.php(308): trustmate_view_dispatcher()
#2 /wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#3 /wp-includes/plugin.php(517): WP_Hook->do_action()
#4 /wp-admin/admin.php(259): do_action()
#5 /wp-admin/options-general.php(10): require_once('...')
#6 {main}
  thrown in /wp-content/plugins/trustmate-io-integration-for-woocommerce/install_form.php on line 59
[03-Feb-2023 14:39:00 UTC] PHP Notice:  Function wp_register_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:00 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:00 UTC] PHP Notice:  Function wp_register_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:00 UTC] PHP Notice:  Function wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:01 UTC] PHP Notice:  Function wp_register_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:01 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:01 UTC] PHP Notice:  Function wp_register_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:01 UTC] PHP Notice:  Function wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:03 UTC] PHP Notice:  Function wp_register_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:03 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:03 UTC] PHP Notice:  Function wp_register_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:03 UTC] PHP Notice:  Function wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:03 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function woocommerce_form_field() in /wp-content/plugins/trustmate-io-integration-for-woocommerce/install_form.php:59
Stack trace:
#0 /wp-content/plugins/trustmate-io-integration-for-woocommerce/trustmate-plugin.php(241): trustmate_render_setup_choice()
#1 /wp-includes/class-wp-hook.php(308): trustmate_view_dispatcher()
#2 /wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#3 /wp-includes/plugin.php(517): WP_Hook->do_action()
#4 /wp-admin/admin.php(259): do_action()
#5 {main}
  thrown in /wp-content/plugins/trustmate-io-integration-for-woocommerce/install_form.php on line 59
[03-Feb-2023 14:39:04 UTC] PHP Notice:  Function wp_register_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:04 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:04 UTC] PHP Notice:  Function wp_register_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:04 UTC] PHP Notice:  Function wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:05 UTC] PHP Notice:  Function wp_register_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:05 UTC] PHP Notice:  Function wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:05 UTC] PHP Notice:  Function wp_register_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:05 UTC] PHP Notice:  Function wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>5.2.3_bootstrap</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5835
[03-Feb-2023 14:39:07 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function is_product() in /wp-content/plugins/trustmate-io-integration-for-woocommerce/embed_scripts.php:134
Stack trace:
#0 /wp-includes/class-wp-hook.php(310): trustmate_render_widget_product_ferret()
#1 /wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-includes/general-template.php(82): do_action()
#4 /wp-content/themes/twentyseventeen/index.php(72): get_footer()
#5 /wp-includes/template-loader.php(106): include('...')
#6 /wp-blog-header.php(19): require_once('...')
#7 /index.php(17): require('...')
#8 {main}
  thrown in /wp-content/plugins/trustmate-io-integration-for-woocommerce/embed_scripts.php on line 134
[03-Feb-2023 14:39:15 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function is_product() in /wp-content/plugins/trustmate-io-integration-for-woocommerce/embed_scripts.php:134
Stack trace:
#0 /wp-includes/class-wp-hook.php(310): trustmate_render_widget_product_ferret()
#1 /wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-includes/general-template.php(82): do_action()
#4 /wp-content/themes/twentyseventeen/index.php(72): get_footer()
#5 /wp-includes/template-loader.php(106): include('...')
#6 /wp-blog-header.php(19): require_once('...')
#7 /index.php(17): require('...')
#8 {main}
  thrown in /wp-content/plugins/trustmate-io-integration-for-woocommerce/embed_scripts.php on line 134