MinecraftSV Status 0.1
Does MinecraftSV Status work with WordPress 6.5.2 and PHP 8.1.12? A smoke test was performed on .
Summary
Errors
| The plugin could not be activated | |
| 1 | PHP fatal errors |
| No JavaScript exceptions | |
| No resource errors |
Performance
No data available.
Environment
| WordPress version | 6.5.2 |
|---|---|
| PHP version | 8.1.12 |
| MySQL version | 10.6.10 |
| PHP memory limit | 512M |
Plugin Info
| Last updated | |
|---|---|
| Active installs | 50+ |
| WordPress.org page | https://wordpress.org/plugins/minecraft-server-status-checker/ |
| Badges |
|
Pages 1
Plugins ‹ Test site — WordPress
| URL | /wp-admin/plugins.php?plugin=minecraft-server-status-checker%2Fminecraftsv.php |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=minecraft-server-status-checker%2Fminecraftsv.php&plugin_status=all&paged=1&s&_wpnonce=e963506701 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.253 s |
| Memory usage | 3.38 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
No benchmark data available.
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.
| Language | % | Lines of code | Comment lines | Files | |
|---|---|---|---|---|---|
| PHP | 57.7% | 60 | 10 | 2 | |
| CSS | 42.3% | 44 | 9 | 2 | |
| Total | 104 | 19 | 4 | ||
PHP Code Analysis | More results »
| Lines of code | 58 |
|---|---|
| Total complexity | 10 |
| Median class complexity | 10.0 |
| Median method complexity | 2.0 |
| Most complex class | mcsv_status |
| Most complex function | mcsv_status::widget() |
| Classes | 1 |
|---|---|
| Methods | 5 |
| Functions | 0 |
Additions
No data available.
PHP Error Log 8 lines
[23-Apr-2024 17:03:39 UTC] PHP Fatal error: Uncaught TypeError: call_user_func_array(): Argument #1 ($callback) must be a valid callback, non-static method mcsv_status::activate() cannot be called statically in /wp-includes/class-wp-hook.php:324
Stack trace:
#0 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#1 /wp-includes/plugin.php(517): WP_Hook->do_action()
#2 /wp-admin/includes/plugin.php(705): do_action()
#3 /wp-admin/plugins.php(60): activate_plugin()
#4 {main}
thrown in /wp-includes/class-wp-hook.php on line 324
See also: All tests for this plugin