1. Home
  2. Winspark Widget Specific Category Posts
  3. 1.0

Winspark Widget Specific Category Posts 1.0

Does "Winspark Widget Specific Category Posts" work with WordPress 6.0.1 and PHP 7.4.8? A smoke test was performed on .

Summary

Errors
No PHP errors, warnings or notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Looks good! No problems were detected.
Performance

Memory usage: 1.96 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.

Environment
WordPress version6.0.1
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs <10
WordPress.org page https://wordpress.org/plugins/winspark-widget-specific-posts/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 3

Plugins ‹ Test site — WordPress

Page screenshot: Plugins ‹ Test site — WordPress
URL /wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL /wp-admin/plugins.php?action=activate&plugin=winspark-widget-specific-posts%2Fwinspark_widget_specific_posts.php&plugin_status=all&paged=1&s&_wpnonce=1bc389252f
Aspect after-activation
HTTP status 200
Load time 0.273 s
Memory usage 3.7 MiB
JS errors None
Resource errors None

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.179 s
Memory usage 3.56 MiB
JS errors None
Resource errors None

Widgets ‹ Test site — WordPress

Page screenshot: Widgets ‹ Test site — WordPress
URL /wp-admin/widgets.php
Aspect new-sidebar-widgets
HTTP status 200
Load time 1.918 s
Memory usage 5.54 MiB
JS errors
External errors: The following JavaScript errors were probably triggered by WordPress itself, or by compatibility issues in the test runner. They are not related to the plugin. 
[
    {
        "message": "TypeError: Cannot read properties of null (reading 'offsetHeight')\n    at t (/wp-includes/js/dist/widgets.min.js?ver=80e98954519d1dad7a91a2248dbc2cc9:7:10419)\n    at IntersectionObserver.n.threshold (/wp-includes/js/dist/widgets.min.js?ver=80e98954519d1dad7a91a2248dbc2cc9:7:10591)",
        "trace": null,
        "code": null
    }
]
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.318 s0.376 s+0.058 s3.72 MiB3.73 MiB+ 8.45 KiB
/wp-admin/edit.php0.187 s0.256 s+0.069 s3.75 MiB3.76 MiB+ 8.45 KiB
/wp-admin/post-new.php1.610 s1.159 s-0.451 s5.55 MiB5.56 MiB+ 16.8 KiB
/wp-admin/upload.php0.439 s0.366 s-0.073 s3.68 MiB3.69 MiB+ 7.31 KiB
/wp-admin/options-writing.php0.151 s0.153 s+0.002 s3.62 MiB3.6 MiB- 12.78 KiB
/wp-admin/media-new.php0.429 s0.190 s-0.239 s3.66 MiB3.67 MiB+ 7.48 KiB
/wp-admin/edit-tags.php?taxonomy=category0.177 s0.196 s+0.019 s3.69 MiB3.7 MiB+ 8.39 KiB
/wp-admin/post-new.php?post_type=page0.904 s0.886 s-0.018 s5.54 MiB5.55 MiB+ 8.39 KiB
/wp-admin/options-discussion.php0.205 s0.298 s+0.093 s3.6 MiB3.6 MiB+ 7.8 KiB
/wp-admin/edit-comments.php0.207 s0.216 s+0.009 s3.69 MiB3.7 MiB+ 7.3 KiB
/0.263 s0.207 s-0.056 s3.6 MiB3.56 MiB- 46.07 KiB
Average 0.445 s0.391 s-0.053 s4.01 MiB4.01 MiB+ 1.96 KiB

Code Statistics

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.

PHP
Language % Lines of code Comment lines Files
PHP100.0%90751
Total 90 75 1

PHP Code Analysis | More results »

Lines of code 94
Total complexity 15
Median class complexity 14.0
Median method complexity 3.0
Most complex class winspark_widget_specific_posts
Most complex function winspark_widget_specific_posts::widget()
Classes 1
Methods 4
Functions 1

Additions

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.

Options wp_options 1

Sidebar Widgets 1

ID Name
widget_specific_postsWinspark Specific Posts

PHP Error Log

The log file is empty.

See also: All tests for this plugin