Does Brizy work with WordPress 5.0.1 and PHP 7.0.16? A smoke test was performed on .
6 | WordPress deprecation warnings |
3 | JavaScript exceptions |
All test pages loaded successfully | |
No resource errors |
Memory usage: 414.63 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 | 80,000+ |
WordPress.org page | https://wordpress.org/plugins/brizy/ |
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=brizy%2Fbrizy.php&plugin_status=all&paged=1&s&_wpnonce=0b8206bb31 |
Aspect | after-activation |
HTTP status | 200 OK |
Load time | 0.155 s |
Memory usage | 3.67 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=brizy-settings |
---|---|
Aspect | menu-item |
HTTP status | 200 OK |
Load time | 0.040 s |
Memory usage | 3.65 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=brizy-settings&tab=roles |
---|---|
Aspect | menu-item-tab |
HTTP status | 200 OK |
Load time | 0.119 s |
Memory usage | 3.65 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit.php?post_type=brizy_template |
---|---|
Aspect | menu-item |
HTTP status | 200 OK |
Load time | 0.135 s |
Memory usage | 3.58 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 OK |
Load time | 0.124 s |
Memory usage | 3.25 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/index.php |
---|---|
Aspect | new-meta-boxes |
HTTP status | 200 OK |
Load time | 0.179 s |
Memory usage | 3.65 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/post-new.php |
---|---|
Aspect | new-meta-boxes |
HTTP status | 200 OK |
Load time | 0.353 s |
Memory usage | 5.33 MiB |
JS errors |
|
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.155 s | 0.055 s | -0.100 s | 3.22 MiB | 3.64 MiB | + 426.81 KiB |
/wp-admin/edit.php | 0.141 s | 0.150 s | +0.009 s | 3.25 MiB | 3.75 MiB | + 509.67 KiB |
/wp-admin/post-new.php | 0.634 s | 0.503 s | -0.131 s | 4.92 MiB | 5.33 MiB | + 420.47 KiB |
/wp-admin/upload.php | 0.037 s | 0.051 s | +0.014 s | 3.15 MiB | 3.53 MiB | + 390.11 KiB |
/wp-admin/options-writing.php | 0.080 s | 0.098 s | +0.018 s | 3.14 MiB | 3.52 MiB | + 390.42 KiB |
/wp-admin/media-new.php | 0.047 s | 0.126 s | +0.079 s | 3.07 MiB | 3.51 MiB | + 453.98 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.123 s | 0.144 s | +0.021 s | 3.17 MiB | 3.55 MiB | + 391.34 KiB |
/wp-admin/post-new.php?post_type=page | 0.810 s | 0.337 s | -0.473 s | 4.9 MiB | 5.31 MiB | + 411.92 KiB |
/wp-admin/options-discussion.php | 0.106 s | 0.146 s | +0.040 s | 3.07 MiB | 3.52 MiB | + 454.42 KiB |
/wp-admin/edit-comments.php | 0.134 s | 0.067 s | -0.067 s | 3.18 MiB | 3.56 MiB | + 390.15 KiB |
/ | 0.098 s | 0.202 s | +0.104 s | 2.93 MiB | 3.24 MiB | + 321.63 KiB |
Average | 0.215 s | 0.171 s | -0.044 s | 3.46 MiB | 3.86 MiB | + 414.63 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
2ID | Name |
---|---|
brizy-project | Posts |
brizy_template | Templates |
{
"dashboard": {
"brizy_dashboard": {
"title": "Brizy Overview",
"context": "normal"
}
},
"post": {
"pageparentdiv": {
"title": "Post Attributes",
"context": "side"
}
},
"brizy_template": {
"template-rules": {
"title": "Display Conditions",
"context": "normal"
}
}
}
[13-Dec-2018 12:33:46 UTC] PHP Notice: edit_form_after_title 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 12:33:46 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 12:33:48 UTC] PHP Notice: edit_form_after_title 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 12:33:48 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 12:33:51 UTC] PHP Notice: edit_form_after_title 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 12:33:51 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