Trinary Star

In the meantime, I found one that had been tampered with because the site did not show. LiteSpeed Cache version was 5.4, so it was not updated despite expectations. So I tried to update it but failed. Then I tried to delete it, but I could not. Then I found funny directories in the WordPress, and I investigated them. Those directories were the reason that that website did not show. More precisely the content of them were compatible with the latest WordPress 6.6.1 but not WordPress 4.9.x or earlier. That is how I managed to find that that website was tampered with. If it were running on WordPress 6.6.1, I am quite sure that I would not have been able to find that it had been hacked. The latest version of WordPress is the safest? That depends. Please do not blame me for something like that. I have been running websites for a quarter century. Maybe you could give me that sort of advice a quarter century ago, or even better maybe half a century ago for that matter. Then I may have learned a thing or two.

By the way, you made a poor excuse. You could develop a patch for all older versions and a special installer of that patch. But you just did not do it and decided to leave older websites to die. Since this security issue was so extremely serious, you should have expended all your resources to avoid all contingencies that this may cause. You should not have open-sourced this plugin in the first place as I wrote earlier. It should have been part of the LiteSpeed server software and undisclosed to the public. Then it would be much safer, at least safer than to use the latest version of WordPress maybe.

That was a quick response. One of the hosting companies I use applied the latest LiteSpeed Cache update across their entire network. I think that was a good decision. But then I had to go through all of my WordPress sites checking everything because this caused compatibility issues (plus other issues which cannot be disclosed here), applying the update to WordPress 4.8.x or earlier as well. If you were to fix vulnerabilities, you should have fixed vulnerabilities in all your previous versions of LiteSpeed Cache for all the previously compatible versions of WordPress, namely WordPress 3.3 or later. In other words, sites running on WordPress 3.3 to 4.8.x were left to die because you did not care about them. After careful consideration, I deleted the LiteSpeed Cache plugin from many of my WordPress sites.

Also, it looks like the Geo IP database is unavailable right now, so you may want to use Count per Day 3.4.1 which includes the Geo IP database.

But if you have downloaded the Geo IP database before and have happened to back it up in your computer, all you need to do it is just upload it from your computer into your WordPress site, and it works with CPD 3.5.7.

The Geo IP database cannot be upgraded now, but your old Geo IP database would serve the purpose for most of us.

If you happen to have a problem downloading a specific CPD version, you can probably find it at “archive.org.”

But if you use your brain, you can still directly download the past versions of Count per Day from www.ads-software.com. If you don’t want to think, just go to archive.org.

In any case, you don’t need to worry about getting malware if you stick to 3.5.7 or below.

• This reply was modified 4 years, 11 months ago by Trinary Star.
• This reply was modified 4 years, 11 months ago by Trinary Star.

I have downgraded Count per Day to 3.5.7 which the original creator, Tom, coded. I am also keeping WordPress 4.9.x to make Count per Day 3.5.7 work all right (for that purpose, WordPress 4.8.x is even better).

There is a way to keep your favorite WordPress version if your hosting company forces you to upgrade WordPress.

If you happen to upgrade WordPress by mistake, the “WP Downgrade | Specific Core Version” plugin will take you back to your favorite WordPress version.

That way you can probably keep using Count per Day for the next several years or so, and I intend to do so. In the meantime, I will wait for someone to develop Count per Day again.

I do not think data migration is possible unless someone develops a migration script. It would be much easier to take up where Tom left off.

I thought maybe you could put the same link with the name (anchor text) “all-time” next to 30d to avoid confusion.

Also, stats are displayed in too light color like #bbb. It is too difficult to read. Perhaps most people find them that way. Why don’t you show the stats in black like #000?

Finally, the color of the graph is too light too. While it is totally visible, it would look better if it were in darker color, I think. And the top three posts in the list do not need to be in larger font sizes.

As for the use of the graph, the graph of views of all the posts is not very useful because most users of this plugin probably use stats like GA, Count Per Day, etc. Graphs that show when each post gets how many views would be more useful if they do not use too much of server resource. I also think graphs that show how many views each post has achieved would be typical but very useful too.

Thank you.

I got it. Thanks.

I thought it might raise a security issue if I keep exposing the login URL of my blog. Actually my accounts everywhere (Google, Microsoft, and major shopping sites) have been hacked into by several people at least several times for the past six months or so, and I am getting more concerned about security issues than ever. I have been changing passwords to longer and longer, and more and more complex ones, but I am not sure whether that would be enough to stop those hackers. This may not be an extreme case, or would it?

I forgot to write the version of WordPress I am using. It is 4.4.

I want to know how I could change the title separator from “|” to “-” with Twenty Sixteen, Twenty Fifteen and Twenty Fourteen.

Please help me. Thank you.