AppPresser 4.0.4
Does AppPresser work with WordPress 5.5.1 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: 308.79 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.5.1 |
|---|---|
| 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=946247802f |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.567 s |
| Memory usage | 2.94 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.194 s |
| Memory usage | 2.99 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.389 s |
| Memory usage | 3.02 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.311 s |
| Memory usage | 2.97 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.650 s |
| Memory usage | 3.06 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.257 s |
| Memory usage | 2.92 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.263 s |
| Memory usage | 2.82 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.457 s | 0.383 s | -0.074 s | 2.75 MiB | 3.04 MiB | + 294.39 KiB |
| /wp-admin/edit.php | 0.225 s | 0.283 s | +0.058 s | 2.8 MiB | 3.09 MiB | + 300.5 KiB |
| /wp-admin/post-new.php | 1.544 s | 2.013 s | +0.469 s | 4.54 MiB | 4.89 MiB | + 356.74 KiB |
| /wp-admin/upload.php | 0.696 s | 0.465 s | -0.231 s | 2.63 MiB | 2.92 MiB | + 298.39 KiB |
| /wp-admin/options-writing.php | 0.172 s | 0.203 s | +0.031 s | 2.64 MiB | 2.9 MiB | + 265.2 KiB |
| /wp-admin/media-new.php | 0.211 s | 0.201 s | -0.010 s | 2.6 MiB | 2.9 MiB | + 300.8 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.189 s | 0.223 s | +0.034 s | 2.64 MiB | 2.93 MiB | + 295.55 KiB |
| /wp-admin/post-new.php?post_type=page | 1.427 s | 1.391 s | -0.036 s | 4.53 MiB | 4.88 MiB | + 354.63 KiB |
| /wp-admin/options-discussion.php | 0.370 s | 0.272 s | -0.098 s | 2.61 MiB | 2.9 MiB | + 300.2 KiB |
| /wp-admin/edit-comments.php | 0.277 s | 0.234 s | -0.043 s | 2.65 MiB | 3 MiB | + 363.18 KiB |
| / | 0.401 s | 0.267 s | -0.134 s | 2.56 MiB | 2.82 MiB | + 267.11 KiB |
| Average | 0.543 s | 0.540 s | -0.003 s | 3 MiB | 3.3 MiB | + 308.79 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
[03-Sep-2020 05:18:47 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 5225
[03-Sep-2020 05:18:47 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 5225
[03-Sep-2020 05:18:47 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 5225
[03-Sep-2020 05:18:47 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 5225
[03-Sep-2020 05:18:47 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 5225
[03-Sep-2020 05:18:47 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 5225
[03-Sep-2020 05:18:47 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 5225
[03-Sep-2020 05:18:50 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 5225
[03-Sep-2020 05:18:50 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 5225
[03-Sep-2020 05:18:50 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 5225
[03-Sep-2020 05:18:50 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 5225
[03-Sep-2020 05:18:50 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 5225
[03-Sep-2020 05:18:50 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 5225
[03-Sep-2020 05:18:50 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 5225