AstroNerdBoy

I am a non-commercial site. But ads that earn me pennies suddenly make me commercial. ??</img> But it doesn’t matter ’cause what I use now is as good as Akismet.

And thanks for the sales pitch, that will fall on deaf years, much like my issues fell on your deaf ears. ‘Cause auto-sharing is such a massive, expensive undertaking. As I said, what you are wasting money on and oh so proud of, I can do elsewhere.

I’m done, but I did have to lower the number once more as I still had the odd thumbnail show as my avatar rather than the featured image thumbnail. Not sure what that parameter does.

I used this code, but I had to change it from 600 to 300 in order to start displaying all thumbnails correctly

`function jeherve_custom_thumb_size( $get_image_options ) {
$get_image_options[‘avatar_size’] = 600;

return $get_image_options;
}
add_filter( ‘jetpack_top_posts_widget_image_options’, ‘jeherve_custom_thumb_size’ );`

This is where I was at when it came to All Time stats.

https://wordpress.com/stats/day/posts/anime.astronerdboy.com?startDate=2022-06-13&summarize=1&num=-1

As for the post stat totals, this is an example:

https://wordpress.com/stats/post/37498/anime.astronerdboy.com

I wish I could post screen caps, but for the above post, it shows the total number of views for 2021 (when the post first went out) and 2022. But to get the grand total, I have to add the totals up.

Update: I’ve had Top-10 off and I’m still having deadlocks, though not as severe. That aside, I await your thoughts on the table still not showing an index after recreating the key.

I clicked the button (after a backup) and it says, “Primary Key has been recreated”

But when I looked for the index, phpMyAdmin still shows no index.

Update: Doing the recreation of a primary key did not work. When I click the link to go back to wp-admin URL, the site chokes down for several minutes. What my hosting company tells me is that somehow, Top 10 is causing a ton of deadlocks.

• This reply was modified 2 years, 9 months ago by AstroNerdBoy.
• This reply was modified 2 years, 9 months ago by AstroNerdBoy.

Sorry for the extremely long delay! I got busy once things started working and forgot to come back here. Naturally, if I’m coming back here, a new issue has arisen. Whenever I when to my site’s back in (wp-admin) from the front end, the site would choke down hard. My hosting company believes it is Top 10 doing it, which was hard to believe, but testing seems to bear that out.

That aside, there is no index in wp_vry4pg_top_ten_daily. It says “No index defined!” I seem to recall this happening once before, a LONG time ago. The option exists to “Create an index on” and then it gives me a number selector for number of columns. So what do I need to do to create the index?

Can you please try going to Counter Tracker and disable Page Views in admin to see if this makes a difference.

You are correct. Unchecking that immediately solved the problem.

Can you also check that there is an index in wp_vry4pg_top_ten_daily

This is where my ignorance of DB stuff comes into play. How do I check this?

Yeah, but none of that addresses the actual issue — 5.8.1 sites — no issues. 5.8.2 sites — problems. I have no objection making further optimization. But this is a situation where sometimes the site loads fine sometimes it does not. And waiting for pixel.wp.com is a WordPress thing. And it all started with my upgrading to 5.8.2.

Thank you for the testing. It could have been the memory issue, but does your site keep dying without the line?

Yes. After several experiments, I’d hit a certain number of activated plugins and then I’d get the whitescreen. The frontend was fine, so people visiting my site could still view pages, images, etc. But depending on the plugin, certain functionality might be gone.

However, once I added the memory line, suddenly, everything started working again. Obviously, adding the memory line meant that I started using more memory on the server, but I’ve got 3GB allocated to me, and I’m hitting ~2.25 after the new WP version vs. ~1.9GB I was using before.

Update. It was not Top-10. I’ve never had this massive of a failure of a WP update before. But I was reading up and decided to restart from scratch, keeping a copy of all my pugins in a backup directory. With no plugins, WP came back up and deactivated everything. The first thing I did was update Top-10, then activate it with no other plugin going. It works, so you are good.

Man, sometimes I think I may need to move off of WP just to run a simple blog.

Additional: Further research (’cause some other plugins started giving me grief upon reactivation) indicated that I needed to add this line to wp-config.php

> define( ‘WP_MEMORY_LIMIT’, ‘128M’ );

All plugins worked as normal.

• This reply was modified 3 years, 5 months ago by AstroNerdBoy.
• This reply was modified 3 years, 5 months ago by AstroNerdBoy.

I haven’t experienced that problem, but then I am using Duplicate Post version 3.2.2 plugin. So that may be negating my having to select “Classic Editor” every time.

It is still updating since the table was recreated. The recent update had no negative effect either. As such, I’m going to mark as resolved, even if the resolution wasn’t ideal. ??

If I click the wp_xxxxx_top_ten table link, a warning appears at the top of the page for the table.

Current selection does not contain a unique column. Grid edit, checkbox, Edit, Copy and Delete features are not available. Documentation

There’s no option for dropping the table. There is an option from the list of all tables.

I clicked that and the table is gone. Ooops. So I just deactivated and reactivated the plugin. That restored the table. Of course it was completely empty, but the table is now working. There are no longer warnings and there is a drop element as well.

To be honest, I think the table had become unusable. As I had mentioned before, there was no PRIMARY key when I previously looked in phpMyAdmin. And this table always generated warnings when looking at structure or anything else. So what I did may have been the only solution unless there was a way to add the key. But I think that was what you were having me attempt before, right?

In completely dropping the table, I lost total counts, but I was never going to have true total counts because (1) I installed this plugin quite some time after the blog started and (2) I had run a cleanup on the table (via the automated tools in the plugin) to trim it back. So I’m not going to worry about that.

That’s weird that it is coming up with an error for duplicate entry when I couldn’t drop the PRIMARY key since it supposedly didn’t exist. (But then my SQL knowledge is limited to having a vague understanding of what the commands you gave me are doing within the database.)