Does GoDAM work with WordPress 6.7.2 and PHP 8.1.12? A smoke test was performed on .
3 | PHP notices |
1 | JavaScript exceptions |
All test pages loaded successfully | |
No resource errors |
Memory usage: 125.24 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.053 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 6.7.2 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 80+ |
WordPress.org page | https://wordpress.org/plugins/godam/ |
Badges |
|
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=godam%2Fgodam.php&plugin_status=all&paged=1&s&_wpnonce=a49a811621 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.925 s |
Memory usage | 3.61 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=rtgodam |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 1.072 s |
Memory usage | 3.6 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=rtgodam_video_editor |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 2.434 s |
Memory usage | 3.61 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=rtgodam_analytics |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.751 s |
Memory usage | 3.6 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=rtgodam_help |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.545 s |
Memory usage | 3.6 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.908 s |
Memory usage | 3.52 MiB |
JS errors |
|
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.342 s | 0.534 s | +0.192 s | 3.48 MiB | 3.6 MiB | + 118.02 KiB |
/wp-admin/edit.php | 0.210 s | 0.297 s | +0.087 s | 3.54 MiB | 3.66 MiB | + 116.23 KiB |
/wp-admin/post-new.php | 0.842 s | 1.121 s | +0.279 s | 5.92 MiB | 6.1 MiB | + 184.11 KiB |
/wp-admin/upload.php | 0.763 s | 0.463 s | -0.300 s | 3.49 MiB | 3.6 MiB | + 106.15 KiB |
/wp-admin/options-writing.php | 0.208 s | 0.236 s | +0.028 s | 3.47 MiB | 3.58 MiB | + 110.55 KiB |
/wp-admin/media-new.php | 0.282 s | 0.425 s | +0.143 s | 3.46 MiB | 3.58 MiB | + 118.74 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.176 s | 0.234 s | +0.058 s | 3.48 MiB | 3.59 MiB | + 121.66 KiB |
/wp-admin/post-new.php?post_type=page | 0.700 s | 0.684 s | -0.016 s | 5.92 MiB | 6.1 MiB | + 181.1 KiB |
/wp-admin/options-discussion.php | 0.287 s | 0.323 s | +0.036 s | 3.47 MiB | 3.58 MiB | + 107.67 KiB |
/wp-admin/edit-comments.php | 0.222 s | 0.321 s | +0.099 s | 3.49 MiB | 3.6 MiB | + 106.7 KiB |
/ | 0.327 s | 0.309 s | -0.018 s | 3.41 MiB | 3.52 MiB | + 106.71 KiB |
Average | 0.396 s | 0.450 s | +0.053 s | 3.92 MiB | 4.05 MiB | + 125.24 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 | |
---|---|---|---|---|---|
JavaScript | 50.9% | 13,790 | 7,830 | 16 | |
CSS | 33.0% | 8,938 | 89 | 12 | |
PHP | 15.6% | 4,216 | 1,847 | 38 | |
JSON | 0.5% | 123 | 0 | 1 | |
SVG | 0.0% | 10 | 0 | 2 | |
Total | 27,077 | 9,766 | 69 |
Lines of code | 4,024 |
---|---|
Total complexity | 691 |
Median class complexity | 15.0 |
Median method complexity | 2.0 |
Most complex class | RTGODAM_RetranscodeMedia |
Most complex function | RTGODAM_RetranscodeMedia::retranscode_interface() |
Classes | 21 |
---|---|
Methods | 131 |
Functions | 34 |
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
1[11-Apr-2025 11:02:30 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://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6114
[11-Apr-2025 11:02:33 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://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6114
[11-Apr-2025 11:02:35 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://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6114