Does Data Track work with WordPress 7.0 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: 93.68 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 | 7.0 |
|---|---|
| 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=751fb3ef93 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.583 s |
| Memory usage | 3.95 MiB |
| JS errors | |
| Resource errors | None |
| URL | /wp-admin/edit.php?post_type=wpdt_data |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.483 s |
| Memory usage | 3.97 MiB |
| JS errors | |
| Resource errors | None |
| URL | /wp-admin/post-new.php?post_type=wpdt_data |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 2.088 s |
| Memory usage | 6.8 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 | 1.042 s |
| Memory usage | 3.92 MiB |
| JS errors | |
| Resource errors | None |
| URL | /wp-admin/options-general.php?page=wpdt-plugin |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.143 s |
| Memory usage | N/A |
| JS errors | None |
| Resource errors | None |
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.298 s |
| Memory usage | 4.29 MiB |
| JS errors | None |
| Resource errors | None |
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 1.325 s | 0.863 s | -0.462 s | 3.93 MiB | 3.99 MiB | + 62.73 KiB |
| /wp-admin/edit.php | 0.776 s | 0.553 s | -0.223 s | 3.98 MiB | 4.05 MiB | + 65.11 KiB |
| /wp-admin/post-new.php | 2.367 s | 2.295 s | -0.072 s | 6.56 MiB | 6.81 MiB | + 261.38 KiB |
| /wp-admin/upload.php | 0.712 s | 1.212 s | +0.500 s | 3.89 MiB | 3.93 MiB | + 48.13 KiB |
| /wp-admin/options-writing.php | 0.991 s | 0.645 s | -0.346 s | 3.86 MiB | 3.91 MiB | + 52.13 KiB |
| /wp-admin/media-new.php | 1.078 s | 0.575 s | -0.503 s | 3.85 MiB | 3.91 MiB | + 60.32 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.538 s | 0.516 s | -0.022 s | 3.86 MiB | 3.93 MiB | + 64.45 KiB |
| /wp-admin/post-new.php?post_type=page | 1.769 s | 1.960 s | +0.191 s | 6.55 MiB | 6.8 MiB | + 254.63 KiB |
| /wp-admin/options-discussion.php | 0.805 s | 0.728 s | -0.077 s | 3.86 MiB | 3.91 MiB | + 48.31 KiB |
| /wp-admin/edit-comments.php | 1.002 s | 0.554 s | -0.448 s | 3.88 MiB | 3.93 MiB | + 48.13 KiB |
| / | 0.318 s | 0.271 s | -0.047 s | 4.23 MiB | 4.29 MiB | + 65.2 KiB |
| Average | 1.062 s | 0.925 s | -0.137 s | 4.4 MiB | 4.5 MiB | + 93.68 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"
}
}
}[01-Jun-2026 16:47:33 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 6170
[01-Jun-2026 16:47:33 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 6170
[01-Jun-2026 16:47:39 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(341): wpdt_options_page()
#2 /wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()
#3 /wp-includes/plugin.php(522): WP_Hook->do_action()
#4 /wp-admin/admin.php(264): 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
[01-Jun-2026 16:47:43 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 6170
[01-Jun-2026 16:47:43 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 6170
[01-Jun-2026 16:47:50 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 6170
[01-Jun-2026 16:47:50 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 6170