AppPresser 4.0.6
Does AppPresser work with WordPress 5.6 and PHP 7.4.8? A smoke test was performed on .
Summary
Errors
| 14 | PHP notices |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Performance
Memory usage: 346.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 version | 5.6 |
|---|---|
| PHP version | 7.4.8 |
| MySQL version | 8.0.21 |
| PHP memory limit | 256M |
Plugin Info
| Last updated | |
|---|---|
| Active installs | 1,000+ |
| WordPress.org page | https://wordpress.org/plugins/apppresser/ |
| Badges |
|
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=85e823a78e |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.448 s |
| Memory usage | 3.05 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.178 s |
| Memory usage | 3.04 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.421 s |
| Memory usage | 3.13 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.303 s |
| Memory usage | 3.08 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.212 s |
| Memory usage | 3.12 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.422 s |
| Memory usage | 3.03 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.86 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.272 s | 0.339 s | +0.067 s | 2.79 MiB | 3.09 MiB | + 301.5 KiB |
| /wp-admin/edit.php | 0.179 s | 0.197 s | +0.018 s | 2.84 MiB | 3.14 MiB | + 307.61 KiB |
| /wp-admin/post-new.php | 0.903 s | 0.974 s | +0.071 s | 4.93 MiB | 5.38 MiB | + 459.2 KiB |
| /wp-admin/upload.php | 0.517 s | 0.482 s | -0.035 s | 2.67 MiB | 3.02 MiB | + 365.93 KiB |
| /wp-admin/options-writing.php | 0.230 s | 0.169 s | -0.061 s | 2.68 MiB | 3.01 MiB | + 331.75 KiB |
| /wp-admin/media-new.php | 0.211 s | 0.190 s | -0.021 s | 2.65 MiB | 3 MiB | + 366.1 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.182 s | 0.201 s | +0.019 s | 2.68 MiB | 3.04 MiB | + 365.22 KiB |
| /wp-admin/post-new.php?post_type=page | 1.104 s | 0.735 s | -0.369 s | 4.92 MiB | 5.36 MiB | + 445.18 KiB |
| /wp-admin/options-discussion.php | 0.408 s | 0.249 s | -0.159 s | 2.65 MiB | 3.01 MiB | + 366.75 KiB |
| /wp-admin/edit-comments.php | 0.240 s | 0.209 s | -0.031 s | 2.75 MiB | 3.04 MiB | + 302.35 KiB |
| / | 0.667 s | 0.253 s | -0.414 s | 2.67 MiB | 2.86 MiB | + 200.05 KiB |
| Average | 0.447 s | 0.363 s | -0.083 s | 3.11 MiB | 3.45 MiB | + 346.51 KiB |
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
[16-Dec-2020 17:14:23 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 5311
[16-Dec-2020 17:14:23 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 5311
[16-Dec-2020 17:14:23 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 5311
[16-Dec-2020 17:14:23 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 5311
[16-Dec-2020 17:14:23 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 5311
[16-Dec-2020 17:14:23 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 5311
[16-Dec-2020 17:14:23 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 5311
[16-Dec-2020 17:14:26 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 5311
[16-Dec-2020 17:14:26 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 5311
[16-Dec-2020 17:14:26 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 5311
[16-Dec-2020 17:14:26 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 5311
[16-Dec-2020 17:14:26 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 5311
[16-Dec-2020 17:14:26 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 5311
[16-Dec-2020 17:14:26 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 5311