Does Simple Custom Post Order work with WordPress 5.0.1 and PHP 7.0.16? A smoke test was performed on .
2 | WordPress deprecation warnings |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 38.96 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.
WordPress version | 5.0.1 |
---|---|
PHP version | 7.0.16 |
MySQL version | 5.7.17 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 300,000+ |
WordPress.org page | https://wordpress.org/plugins/simple-custom-post-order/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?activate=true&plugin_status=all&paged=1&s= |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=simple-custom-post-order%2Fsimple-custom-post-order.php&plugin_status=all&paged=1&s&_wpnonce=8607a2ee36 |
Aspect | after-activation |
HTTP status | 200 OK |
Load time | 0.208 s |
Memory usage | 3.2 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/options-general.php?page=scporder-settings |
---|---|
Aspect | menu-item |
HTTP status | 200 OK |
Load time | 0.087 s |
Memory usage | 3.28 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 OK |
Load time | 0.112 s |
Memory usage | 2.95 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.138 s | 0.120 s | -0.018 s | 3.22 MiB | 3.25 MiB | + 27.71 KiB |
/wp-admin/edit.php | 0.117 s | 0.141 s | +0.024 s | 3.25 MiB | 3.28 MiB | + 27.46 KiB |
/wp-admin/post-new.php | 0.504 s | 0.291 s | -0.213 s | 4.92 MiB | 4.95 MiB | + 34.51 KiB |
/wp-admin/upload.php | 0.039 s | 0.050 s | +0.011 s | 3.15 MiB | 3.18 MiB | + 28.62 KiB |
/wp-admin/options-writing.php | 0.082 s | 0.048 s | -0.034 s | 3.14 MiB | 3.17 MiB | + 26.55 KiB |
/wp-admin/media-new.php | 0.045 s | 0.118 s | +0.073 s | 3.07 MiB | 3.16 MiB | + 88.5 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.109 s | 0.106 s | -0.003 s | 3.17 MiB | 3.2 MiB | + 26.61 KiB |
/wp-admin/post-new.php?post_type=page | 0.417 s | 0.468 s | +0.051 s | 4.9 MiB | 4.93 MiB | + 26.52 KiB |
/wp-admin/options-discussion.php | 0.031 s | 0.104 s | +0.073 s | 3.07 MiB | 3.16 MiB | + 90.09 KiB |
/wp-admin/edit-comments.php | 0.081 s | 0.083 s | +0.002 s | 3.18 MiB | 3.2 MiB | + 25.78 KiB |
/ | 0.095 s | 0.069 s | -0.026 s | 2.93 MiB | 2.96 MiB | + 26.19 KiB |
Average | 0.151 s | 0.145 s | -0.005 s | 3.46 MiB | 3.49 MiB | + 38.96 KiB |
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.
wp_options
1[13-Dec-2018 09:47:52 UTC] PHP Notice: edit_form_advanced is <strong>deprecated</strong> since version 5.0.0! Use block_editor_meta_box_hidden_fields instead. This action is still supported in the classic editor, but is deprecated in the block editor. in /wp-includes/functions.php on line 4147
[13-Dec-2018 09:47:54 UTC] PHP Notice: edit_form_advanced is <strong>deprecated</strong> since version 5.0.0! Use block_editor_meta_box_hidden_fields instead. This action is still supported in the classic editor, but is deprecated in the block editor. in /wp-includes/functions.php on line 4147