Report - Bot for Telegram on WooCommerce 1.0.2

Does "Bot for Telegram on WooCommerce" work with WordPress 5.6.1 and PHP 7.4.8? A smoke test was performed on 2021-02-11 00:47:20 UTC.

Summary

Errors

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

Performance

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

Plugin Info

Last updated	2025-04-21T18:16:00+00:00
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=757a9740d4
Aspect	after-activation
HTTP status	200
Load time	0.249 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.254 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.282 s	0.290 s	+0.008 s	2.79 MiB	2.83 MiB	+ 39.43 KiB
/wp-admin/edit.php	0.189 s	0.199 s	+0.010 s	2.84 MiB	2.87 MiB	+ 39.12 KiB
/wp-admin/post-new.php	0.899 s	0.702 s	-0.197 s	4.94 MiB	5 MiB	+ 69.45 KiB
/wp-admin/upload.php	0.544 s	0.508 s	-0.036 s	2.67 MiB	2.71 MiB	+ 38.35 KiB
/wp-admin/options-writing.php	0.160 s	0.190 s	+0.030 s	2.68 MiB	2.69 MiB	+ 5.96 KiB
/wp-admin/media-new.php	0.231 s	0.189 s	-0.042 s	2.65 MiB	2.68 MiB	+ 38.16 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.209 s	0.195 s	-0.014 s	2.68 MiB	2.72 MiB	+ 39.06 KiB
/wp-admin/post-new.php?post_type=page	1.249 s	0.670 s	-0.579 s	4.92 MiB	4.99 MiB	+ 65.04 KiB
/wp-admin/options-discussion.php	0.310 s	0.225 s	-0.085 s	2.65 MiB	2.69 MiB	+ 38.47 KiB
/wp-admin/edit-comments.php	0.232 s	0.213 s	-0.019 s	2.75 MiB	2.79 MiB	+ 37.97 KiB
/	0.262 s	0.209 s	-0.053 s	2.61 MiB	2.65 MiB	+ 37.57 KiB
Average	0.415 s	0.326 s	-0.089 s	3.11 MiB	3.15 MiB	+ 40.78 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	89.4%	1,500	16	12
	JavaScript	4.5%	76	26	2
	CSS	2.6%	44	0	1
	Sass	2.6%	43	0	1
	JSON	0.8%	14	0	1
	SVG	0.1%	1	0	1
Total			1,678	42	18

PHP Code Analysis | More results »

Lines of code	1,500
Total complexity	185
Median class complexity	13.0
Median method complexity	1.0
Most complex class	BFTOW_Telegram
Most complex function	BFTOW_Telegram::get_tg_data()

Classes	9
Methods	79
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

[11-Feb-2021 00:47:37 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
[11-Feb-2021 00:47:37 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
[11-Feb-2021 00:47:40 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
[11-Feb-2021 00:47:40 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