Does Custom Twitter Feeds work with WordPress 6.3.2 and PHP 8.1.12? A smoke test was performed on .
4 | PHP warnings |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 190.66 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.3.2 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 100,000+ |
WordPress.org page | https://wordpress.org/plugins/custom-twitter-feeds/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=custom-twitter-feeds%2Fcustom-twitter-feed.php&plugin_status=all&paged=1&s&_wpnonce=4b8fba4d60 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.859 s |
Memory usage | 3.72 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=ctf-feed-builder |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.898 s |
Memory usage | 5.35 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=ctf-settings |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.504 s |
Memory usage | 3.64 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=custom-twitter-feeds |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.186 s |
Memory usage | 2.92 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=ctf-support |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.392 s |
Memory usage | 3.6 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=ctf-about-us |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.399 s |
Memory usage | 2.98 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=custom-twitter-feeds&tab=more |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.189 s |
Memory usage | 2.92 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.260 s |
Memory usage | 3.2 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/widgets.php |
---|---|
Aspect | new-sidebar-widgets |
HTTP status | 200 |
Load time | 2.231 s |
Memory usage | 5.39 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.368 s | 0.464 s | +0.096 s | 2.83 MiB | 3.03 MiB | + 204.05 KiB |
/wp-admin/edit.php | 0.201 s | 0.219 s | +0.018 s | 2.85 MiB | 3.05 MiB | + 205.26 KiB |
/wp-admin/post-new.php | 0.737 s | 1.008 s | +0.271 s | 5.22 MiB | 5.44 MiB | + 232.7 KiB |
/wp-admin/upload.php | 0.611 s | 0.392 s | -0.219 s | 2.77 MiB | 2.95 MiB | + 186.99 KiB |
/wp-admin/options-writing.php | 0.225 s | 0.219 s | -0.006 s | 2.76 MiB | 2.94 MiB | + 178.02 KiB |
/wp-admin/media-new.php | 0.379 s | 0.223 s | -0.156 s | 2.74 MiB | 2.94 MiB | + 202.09 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.201 s | 0.218 s | +0.017 s | 2.76 MiB | 2.96 MiB | + 202.8 KiB |
/wp-admin/post-new.php?post_type=page | 0.590 s | 0.816 s | +0.226 s | 5.21 MiB | 5.43 MiB | + 228.28 KiB |
/wp-admin/options-discussion.php | 0.210 s | 0.282 s | +0.072 s | 2.75 MiB | 2.94 MiB | + 189.83 KiB |
/wp-admin/edit-comments.php | 0.437 s | 0.242 s | -0.195 s | 2.78 MiB | 2.96 MiB | + 187.23 KiB |
/ | 0.303 s | 0.282 s | -0.021 s | 3.13 MiB | 3.21 MiB | + 80.05 KiB |
Average | 0.387 s | 0.397 s | +0.009 s | 3.26 MiB | 3.44 MiB | + 190.66 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 | 47.5% | 22,859 | 5,600 | 147 | |
CSS | 41.3% | 19,887 | 548 | 13 | |
JavaScript | 10.4% | 5,025 | 982 | 15 | |
SVG | 0.4% | 183 | 0 | 14 | |
HTML | 0.2% | 103 | 3 | 1 | |
JSON | 0.1% | 48 | 0 | 1 | |
Total | 48,105 | 7,133 | 191 |
Lines of code | 19,349 |
---|---|
Total complexity | 3,814 |
Median class complexity | 11.0 |
Median method complexity | 2.0 |
Most complex class | TwitterFeed\CtfFeed |
Most complex function | TwitterFeed\CTF_Settings::legacy_shortcode_atts() |
Classes | 81 |
---|---|
Methods | 683 |
Functions | 85 |
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
8ID | Name |
---|---|
custom-twitter-feeds-widget | Custom Twitter Feeds |
[30-Oct-2023 20:22:56 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/custom-twitter-feeds/inc/Admin/CTF_Support.php on line 462
[30-Oct-2023 20:22:56 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/custom-twitter-feeds/inc/Admin/CTF_Support.php on line 463
[30-Oct-2023 20:22:56 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/custom-twitter-feeds/inc/Admin/CTF_Support.php on line 462
[30-Oct-2023 20:22:56 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/custom-twitter-feeds/inc/Admin/CTF_Support.php on line 463