Report - Bot for Telegram on WooCommerce 1.0.4

Does "Bot for Telegram on WooCommerce" work with WordPress 5.6.2 and PHP 7.4.8? A smoke test was performed on 2021-02-28 02:13:09 UTC.

Summary

Errors

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

Performance

Memory usage: 42.81 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.6.2
PHP version	7.4.8
MySQL version	8.0.21
PHP memory limit	256M

Plugin Info

Last updated	18 days ago
Active installs	300+
WordPress.org page	https://wordpress.org/plugins/bot-for-telegram-on-woocommerce/
Badges	Get badge code

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=bot-for-telegram-on-woocommerce%2Fbot-for-telegram-on-woocommerce.php&plugin_status=all&paged=1&s&_wpnonce=a22893ee41
Aspect	after-activation
HTTP status	200
Load time	0.238 s
Memory usage	2.72 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.237 s
Memory usage	2.65 MiB
JS errors	None
Resource errors	None

Benchmark

URL	Load time			Memory usage
URL	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/index.php	0.254 s	0.252 s	-0.002 s	2.79 MiB	2.83 MiB	+ 41.23 KiB
/wp-admin/edit.php	0.178 s	0.192 s	+0.014 s	2.84 MiB	2.88 MiB	+ 41.23 KiB
/wp-admin/post-new.php	0.843 s	0.643 s	-0.200 s	4.94 MiB	5 MiB	+ 71.26 KiB
/wp-admin/upload.php	0.520 s	0.460 s	-0.060 s	2.67 MiB	2.71 MiB	+ 40.47 KiB
/wp-admin/options-writing.php	0.173 s	0.170 s	-0.003 s	2.68 MiB	2.69 MiB	+ 8.08 KiB
/wp-admin/media-new.php	0.312 s	0.168 s	-0.144 s	2.65 MiB	2.68 MiB	+ 40.27 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.195 s	0.205 s	+0.010 s	2.68 MiB	2.72 MiB	+ 41.18 KiB
/wp-admin/post-new.php?post_type=page	0.782 s	0.621 s	-0.161 s	4.92 MiB	4.99 MiB	+ 66.84 KiB
/wp-admin/options-discussion.php	0.293 s	0.218 s	-0.075 s	2.65 MiB	2.69 MiB	+ 40.59 KiB
/wp-admin/edit-comments.php	0.241 s	0.204 s	-0.037 s	2.75 MiB	2.79 MiB	+ 40.09 KiB
/	0.303 s	0.214 s	-0.089 s	2.61 MiB	2.65 MiB	+ 39.69 KiB
Average	0.372 s	0.304 s	-0.068 s	3.11 MiB	3.15 MiB	+ 42.81 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

Language		%	Lines of code	Comment lines	Files
	PHP	91.6%	1,941	22	13
	JavaScript	3.6%	76	26	2
	CSS	2.1%	44	0	1
	Sass	2.0%	43	0	1
	JSON	0.7%	14	0	1
	SVG	0.0%	1	0	1
Total			2,119	48	19

PHP Code Analysis | More results »

Lines of code	1,940
Total complexity	264
Median class complexity	16.5
Median method complexity	1.0
Most complex class	BFTOW_Telegram
Most complex function	BFTOW_Telegram::get_tg_data()

Classes	10
Methods	91
Functions	5

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

[28-Feb-2021 02:13:25 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>woo-telegram/v1/product</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://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5311
[28-Feb-2021 02:13:25 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>woo-telegram/v1/main</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://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5311
[28-Feb-2021 02:13:28 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>woo-telegram/v1/product</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://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5311
[28-Feb-2021 02:13:28 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>woo-telegram/v1/main</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://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5311