Ivan Arnaudov

Huh? This limitation has been clearly stated in the features description.
Internet Archive link dated 27 November

1. 21+ Channels
2. 1 Active Widget
3. 2 Active Channels
4. (…)

It is totally unfair of you to downvote this plugin when you didn’t read the description.

Yes, thanks!! Marking issue as resolved.

FWIF, sd_rewrite_rules() which operates on the same value, also breaks for the same reason (and leaves the dropdown list empty). So the underlying reason should be the way rewrite_rules are fetched?

Note: I am testing this on a dev site with 1 static page of content and default permalinks. Might be simply there aren’t any rewrite_rules? Will check the DB and update this reply.

Update: Yes, it turned out the rewrite_rules within wp_options can be empty. Hence the root cause for failure by sd_rewrite_rules() and sd_rewrite_rules_count().

So the possible solution would be to gracefully handle the rare condition where there are zero rewrite rules.

• This reply was modified 2 years, 8 months ago by Ivan Arnaudov. Reason: Updated with more info and possible solution

Please update to v2.0.2 which I’ve just released and let me know if that works better for you.

Yes, it works now without issues. Tested up to PHP 8.1

I rarely use Litespeed-powered server/hosting, and will spend some time playing around with it for a future release.

No need for specific testing as far as my experience shows. Litespeed is designed to be drop-in compatible with Apache, and the only significant difference is that their team compiles and packages PHP themselves, which means sometimes they might be a minor version behind the most current version for a given PHP branch.

Anyway I will be putting your plugin onto several websites under different Litespeed servers and will hopefully be able to catch and report other issues, if any.

Thanks for taking care of this! Marking this thread as resolved.

Hi @qriouslad, thanks for responding. I am using shared hosting (Litespeed) and can reproduce the issue under PHP 8.0/8.1. The code executes under PHP 7.4 and earlier versions with some non-breaking issues.

I believe the root cause for the problem is a combination of a configuration limitation of my host under PHP 8.x and a mishandling of the ‘Disk Usage’ string on your end.

1. The configuration limitation is that my host allows exec() but does not have a setting to allow shell_exec() and it makes it impossible to extract the needed values to work with on your end. In both PHP 7.4 and PHP 8.0, your module reports CPU uptime, Load Average, RAM usage and the output of sd_total_disk_space() as ‘undetectable’.

(I tested that last one by replacing the whole line that populates the ‘Disk Usage’ content with 'content' => $this->sd_total_disk_space() to see what happens.)

Maybe consider using exec() instead of shell_exec()? I don’t have a lot of experience with PHP but the way I see it, exec() can be made to return the full output of a command as an array, and will even return a stat code for successful operation completion?

2. The problem with your code is that it will use the output of sd_total_disk_space twice on that line regardless of whether it returns a numeric value or ‘undetectable’. PHP 7.4 lets this slide by throwing a series of warnings (non-numeric value detected, division by zero) but PHP 8.x is more strict about casting strings as ints and floats, and will have none of it. That is why under PHP 7.4 I get a <strong>Disk Usage</strong> 1 TB free (INF%) of bytes total message but under PHP 8.x WordPress breaks completely.

While there is obviously nothing you can do about my host configuration, I believe with this information you will be able to improve the process of reporting disk storage to allow for ‘undetectable’ total disk space.

A separate issue: You have a typo within sd_site_health() on line 366 in the same file (misspelled $output as $ouput in the $issues_total count check). In case your line numbering has changed, this screenshot refers: https://i.imgur.com/naKHCSZ.jpg

• This reply was modified 2 years, 8 months ago by Ivan Arnaudov.
• This reply was modified 2 years, 8 months ago by Ivan Arnaudov. Reason: Improved suggestion

Update: issue is carried over following the 1.60 update (error line has moved).

Uncaught TypeError: Unsupported operand types: float / string in /home/xxxxxxx/public_html/wp-content/plugins/system-dashboard/admin/class-system-dashboard-admin.php:6464

No need to delete & reinstall. Just download the new (0.95.8) version, extract it in a local folder and upload the contents of that folder via FTP over the old one (0.95.7), and your website will come back from the dead as if nothing happened.

@mrioia: ProxyFCGIBackendType GENERIC did not work for me but I was able to switch from FPM to FCGId because I run my own host. A big THANK YOU for this valuable info.

Thank you for responding so quickly, Frank!

I understand the logic of the default settings, but what confused me is that Revslider will still work on a different website, running the very same Autoptimize parameters. I guess I have to assume that it depends on the way the theme developer has integrated Revslider and move on.

Thank you once again, I admire your work!

Ivan

Updating TimThumb alone ***will not*** fix the issue.

1. The hack entry must be removed — for me it was two files called
/blog/wp-content/upd.php
/blog/wp-content/eab9c5e9815adc4c40a6557495eed6d3.php

2A. All references to counter-wordpress.com inside html/php files must be removed by hand, or
2B. The WP and theme files must be deleted and restored from a secure copy.

ElegantThemes used the TimThumb library until a big hole was discovered in TimThumb recently (beginning of August).

I am in the exact same mess right now; I am not a security expert and a friend is helping me out but basically you should assume that your hosting is compromised (the attacker can see your passwords and everything in your hosting panel).

Begin by stopping the website, dumping the files on your HDD and scanning them for the following:

eval(base64_decode
$a = ‘m’.’d5′
$y = ‘base’.’6′

and also for all references to counter-wordpress.com

Change your host panel password, SQL database website and everything else that may be accessible to somebody who can log on to your hosting.

I will appreciate comments from other, more knowledgeable folks as well.