Does IgnitionDeck work with WordPress 5.9 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.61 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.029 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 5.9 |
---|---|
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=0926ef5d0f |
Aspect | after-activation |
HTTP status | 200 |
Load time | 1.901 s |
Memory usage | 3.54 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/plugins.php?page=idf-plugins |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.355 s |
Memory usage | 3.42 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=idf |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 1.361 s |
Memory usage | 3.42 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=idf-themes |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 1.557 s |
Memory usage | 3.49 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.375 s |
Memory usage | 3.42 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.352 s | 0.334 s | -0.018 s | 3.36 MiB | 3.47 MiB | + 104.44 KiB |
/wp-admin/edit.php | 0.218 s | 0.252 s | +0.034 s | 3.39 MiB | 3.5 MiB | + 106.8 KiB |
/wp-admin/post-new.php | 0.927 s | 1.000 s | +0.073 s | 6.14 MiB | 6.25 MiB | + 103.88 KiB |
/wp-admin/upload.php | 0.393 s | 0.369 s | -0.024 s | 3.24 MiB | 3.41 MiB | + 175.85 KiB |
/wp-admin/options-writing.php | 0.323 s | 0.216 s | -0.107 s | 3.24 MiB | 3.39 MiB | + 161.91 KiB |
/wp-admin/media-new.php | 0.346 s | 0.243 s | -0.103 s | 3.22 MiB | 3.39 MiB | + 176.02 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.256 s | 0.250 s | -0.006 s | 3.25 MiB | 3.42 MiB | + 177.05 KiB |
/wp-admin/post-new.php?post_type=page | 0.745 s | 1.198 s | +0.453 s | 6.14 MiB | 6.24 MiB | + 99.48 KiB |
/wp-admin/options-discussion.php | 0.292 s | 0.366 s | +0.074 s | 3.22 MiB | 3.39 MiB | + 178.56 KiB |
/wp-admin/edit-comments.php | 0.257 s | 0.259 s | +0.002 s | 3.26 MiB | 3.43 MiB | + 167.02 KiB |
/ | 0.336 s | 0.282 s | -0.054 s | 3.35 MiB | 3.42 MiB | + 73.72 KiB |
Average | 0.404 s | 0.434 s | +0.029 s | 3.8 MiB | 3.94 MiB | + 138.61 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,278 | 1,808 | 52 | |
JSON | 24.5% | 3,188 | 0 | 4 | |
CSS | 24.2% | 3,149 | 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 | 12,992 | 1,977 | 85 |
Lines of code | 4,746 |
---|---|
Total complexity | 1,158 |
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[03-Feb-2022 23:11:29 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 5768
[03-Feb-2022 23:11:29 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 5768
[03-Feb-2022 23:11:38 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 5768
[03-Feb-2022 23:11:38 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 5768