AppPresser 4.0.3
Does AppPresser work with WordPress 5.5 and PHP 7.2.16? 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: 347.06 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.039 seconds
The average page load time increased by this amount after activating the plugin.
Environment
| WordPress version | 5.5 |
|---|---|
| PHP version | 7.2.16 |
| MySQL version | 8.0.15 |
| 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=422d8f3f10 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.406 s |
| Memory usage | 4.28 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.182 s |
| Memory usage | 4.28 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 | 4.36 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.302 s |
| Memory usage | 4.25 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 | 4.34 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.267 s |
| Memory usage | 4.2 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.270 s |
| Memory usage | 3.91 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.442 s | 0.396 s | -0.046 s | 3.96 MiB | 4.34 MiB | + 383.23 KiB |
| /wp-admin/edit.php | 0.222 s | 0.261 s | +0.039 s | 3.99 MiB | 4.37 MiB | + 384.46 KiB |
| /wp-admin/post-new.php | 1.553 s | 1.870 s | +0.317 s | 5.81 MiB | 6.18 MiB | + 378.82 KiB |
| /wp-admin/upload.php | 0.723 s | 0.486 s | -0.237 s | 3.83 MiB | 4.2 MiB | + 381.55 KiB |
| /wp-admin/options-writing.php | 0.169 s | 0.198 s | +0.029 s | 3.9 MiB | 4.19 MiB | + 287.73 KiB |
| /wp-admin/media-new.php | 0.201 s | 0.205 s | +0.004 s | 3.8 MiB | 4.18 MiB | + 384.54 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.187 s | 0.216 s | +0.029 s | 3.91 MiB | 4.22 MiB | + 315.55 KiB |
| /wp-admin/post-new.php?post_type=page | 1.352 s | 1.546 s | +0.194 s | 5.8 MiB | 6.17 MiB | + 374.1 KiB |
| /wp-admin/options-discussion.php | 0.265 s | 0.306 s | +0.041 s | 3.81 MiB | 4.18 MiB | + 383.95 KiB |
| /wp-admin/edit-comments.php | 0.214 s | 0.266 s | +0.052 s | 3.91 MiB | 4.23 MiB | + 318.94 KiB |
| / | 0.300 s | 0.305 s | +0.005 s | 3.69 MiB | 3.91 MiB | + 224.78 KiB |
| Average | 0.512 s | 0.550 s | +0.039 s | 4.22 MiB | 4.56 MiB | + 347.06 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
[13-Aug-2020 02:37:29 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
[13-Aug-2020 02:37:29 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
[13-Aug-2020 02:37:29 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
[13-Aug-2020 02:37:29 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
[13-Aug-2020 02:37:29 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
[13-Aug-2020 02:37:29 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
[13-Aug-2020 02:37:29 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
[13-Aug-2020 02:37:32 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
[13-Aug-2020 02:37:32 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
[13-Aug-2020 02:37:32 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
[13-Aug-2020 02:37:32 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
[13-Aug-2020 02:37:32 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
[13-Aug-2020 02:37:32 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
[13-Aug-2020 02:37:32 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