robzy

Yes, seems to be fixed! Thanks.

Had to uninstall and reinstall, perhaps because the version number hasn’t changed.

Yeah it looks like the theme I’m using assigns display: block to all img elements, and UCP is the only plug-in that uses an img element to display the icon; all others seem to use dashicons, a background image, etc. Great if you can hardcode that as an inline-block, a float, or something similar. Thanks!

Updated. Thanks for the quick fix!

Thanks, Bruce. I submitted a ticket: #7300095

I ran them as you posted them here, so the UPDATE first, followed immediately by the ALTER. But it’s possible that the ALTER still ran after the UPDATE failed because I ran them as one command (separated by semi-colon), I’m not sure.

Just updated the _terms table and everything seems to be working again.

Thanks for your assistance!

Thanks, Arnaud. The ALTER TABLE seems to have run OK (or had successfully run while updating), but the UPDATE query gets stuck:

Truncated incorrect DOUBLE value: ‘default’

A SELECT shows that those rows currently have a priority value of 0, so it probably gets hung up on that not being a float (or that ‘default’ cannot possibly be a value of a FLOAT field). It’s only 12 rows so I updated those manually.

That only affects posts, though. After clearing caches I still see a ‘default’ priority for about 2/3 of the URLs in the category sitemap.

Do I also need to update wp_aioseo_terms? Any other places?

• This reply was modified 1 year, 5 months ago by robzy.

Even after setting the priorities manually in the Advanced Settings, many URLs in the category sitemap are still assigned a priority of “default”. Which is weird, because why would some category URLs be assigned the manually set priority (0.8) and others “default”, when they ought to use the same setting?

<url>
<loc><![CDATA[https://www.example.com/A]]></loc>
<lastmod><![CDATA[2023-06-09T07:17:22+00:00]]></lastmod>
<changefreq><![CDATA[monthly]]></changefreq>
<priority><![CDATA[0.8]]></priority>
</url>
<url>
<loc><![CDATA[https://www.example.com/B]]></loc>
<lastmod><![CDATA[2023-05-30T12:46:38+00:00]]></lastmod>
<changefreq><![CDATA[monthly]]></changefreq>
<priority><![CDATA[default]]></priority>
</url>
<url>
<loc><![CDATA[https://www.example.com/C]]></loc>
<lastmod><![CDATA[2023-06-01T12:14:48+00:00]]></lastmod>
<changefreq><![CDATA[monthly]]></changefreq>
<priority><![CDATA[default]]></priority>
</url>
<url>
<loc><![CDATA[https://www.example.com/D]]></loc>
<lastmod><![CDATA[2023-06-09T10:04:44+00:00]]></lastmod>
<changefreq><![CDATA[monthly]]></changefreq>
<priority><![CDATA[0.8]]></priority>
</url>

This happens even after I ungroup the taxonomy priority score settings and set a value for each one of them individually.

• This reply was modified 1 year, 5 months ago by robzy.
• This reply was modified 1 year, 5 months ago by robzy.
• This reply was modified 1 year, 5 months ago by robzy.
• This reply was modified 1 year, 5 months ago by robzy.
• This reply was modified 1 year, 5 months ago by robzy.

OK, thanks @vmarko

So I’m afraid we won’t be able to create a new release version just for this

It’s not “just for this”, it’s also for those users like myself who’ve disabled the bad BackWPup 4.0 version and are waiting for an update to a newer version that will fix the issues without having to uninstall, reinstall and reconfigure.

Meanwhile, backups aren’t running and I’m considering switching to a different plugin because the way you’ve been handling this is quite bad.

@arnaudbroes Cheers, it’s working again. Thanks for the quick fix on a Sunday ??

@elgopa Good idea, thanks! Not ideal, but at least the sitemap works again.

Perhaps you can separate the database from the repository plug-in, but add the functionality, and have the user upload the database if they want to use it? Or would that still result in removal?

A “master switch” that toggles on/off GeoIP lookups across all ad slots might also be something to consider. That way, you won’t have to check all slots for GeoIP settings unless the user has actually chosen to enable GeoIP.

Wasn’t aware of that plug-in, thanks mbox99. I often use Blackfire.io myself.

With 30,000+ active installs, a 500ms delay per visitor is a lot of wasted time. I never knew WP Insert was doing this until the API stopped working; now that I’ve disabled it, the site is much more responsive. If you keep this in the plug-in, I’d recommend making it optional, disabling it by default, and including a warning regarding the performance hit.

(Especially because one of the “Features” of the WP Insert plug-in listed in its description is “Does not slow down your site”)

Right, you might as well comment out the function, too.

RAM usage is down by about a 1/3 for me (overall). This is PHP-FPM behind NGINX.