Does Data Track work with WordPress 6.8.3 and PHP 8.1.12? A smoke test was performed on .
1 | PHP fatal errors |
6 | PHP notices |
4 | JavaScript exceptions |
All test pages loaded successfully | |
No resource errors |
Memory usage: 103.52 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.8.3 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | <10 |
WordPress.org page | https://wordpress.org/plugins/data-track/ |
Badges |
|
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=data-track%2Fwp-data-track.php&plugin_status=all&paged=1&s&_wpnonce=82a74c0213 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.305 s |
Memory usage | 3.59 MiB |
JS errors |
|
Resource errors | None |
URL | /wp-admin/edit.php?post_type=wpdt_data |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.166 s |
Memory usage | 3.61 MiB |
JS errors |
|
Resource errors | None |
URL | /wp-admin/post-new.php?post_type=wpdt_data |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.624 s |
Memory usage | 6.34 MiB |
JS errors |
|
Resource errors | None |
URL | /wp-admin/edit-tags.php?taxonomy=wpdt_types&post_type=wpdt_data |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.207 s |
Memory usage | 3.56 MiB |
JS errors |
|
Resource errors | None |
URL | /wp-admin/options-general.php?page=wpdt-plugin |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.133 s |
Memory usage | N/A |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.289 s |
Memory usage | 3.5 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.349 s | 0.293 s | -0.056 s | 3.51 MiB | 3.57 MiB | + 66.91 KiB |
/wp-admin/edit.php | 0.202 s | 0.200 s | -0.002 s | 3.57 MiB | 3.63 MiB | + 63.18 KiB |
/wp-admin/post-new.php | 0.785 s | 0.801 s | +0.016 s | 6.06 MiB | 6.35 MiB | + 295.61 KiB |
/wp-admin/upload.php | 0.560 s | 0.553 s | -0.007 s | 3.52 MiB | 3.58 MiB | + 52.96 KiB |
/wp-admin/options-writing.php | 0.200 s | 0.203 s | +0.003 s | 3.5 MiB | 3.56 MiB | + 56.95 KiB |
/wp-admin/media-new.php | 0.285 s | 0.241 s | -0.044 s | 3.49 MiB | 3.56 MiB | + 65.15 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.274 s | 0.193 s | -0.081 s | 3.5 MiB | 3.57 MiB | + 67.98 KiB |
/wp-admin/post-new.php?post_type=page | 0.615 s | 0.619 s | +0.004 s | 6.05 MiB | 6.34 MiB | + 292.23 KiB |
/wp-admin/options-discussion.php | 0.311 s | 0.244 s | -0.067 s | 3.5 MiB | 3.56 MiB | + 53.45 KiB |
/wp-admin/edit-comments.php | 0.196 s | 0.511 s | +0.315 s | 3.52 MiB | 3.57 MiB | + 52.95 KiB |
/ | 0.298 s | 0.248 s | -0.050 s | 3.43 MiB | 3.5 MiB | + 71.3 KiB |
Average | 0.370 s | 0.373 s | +0.003 s | 3.97 MiB | 4.07 MiB | + 103.52 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 | 85.3% | 833 | 496 | 17 | |
JavaScript | 13.8% | 135 | 92 | 3 | |
CSS | 0.8% | 8 | 0 | 2 | |
Total | 976 | 588 | 22 |
Lines of code | 348 |
---|---|
Total complexity | 52 |
Median class complexity | 0.0 |
Median method complexity | 0.0 |
Most complex class | — |
Most complex function | wpdt_admin_options_build_section() |
Classes | 0 |
---|---|
Methods | 0 |
Functions | 29 |
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.
ID | Name |
---|---|
wpdt_data | Data Track |
{
"wpdt_data": {
"wpdt-meta-data": {
"title": "Data",
"context": "side"
}
}
}
[09-Oct-2025 13:51:59 UTC] PHP Notice: Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp-data-track/v1/metaboxes</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 6121
[09-Oct-2025 13:51:59 UTC] PHP Notice: Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp-data-track/v1/remove-field</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 6121
[09-Oct-2025 13:52:02 UTC] PHP Fatal error: Uncaught Error: Call to undefined function wpdt_admin_options_get_tab() in /wp-content/plugins/data-track/inc/admin/options.php:151
Stack trace:
#0 /wp-content/plugins/data-track/inc/admin/options.php(162): wpdt_options_page_tab_nav()
#1 /wp-includes/class-wp-hook.php(324): wpdt_options_page()
#2 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#3 /wp-includes/plugin.php(517): WP_Hook->do_action()
#4 /wp-admin/admin.php(260): do_action()
#5 /wp-admin/options-general.php(10): require_once('...')
#6 {main}
thrown in /wp-content/plugins/data-track/inc/admin/options.php on line 151
[09-Oct-2025 13:52:04 UTC] PHP Notice: Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp-data-track/v1/metaboxes</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 6121
[09-Oct-2025 13:52:04 UTC] PHP Notice: Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp-data-track/v1/remove-field</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 6121
[09-Oct-2025 13:52:08 UTC] PHP Notice: Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp-data-track/v1/metaboxes</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 6121
[09-Oct-2025 13:52:08 UTC] PHP Notice: Function register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wp-data-track/v1/remove-field</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 6121