Does IgnitionDeck work with WordPress 5.8.1 and PHP 7.4.8? A smoke test was performed on .
4 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 126.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.8.1 |
---|---|
PHP version | 7.4.8 |
MySQL version | 8.0.21 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 300+ |
WordPress.org page | https://wordpress.org/plugins/ignitiondeck/ |
Badges |
Get badge code |
URL | /wp-admin/admin.php?page=idf |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=ignitiondeck%2Fidf.php&plugin_status=all&paged=1&s&_wpnonce=9eea499584 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 3.173 s |
Memory usage | 3.26 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/plugins.php?page=idf-plugins |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.168 s |
Memory usage | 3.2 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=idf |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.933 s |
Memory usage | 3.15 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=idf-themes |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 1.384 s |
Memory usage | 3.21 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.251 s |
Memory usage | 3.04 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.310 s | 0.286 s | -0.024 s | 3.08 MiB | 3.25 MiB | + 175.21 KiB |
/wp-admin/edit.php | 0.170 s | 0.204 s | +0.034 s | 3.11 MiB | 3.29 MiB | + 178.68 KiB |
/wp-admin/post-new.php | 0.762 s | 0.922 s | +0.160 s | 5.27 MiB | 5.44 MiB | + 172.82 KiB |
/wp-admin/upload.php | 0.388 s | 0.498 s | +0.110 s | 3.03 MiB | 3.13 MiB | + 102.99 KiB |
/wp-admin/options-writing.php | 0.245 s | 0.171 s | -0.074 s | 3.02 MiB | 3.11 MiB | + 89.18 KiB |
/wp-admin/media-new.php | 0.344 s | 0.206 s | -0.138 s | 3.01 MiB | 3.11 MiB | + 103.16 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.187 s | 0.205 s | +0.018 s | 3.04 MiB | 3.14 MiB | + 104.2 KiB |
/wp-admin/post-new.php?post_type=page | 0.656 s | 0.712 s | +0.056 s | 5.26 MiB | 5.36 MiB | + 103.8 KiB |
/wp-admin/options-discussion.php | 0.248 s | 0.249 s | +0.001 s | 3 MiB | 3.11 MiB | + 105.7 KiB |
/wp-admin/edit-comments.php | 0.210 s | 0.226 s | +0.016 s | 3.04 MiB | 3.17 MiB | + 131.7 KiB |
/ | 0.386 s | 0.242 s | -0.144 s | 2.91 MiB | 3.04 MiB | + 129.12 KiB |
Average | 0.355 s | 0.356 s | +0.001 s | 3.43 MiB | 3.56 MiB | + 126.96 KiB |
Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.
Language | % | Lines of code | Comment lines | Files | |
---|---|---|---|---|---|
PHP | 39.7% | 5,077 | 1,790 | 52 | |
JSON | 24.9% | 3,188 | 0 | 4 | |
CSS | 24.6% | 3,149 | 108 | 9 | |
JavaScript | 5.3% | 678 | 59 | 12 | |
Sass | 3.3% | 425 | 0 | 1 | |
SVG | 1.8% | 229 | 2 | 6 | |
HTML | 0.4% | 45 | 0 | 1 | |
Total | 12,791 | 1,959 | 85 |
Lines of code | 4,544 |
---|---|
Total complexity | 1,131 |
Median class complexity | 9.0 |
Median method complexity | 2.0 |
Most complex class | TGM_Plugin_Activation |
Most complex function | TGMPA_List_Table::process_bulk_actions() |
Classes | 19 |
---|---|
Methods | 168 |
Functions | 156 |
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
4[28-Sep-2021 19:52:42 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[28-Sep-2021 19:52:42 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[28-Sep-2021 19:52:48 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663
[28-Sep-2021 19:52:48 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. 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.7.0.) in /wp-includes/functions.php on line 5663