Does Advanced Floating Content work with WordPress 6.1 and PHP 7.4.8? A smoke test was performed on .
10 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 42.2 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 | 9,000+ |
WordPress.org page | https://wordpress.org/plugins/advanced-floating-content-lite/ |
Badges |
|
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=advanced-floating-content-lite%2Fadvanced-floating-content.php&plugin_status=all&paged=1&s&_wpnonce=e73430df52 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.437 s |
Memory usage | 3.55 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit.php?post_type=ct_afc |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.186 s |
Memory usage | 3.57 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/post-new.php?post_type=ct_afc |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 1.174 s |
Memory usage | 3.73 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.257 s |
Memory usage | 3.46 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.341 s | 0.325 s | -0.016 s | 3.55 MiB | 3.59 MiB | + 42.18 KiB |
/wp-admin/edit.php | 0.177 s | 0.195 s | +0.018 s | 3.58 MiB | 3.62 MiB | + 41.16 KiB |
/wp-admin/post-new.php | 0.933 s | 1.083 s | +0.150 s | 5.48 MiB | 5.53 MiB | + 53.76 KiB |
/wp-admin/upload.php | 0.549 s | 0.484 s | -0.065 s | 3.49 MiB | 3.53 MiB | + 41.36 KiB |
/wp-admin/options-writing.php | 0.143 s | 0.142 s | -0.001 s | 3.48 MiB | 3.51 MiB | + 24.04 KiB |
/wp-admin/media-new.php | 0.232 s | 0.180 s | -0.052 s | 3.47 MiB | 3.51 MiB | + 43.72 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.230 s | 0.175 s | -0.055 s | 3.5 MiB | 3.56 MiB | + 58.57 KiB |
/wp-admin/post-new.php?post_type=page | 0.911 s | 0.926 s | +0.015 s | 5.47 MiB | 5.52 MiB | + 45.31 KiB |
/wp-admin/options-discussion.php | 0.202 s | 0.215 s | +0.013 s | 3.47 MiB | 3.53 MiB | + 63.41 KiB |
/wp-admin/edit-comments.php | 0.184 s | 0.195 s | +0.011 s | 3.5 MiB | 3.56 MiB | + 61.63 KiB |
/ | 0.240 s | 0.202 s | -0.038 s | 3.47 MiB | 3.46 MiB | - 10.88 KiB |
Average | 0.377 s | 0.375 s | -0.002 s | 3.86 MiB | 3.9 MiB | + 42.2 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 | 88.4% | 594 | 600 | 14 | |
CSS | 10.0% | 67 | 8 | 2 | |
JavaScript | 1.6% | 11 | 27 | 2 | |
Total | 672 | 635 | 18 |
Lines of code | 443 |
---|---|
Total complexity | 75 |
Median class complexity | 7.0 |
Median method complexity | 1.0 |
Most complex class | Advanced_Floating_Content_Admin |
Most complex function | Advanced_Floating_Content_Public::css_styling() |
Classes | 7 |
---|---|
Methods | 40 |
Functions | 5 |
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
3wp_usermeta
1ID | Name |
---|---|
ct_afc | Advanced Floating Content |
{
"ct_afc": {
"submitdiv": {
"title": "Advanced Floating Content",
"context": "side"
},
"ct_information": {
"title": "Code Tides",
"context": "side"
},
"advanced_floating_content_meta_box": {
"title": "Floating Content Details",
"context": "advanced"
},
"advanced_floating_content_premium_meta_box": {
"title": "Premium Options",
"context": "advanced"
}
}
}
[02-Nov-2022 20:08:14 UTC] PHP Notice: Undefined variable: responsive_view_480 in /wp-content/plugins/advanced-floating-content-lite/public/class-advanced-floating-content-public.php on line 136
[02-Nov-2022 20:08:14 UTC] PHP Notice: Undefined variable: responsive_view_320 in /wp-content/plugins/advanced-floating-content-lite/public/class-advanced-floating-content-public.php on line 136
[02-Nov-2022 20:08:14 UTC] PHP Notice: Undefined variable: content in /wp-content/plugins/advanced-floating-content-lite/public/class-advanced-floating-content-public.php on line 137
[02-Nov-2022 20:08:14 UTC] PHP Notice: Function wp_add_inline_style was called <strong>incorrectly</strong>. Do not pass <code><style></code> tags to <code>wp_add_inline_style()</code>. 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 3.7.0.) in /wp-includes/functions.php on line 5835
[02-Nov-2022 20:08:14 UTC] PHP Notice: Function wp_add_inline_script was called <strong>incorrectly</strong>. Do not pass <code><script></code> tags to <code>wp_add_inline_script()</code>. 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 4.5.0.) in /wp-includes/functions.php on line 5835
[02-Nov-2022 20:08:22 UTC] PHP Notice: Undefined variable: responsive_view_480 in /wp-content/plugins/advanced-floating-content-lite/public/class-advanced-floating-content-public.php on line 136
[02-Nov-2022 20:08:22 UTC] PHP Notice: Undefined variable: responsive_view_320 in /wp-content/plugins/advanced-floating-content-lite/public/class-advanced-floating-content-public.php on line 136
[02-Nov-2022 20:08:22 UTC] PHP Notice: Undefined variable: content in /wp-content/plugins/advanced-floating-content-lite/public/class-advanced-floating-content-public.php on line 137
[02-Nov-2022 20:08:22 UTC] PHP Notice: Function wp_add_inline_style was called <strong>incorrectly</strong>. Do not pass <code><style></code> tags to <code>wp_add_inline_style()</code>. 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 3.7.0.) in /wp-includes/functions.php on line 5835
[02-Nov-2022 20:08:22 UTC] PHP Notice: Function wp_add_inline_script was called <strong>incorrectly</strong>. Do not pass <code><script></code> tags to <code>wp_add_inline_script()</code>. 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 4.5.0.) in /wp-includes/functions.php on line 5835