Forums

Yet Another Related Posts Plugin
[resolved] The used table type doesn't support FULLTEXT indexes (9 posts)

  1. viktorix
    Member
    Posted 3 months ago #

    Below you'll see the error I'm getting. The site is hosted on Azure websites hosting (win server). Any help getting through this?

    -----------------------------------------------------------------------
    WordPress database error: [The used table type doesn't support FULLTEXT indexes]
    ALTER TABLE wp_posts ADD FULLTEXT yarpp_title ( post_title )

    WordPress database error: [The used table type doesn't support FULLTEXT indexes]
    ALTER TABLE wp_posts ADD FULLTEXT yarpp_content ( post_content )

    http://wordpress.org/extend/plugins/yet-another-related-posts-plugin/

  2. markfarrar
    Member
    Posted 3 months ago #

    I'm getting a similar error on a WP v3.5.1 blog hosted on HostGator:

    [22-Feb-2013 23:00:57] WordPress database error The used table type doesn't support FULLTEXT indexes for query ALTER TABLE wp_posts ADD FULLTEXT yarpp_content ( post_content ) made by require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/socrates/single.php'), the_content, apply_filters('the_content'), call_user_func_array, YARPP->the_content, YARPP->display_related, YARPP->enforce, YARPP->activate

  3. mitcho (Michael Yoshitaka Erlewine)
    Member
    Plugin Author

    Posted 2 months ago #

    @viktorix: thanks for bringing this up. I should do a better job checking for FULLTEXT index support before trying to add it... I'm unfortunately not sure how to do so... will have to read up a bit.

    In the mean time, YARPP will continue to work without those fulltext indices, but you will have to lower the "match threshold". Go to screen options > display "relatedness" options, then lower the match threshold to 1 or 2 and save.

    @markfarrar: do you know what kind of tables or databases your hosting uses? MySQL servers? MyISAM table type?

  4. viktorix
    Member
    Posted 2 months ago #

    Hey Michael,
    Thanks for quick reply. The problem is twofold. Those errors do not go away in the admin, and two - on the frontend right before the_content is being displayed it outputs a bunch of database variables and stuff. Is it possible to simply disable that feature to be able to use low relatedness feature?

  5. markfarrar
    Member
    Posted 2 months ago #

    Michael,

    The tables on my WP database for this site appear to be a mixture of InnoDB and MyISAM, with the single YARPP table being a MyISAM.

    Thanks,

    Mark

  6. mitcho (Michael Yoshitaka Erlewine)
    Member
    Plugin Author

    Posted 2 months ago #

    @markfarrar the question is what type of table wp_posts is. You want that one to be MyISAM.

    @viktorix I'm going to try to do some more testing to make this handling a bit better in a later version. Sorry about that.

  7. markfarrar
    Member
    Posted 2 months ago #

    Michael,

    It seems as though wp_posts is an InnoDB table.

    Can this be changes to MyISAM, or am I stuck with this problem?

    Thanks again,

    Mark

  8. mitcho (Michael Yoshitaka Erlewine)
    Member
    Plugin Author

    Posted 2 months ago #

    @markfarrar yes, you can change your wp_posts table to MyISAM and you'll be all set.

  9. markfarrar
    Member
    Posted 2 months ago #

    Michael,

    Thanks - that seems to have solved it.

    Best wishes,

    Mark

Reply

You must log in to post.

About this Plugin

About this Topic