Does SMS Sharing Button for Jetpack work with WordPress 6.6.2 and PHP 8.1.12? A smoke test was performed on .
No PHP errors, warnings or notices | |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors | |
Looks good! No problems were detected. |
Memory usage: 0 bytes
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.6.2 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 60+ |
WordPress.org page | https://wordpress.org/plugins/sms-sharing-button-for-jetpack/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=sms-sharing-button-for-jetpack%2Fjetpack-sms.php&plugin_status=all&paged=1&s&_wpnonce=12a711a216 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.246 s |
Memory usage | 3.51 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.190 s |
Memory usage | 3.4 MiB |
JS errors | None |
Resource errors | None |
No benchmark data available.
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 | 58.8% | 217 | 22 | 3 | |
CSS | 22.0% | 81 | 8 | 1 | |
PO File | 19.0% | 70 | 23 | 2 | |
JavaScript | 0.3% | 1 | 0 | 1 | |
Total | 369 | 53 | 7 |
Lines of code | 217 |
---|---|
Total complexity | 44 |
Median class complexity | 12.0 |
Median method complexity | 2.0 |
Most complex class | Jetpack_SMS_Pack |
Most complex function | Jetpack_SMS_Pack::init() |
Classes | 3 |
---|---|
Methods | 22 |
Functions | 2 |
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.
No new entries found.
The log file is empty.