InPost for WooCommerce 1.3.2
Does InPost for WooCommerce work with WordPress 5.0.1 and PHP 7.0.16? A smoke test was performed on .
Summary
Errors
| 2 | WordPress deprecation warnings |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Performance
Memory usage: 17.05 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.0.1 |
|---|---|
| PHP version | 7.0.16 |
| MySQL version | 5.7.17 |
| PHP memory limit | 256M |
Plugin Info
| Last updated | |
|---|---|
| Active installs | 3,000+ |
| WordPress.org page | https://wordpress.org/plugins/woo-inpost/ |
| Badges |
|
Pages 2
Plugins ‹ Test site — WordPress
| URL | /wp-admin/plugins.php?activate=true&plugin_status=all&paged=1&s= |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=woo-inpost%2Fwoo-inpost.php&plugin_status=all&paged=1&s&_wpnonce=e40b2111af |
| Aspect | after-activation |
| HTTP status | 200 OK |
| Load time | 0.150 s |
| Memory usage | 3.18 MiB |
| JS errors | None |
| Resource errors | None |
Test site – Just another WordPress site
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 OK |
| Load time | 0.116 s |
| Memory usage | 2.93 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.164 s | 0.128 s | -0.036 s | 3.22 MiB | 3.23 MiB | + 4.59 KiB |
| /wp-admin/edit.php | 0.136 s | 0.120 s | -0.016 s | 3.25 MiB | 3.25 MiB | + 4.56 KiB |
| /wp-admin/post-new.php | 0.544 s | 0.285 s | -0.259 s | 4.92 MiB | 4.93 MiB | + 11.73 KiB |
| /wp-admin/upload.php | 0.035 s | 0.041 s | +0.006 s | 3.15 MiB | 3.16 MiB | + 7.31 KiB |
| /wp-admin/options-writing.php | 0.084 s | 0.041 s | -0.043 s | 3.14 MiB | 3.15 MiB | + 4.48 KiB |
| /wp-admin/media-new.php | 0.048 s | 0.106 s | +0.058 s | 3.07 MiB | 3.14 MiB | + 68.48 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.117 s | 0.112 s | -0.005 s | 3.17 MiB | 3.18 MiB | + 4.48 KiB |
| /wp-admin/post-new.php?post_type=page | 0.477 s | 0.509 s | +0.032 s | 4.9 MiB | 4.91 MiB | + 4.48 KiB |
| /wp-admin/options-discussion.php | 0.098 s | 0.112 s | +0.014 s | 3.07 MiB | 3.14 MiB | + 68.48 KiB |
| /wp-admin/edit-comments.php | 0.086 s | 0.079 s | -0.007 s | 3.18 MiB | 3.18 MiB | + 4.48 KiB |
| / | 0.087 s | 0.090 s | +0.003 s | 2.93 MiB | 2.93 MiB | + 4.48 KiB |
| Average | 0.171 s | 0.148 s | -0.023 s | 3.46 MiB | 3.47 MiB | + 17.05 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.
No new entries found.
PHP Error Log 2 lines
[16-Dec-2018 23:47:16 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
[16-Dec-2018 23:47:18 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
See also: All tests for this plugin