Report - AppPresser 4.0.7 - PluginTests.com

Does AppPresser work with WordPress 5.7.2 and PHP 7.4.8? A smoke test was performed on 2021-05-14 11:11:18 UTC.

Summary

Errors

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

Performance

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

Plugin Info

Last updated	2025-03-12T09:20:00+00:00
Active installs	1,000+
WordPress.org page	https://wordpress.org/plugins/apppresser/
Badges	Get badge code

Pages 7

Plugins ‹ Test site — WordPress

URL	/wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL	/wp-admin/plugins.php?action=activate&plugin=apppresser%2Fapppresser.php&plugin_status=all&paged=1&s&_wpnonce=42a4dd3bfc
Aspect	after-activation
HTTP status	200
Load time	0.347 s
Memory usage	3.08 MiB
JS errors	None
Resource errors	None

Plugins → Install Plugins

URL	/wp-admin/plugins.php?page=tgmpa-install-plugins
Aspect	menu-item
HTTP status	200
Load time	0.165 s
Memory usage	3.07 MiB
JS errors	None
Resource errors	None

AppPresser

URL	/wp-admin/admin.php?page=apppresser_settings
Aspect	menu-item
HTTP status	200
Load time	0.411 s
Memory usage	3.17 MiB
JS errors	None
Resource errors	None

AppPresser → Log

URL	/wp-admin/admin.php?page=apppresser_settings&tab=tab-log
Aspect	menu-item-tab
HTTP status	200
Load time	0.290 s
Memory usage	3.13 MiB
JS errors	None
Resource errors	None

AppPresser → System Info

URL	/wp-admin/admin.php?page=apppresser_settings&tab=tab-systeminfo
Aspect	menu-item-tab
HTTP status	200
Load time	1.365 s
Memory usage	3.16 MiB
JS errors	None
Resource errors	None

AppPresser → Help / Support

URL	/wp-admin/admin.php?page=apppresser_sub_help_support
Aspect	menu-item
HTTP status	200
Load time	0.406 s
Memory usage	3.08 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.256 s
Memory usage	2.9 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.268 s	0.350 s	+0.082 s	2.82 MiB	3.12 MiB	+ 303.23 KiB
/wp-admin/edit.php	0.187 s	0.209 s	+0.022 s	2.86 MiB	3.17 MiB	+ 309.34 KiB
/wp-admin/post-new.php	0.922 s	0.898 s	-0.024 s	5.02 MiB	5.46 MiB	+ 447.76 KiB
/wp-admin/upload.php	0.474 s	0.490 s	+0.016 s	2.7 MiB	3.06 MiB	+ 371.29 KiB
/wp-admin/options-writing.php	0.267 s	0.179 s	-0.088 s	2.71 MiB	3.04 MiB	+ 337.48 KiB
/wp-admin/media-new.php	0.219 s	0.195 s	-0.024 s	2.67 MiB	3.04 MiB	+ 371.83 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.202 s	0.207 s	+0.005 s	2.77 MiB	3.07 MiB	+ 306.95 KiB
/wp-admin/post-new.php?post_type=page	1.156 s	0.653 s	-0.503 s	5.01 MiB	5.45 MiB	+ 449.74 KiB
/wp-admin/options-discussion.php	0.318 s	0.223 s	-0.095 s	2.68 MiB	3.04 MiB	+ 372.48 KiB
/wp-admin/edit-comments.php	0.232 s	0.221 s	-0.011 s	2.78 MiB	3.08 MiB	+ 308.08 KiB
/	0.269 s	0.256 s	-0.013 s	2.65 MiB	2.9 MiB	+ 253.45 KiB
Average	0.410 s	0.353 s	-0.058 s	3.15 MiB	3.49 MiB	+ 348.33 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

JavaScript

Language		%	Lines of code	Comment lines	Files
	PHP	47.9%	6,051	3,185	26
	JavaScript	42.4%	5,358	5,250	139
	CSS	5.8%	734	32	3
	PO File	3.3%	418	228	2
	HTML	0.3%	41	17	3
	SVG	0.3%	32	1	1
Total			12,634	8,713	174

PHP Code Analysis | More results »

Lines of code	6,027
Total complexity	1,505
Median class complexity	28.0
Median method complexity	2.0
Most complex class	TGM_Plugin_Activation
Most complex function	AppPresser_Admin_Settings::settings_page()

Classes	29
Methods	363
Functions	18

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` 1

appplog_filename

PHP Error Log 14 lines

[14-May-2021 11:11:39 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>appp/v1/login</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 5313
[14-May-2021 11:11:39 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>appp/v1/logout</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 5313
[14-May-2021 11:11:39 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>appp/v1/register</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 5313
[14-May-2021 11:11:39 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>appp/v1/verify</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 5313
[14-May-2021 11:11:39 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>appp/v1/verify-resend</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 5313
[14-May-2021 11:11:39 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>appp/v1/reset-password</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 5313
[14-May-2021 11:11:39 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>appp/v1/system-info</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 5313
[14-May-2021 11:11:42 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>appp/v1/login</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 5313
[14-May-2021 11:11:42 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>appp/v1/logout</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 5313
[14-May-2021 11:11:42 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>appp/v1/register</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 5313
[14-May-2021 11:11:42 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>appp/v1/verify</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 5313
[14-May-2021 11:11:42 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>appp/v1/verify-resend</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 5313
[14-May-2021 11:11:42 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>appp/v1/reset-password</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 5313
[14-May-2021 11:11:42 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>appp/v1/system-info</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 5313

AppPresser 4.0.7