Does IgnitionDeck work with WordPress 5.9.3 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: 138.66 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.9.3 |
---|---|
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=14b0bf4d58 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 2.893 s |
Memory usage | 3.65 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/plugins.php?page=idf-plugins |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.319 s |
Memory usage | 3.52 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=idf |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.681 s |
Memory usage | 3.65 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=idf-themes |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 1.794 s |
Memory usage | 3.71 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.446 s |
Memory usage | 3.41 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.571 s | 0.426 s | -0.145 s | 3.37 MiB | 3.47 MiB | + 104.44 KiB |
/wp-admin/edit.php | 0.303 s | 0.284 s | -0.019 s | 3.4 MiB | 3.57 MiB | + 170.8 KiB |
/wp-admin/post-new.php | 1.344 s | 1.682 s | +0.338 s | 5.68 MiB | 5.78 MiB | + 103.88 KiB |
/wp-admin/upload.php | 0.509 s | 0.846 s | +0.337 s | 3.25 MiB | 3.42 MiB | + 175.85 KiB |
/wp-admin/options-writing.php | 0.382 s | 0.315 s | -0.067 s | 3.24 MiB | 3.4 MiB | + 161.91 KiB |
/wp-admin/media-new.php | 0.389 s | 0.379 s | -0.010 s | 3.23 MiB | 3.4 MiB | + 176.02 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.300 s | 0.354 s | +0.054 s | 3.27 MiB | 3.43 MiB | + 169.05 KiB |
/wp-admin/post-new.php?post_type=page | 1.712 s | 1.375 s | -0.337 s | 5.68 MiB | 5.77 MiB | + 99.48 KiB |
/wp-admin/options-discussion.php | 0.317 s | 0.416 s | +0.099 s | 3.22 MiB | 3.4 MiB | + 178.56 KiB |
/wp-admin/edit-comments.php | 0.391 s | 0.400 s | +0.009 s | 3.27 MiB | 3.43 MiB | + 167.02 KiB |
/ | 0.613 s | 0.416 s | -0.197 s | 3.4 MiB | 3.41 MiB | + 18.27 KiB |
Average | 0.621 s | 0.627 s | +0.006 s | 3.73 MiB | 3.86 MiB | + 138.66 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 | 40.6% | 5,280 | 1,808 | 52 | |
JSON | 24.5% | 3,188 | 0 | 4 | |
CSS | 24.3% | 3,161 | 108 | 9 | |
JavaScript | 5.2% | 678 | 59 | 12 | |
Sass | 3.3% | 425 | 0 | 1 | |
SVG | 1.8% | 229 | 2 | 6 | |
HTML | 0.3% | 45 | 0 | 1 | |
Total | 13,006 | 1,977 | 85 |
Lines of code | 4,748 |
---|---|
Total complexity | 1,159 |
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 | 158 |
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[04-May-2022 18:58:31 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 5775
[04-May-2022 18:58:31 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 5775
[04-May-2022 18:58:43 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 5775
[04-May-2022 18:58:43 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 5775