Does Baidu TextCensor work with WordPress 5.3.2 and PHP 7.2.16? A smoke test was performed on .
16 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: -2.59 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.022 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 5.3.2 |
---|---|
PHP version | 7.2.16 |
MySQL version | 8.0.15 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 40+ |
WordPress.org page | https://wordpress.org/plugins/baidu-textcensor/ |
Badges |
|
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=baidu-textcensor%2Fwp-baidu-textcensor.php&plugin_status=all&paged=1&s&_wpnonce=9f2af0bf64 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.324 s |
Memory usage | 3.57 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/options-general.php?page=Baidu_Text_Censor |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.143 s |
Memory usage | 3.47 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.207 s |
Memory usage | 3.29 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.249 s | 0.195 s | -0.054 s | 3.61 MiB | 3.62 MiB | + 6.19 KiB |
/wp-admin/edit.php | 0.185 s | 0.198 s | +0.013 s | 3.64 MiB | 3.65 MiB | + 6.19 KiB |
/wp-admin/post-new.php | 1.090 s | 1.651 s | +0.561 s | 5.36 MiB | 5.37 MiB | + 12.95 KiB |
/wp-admin/upload.php | 0.436 s | 0.357 s | -0.079 s | 3.48 MiB | 3.48 MiB | + 5.66 KiB |
/wp-admin/options-writing.php | 0.143 s | 0.150 s | +0.007 s | 3.56 MiB | 3.47 MiB | - 87.78 KiB |
/wp-admin/media-new.php | 0.192 s | 0.183 s | -0.009 s | 3.46 MiB | 3.46 MiB | + 5.83 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.159 s | 0.171 s | +0.012 s | 3.56 MiB | 3.57 MiB | + 6.73 KiB |
/wp-admin/post-new.php?post_type=page | 0.927 s | 0.887 s | -0.040 s | 5.35 MiB | 5.36 MiB | + 6.13 KiB |
/wp-admin/options-discussion.php | 0.326 s | 0.241 s | -0.085 s | 3.46 MiB | 3.47 MiB | + 6.14 KiB |
/wp-admin/edit-comments.php | 0.183 s | 0.195 s | +0.012 s | 3.57 MiB | 3.57 MiB | + 5.04 KiB |
/ | 0.288 s | 0.188 s | -0.100 s | 3.32 MiB | 3.31 MiB | - 1.52 KiB |
Average | 0.380 s | 0.401 s | +0.022 s | 3.85 MiB | 3.85 MiB | - 2.59 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[11-Jan-2020 00:39:12 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986
[11-Jan-2020 00:39:13 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986
[11-Jan-2020 00:39:13 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986
[11-Jan-2020 00:39:14 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986
[11-Jan-2020 00:39:14 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986
[11-Jan-2020 00:39:14 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986
[11-Jan-2020 00:39:16 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986
[11-Jan-2020 00:39:16 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986
[11-Jan-2020 00:39:16 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986
[11-Jan-2020 00:39:17 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986
[11-Jan-2020 00:39:17 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986
[11-Jan-2020 00:39:18 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986
[11-Jan-2020 00:39:18 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986
[11-Jan-2020 00:39:19 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986
[11-Jan-2020 00:39:19 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986
[11-Jan-2020 00:39:19 UTC] PHP Notice: add_submenu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_submenu_page()</code> should be an integer representing menu position. 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.3.0.) in /wp-includes/functions.php on line 4986