Chris

I can access the site normally with an ftp client, and WordPress seems to connect ok too – if I change the setup to use the wrong password, I get a different error. It just can’t do anything once it’s connected.

Here’s what the dialog looks like: https://imgur.com/a/or0Cnqz

• This reply was modified 2 years, 11 months ago by Chris.

The problem seems to have resolved itself. Not sure if it’s thanks to your full sync, or my having applied an actual update to a plugin that popped up with a new version this weekend, or just time passing. But now all my sites are showing up as up-to-date, so I’m happy.

Marking as fixed.

https://www.hughtempleton.co.uk/

I’ve done a bit more digging, and it looks like the old version was using Shutter Reloaded instead of Fancybox – but it still has the same issue. It used to say

Title-in-bold (description)

Now it just says

decription

See https://web.archive.org/web/20161108202000/https://www.aliquart.co.uk/gallery for the old look.

I’ll fill in a bug report as requested.

I’m seeing the same issue on my blog after upgrading to 3.2 – all posts are only linking to themselves with a score of 0.

Anybody?

I’ve done a bit of debugging, by digging around in the yarpp_myisam_check() function in includes.php.

The function reads the posts table’s status into $table OK, but $table->Engine returns a NULL. Maybe it’s a MySQL issue? If so, perhaps the plugin should say something like “I can’t determine the engine you’re using, make sure it’s MyISAM if you want to use post contents/titles”

Anyway, to answer my previous question – yes there is a way to disable this check.

If you’re getting this message, and you’re SURE your table actually IS running on MyISAM, then here’s a fast-and-dirty fix:

You need to edit the file includes.php in the YARPP plugin’s directory. Go down to line 89 which should read

function yarpp_myisam_check() {

Immediately after this line, add a new one saying

return 1;

This will make the function return true regardless of what MySQL might (not) say. Hopefully this issue will be fixed properly in a new release…

I’m getting the same problem too – WP 2.6.3, plugin 2.1 . Is there any way I can hamstring the “check for MyISAM” bit so it keeps working regardless?