Does "PubyDoc - Data Tables and Charts" work with WordPress 6.1 and PHP 7.4.8? A smoke test was performed on .
8 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 181.94 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 | 6.1 |
---|---|
PHP version | 7.4.8 |
MySQL version | 8.0.21 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 100+ |
WordPress.org page | https://wordpress.org/plugins/pubydoc-data-tables-and-charts/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=pubydoc-data-tables-and-charts%2Fpublish-your-table.php&plugin_status=all&paged=1&s&_wpnonce=46ea81916a |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.388 s |
Memory usage | 3.69 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=pyt-tables&tab=tables |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.886 s |
Memory usage | 3.85 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=pyt-tables&tab=tables-new |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.339 s |
Memory usage | 3.79 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=pyt-tables&tab=tables-diagrams |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.275 s |
Memory usage | 3.74 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=pyt-tables&tab=settings |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.321 s |
Memory usage | 3.77 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.241 s |
Memory usage | 3.59 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.299 s | 0.284 s | -0.015 s | 3.55 MiB | 3.73 MiB | + 185.79 KiB |
/wp-admin/edit.php | 0.175 s | 0.196 s | +0.021 s | 3.58 MiB | 3.77 MiB | + 185.03 KiB |
/wp-admin/post-new.php | 0.961 s | 1.232 s | +0.271 s | 5.48 MiB | 5.67 MiB | + 194.1 KiB |
/wp-admin/upload.php | 0.555 s | 0.464 s | -0.091 s | 3.49 MiB | 3.67 MiB | + 184.69 KiB |
/wp-admin/options-writing.php | 0.262 s | 0.164 s | -0.098 s | 3.49 MiB | 3.65 MiB | + 165.8 KiB |
/wp-admin/media-new.php | 0.229 s | 0.203 s | -0.026 s | 3.47 MiB | 3.65 MiB | + 184.86 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.173 s | 0.189 s | +0.016 s | 3.5 MiB | 3.7 MiB | + 201.3 KiB |
/wp-admin/post-new.php?post_type=page | 0.859 s | 0.892 s | +0.033 s | 5.47 MiB | 5.65 MiB | + 185.66 KiB |
/wp-admin/options-discussion.php | 0.195 s | 0.206 s | +0.011 s | 3.47 MiB | 3.65 MiB | + 186.98 KiB |
/wp-admin/edit-comments.php | 0.189 s | 0.200 s | +0.011 s | 3.5 MiB | 3.7 MiB | + 204.69 KiB |
/ | 0.246 s | 0.245 s | -0.001 s | 3.47 MiB | 3.59 MiB | + 122.38 KiB |
Average | 0.377 s | 0.389 s | +0.012 s | 3.86 MiB | 4.04 MiB | + 181.94 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 | 48.9% | 13,091 | 1,388 | 71 | |
JavaScript | 27.9% | 7,466 | 171 | 15 | |
CSS | 13.2% | 3,525 | 115 | 16 | |
SVG | 10.0% | 2,671 | 0 | 1 | |
Total | 26,753 | 1,674 | 103 |
Lines of code | 8,334 |
---|---|
Total complexity | 2,328 |
Median class complexity | 25.5 |
Median method complexity | 2.0 |
Most complex class | CellsModelPyt |
Most complex function | CellsModelPyt::saveCellsData() |
Classes | 48 |
---|---|
Methods | 691 |
Functions | 15 |
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
4wp_usermeta
1[10-Nov-2022 12:52:41 UTC] PHP Notice: Function 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 5835
[10-Nov-2022 12:52:41 UTC] PHP Notice: Function 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 5835
[10-Nov-2022 12:52:42 UTC] PHP Notice: Function 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 5835
[10-Nov-2022 12:52:42 UTC] PHP Notice: Function 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 5835
[10-Nov-2022 12:52:43 UTC] PHP Notice: Function 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 5835
[10-Nov-2022 12:52:43 UTC] PHP Notice: Function 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 5835
[10-Nov-2022 12:52:44 UTC] PHP Notice: Function 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 5835
[10-Nov-2022 12:52:44 UTC] PHP Notice: Function 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 5835