YARPP does not allow relatedness options for InnoDB in MySQL 5.6

  • I am using the latest YARPP (4.2.2) on the latest WordPress (4.1)

    I was trying to set up YARPP, trying to setup “Relatedness Options” for “Titles” and “Bodies”. However, I was unable to change the optoins to be something other than “do not consider”.

    After further reading, it turned out that I must change my table to MyIsam. However, in MySQL 5.6+, InnoDB allows full text search, and therefore YARPP should work with it. Can you fix this?

    https://www.ads-software.com/plugins/yet-another-related-posts-plugin/

Viewing 8 replies - 1 through 8 (of 8 total)

  • Encountered the same on after migrating to a new server. I think the MyISAM restriction should be removed.

    Update 1: turns out that by pressing “Create fulltext indexes” overrides the MyISAM restriction and tries to create the indexes either way.

    Thread Starter greeso

    (@greeso)

    @gennady Kovshenin

    Which button is that? Where is the “Create fulltext indexes” button? Can you please elaborate?

    Oi, bom dia!

    Estou tendo este mesmo erro, mas n?o sei consertar. é necessário?
    Se sim, como fazer por favor?

    Jonathan

    @greeso That text (and button) only seem to show up immediately after (re)install. It’s at the top of the /wp-admin/options-general.php?page=yarpp page with a single line of blue text with a “+” to expand it.

    Thread Starter greeso

    (@greeso)

    @toddzebert

    Sorry, I am not sure what you are referring to, can you elaborate please? I could not find what you were talking about.

    I’m not sure how much different I can explain.

    On the /wp-admin/options-general.php?page=yarpp page, towards the top there’s an easy-to-miss single line of blue text with a warning about database/full text searches. It has a “+” button you can use to expand that to a whole paragraph plus the “Create fulltext indexes” button.

    BUT, it seems it ONLY shows IMMEDIATELY after a full (re)install of the plugin.

    So, if you don’t see it, disable and delete the module, then re-install and activate, then immediately go to the yarpp settings.

    Thread Starter greeso

    (@greeso)

    Thanks. It worked. This is a workaround, however it convert the wp_posts table to MYISAMM. I think I will do that for the time being, however I think this is not the right solution. A correct solution should keep the enging InnoDB, and be able to work with it because InnoDB does support full text indexes now.

    Thread Starter greeso

    (@greeso)

    I do not think converting to MyISAM is a good idea if you are using Amazon Web Services (AWS). Because if you use RDS to create a MySQL, then the backup service would not work. Amazon is moving away from MyISAM and supporting InnoDB. Their backup service works with InnoDB. So, if you want to take advantage of AWS, and I think backup is a necessary feature, then the solution above that converts the table from InnoDB to MyISAM is not good.

    Bottom line, please fix the plugin to support InnoDB.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘YARPP does not allow relatedness options for InnoDB in MySQL 5.6’ is closed to new replies.