Support » Plugin: Wordbooker » SQL fixup fail

  • Resolved mippie32


    I noticed the fix/workaround included in the latest version probably doesnt work as this message keeps coming back. Not a real issue for me (as everything works now ;-)) But FYI

    Diag keeps giving this everytime

    Post Deletion 2013-02-09 11:31:33 SQL Fixup : Alter table wp_wordbooker_fb_friends ADD FULLTEXT INDEX name_idx (name); –
    Post Deletion 2013-02-09 11:31:33 SQL Fixup Fail : The used table type doesn’t support FULLTEXT indexes –

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Steve


    You’ve got your default DB table type set to INNODB at a guess and INNODB doesn’t support fulltext indexes.

    OK. And yes, thats correct.
    I altered the wordbooker tables.

    ALTER TABLE wp_wordbooker_errorlogs ENGINE=MyISAM;
    ALTER TABLE wp_wordbooker_fb_friends ENGINE=MyISAM;
    ALTER TABLE wp_wordbooker_fb_friend_lists ENGINE=MyISAM;
    ALTER TABLE wp_wordbooker_postcomments ENGINE=MyISAM;
    ALTER TABLE wp_wordbooker_postlogs ENGINE=MyISAM;
    ALTER TABLE wp_wordbooker_process_queue ENGINE=MyISAM;
    ALTER TABLE wp_wordbooker_userdata ENGINE=MyISAM;
    ALTER TABLE wp_wordbooker_userstatus ENGINE=MyISAM;

    But it is a little funny I think, isnt it common to use the innodb as engine for WP tables? ( ) ==> When I google around I only see people switching to innodb as engine?

    Anyway, it worked out, thanks.

    Plugin Author Steve


    The only table that needs to be MyISAM is the friends list. The rest of them can be InnoDB so I’ve changed the table create script to specifically state it for that table and the fix up code now checks for storage on tables and will usually leave them alone.

    I suspect most people on single blogs wont notice the differences between the two normally.

    Great 🙂

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘SQL fixup fail’ is closed to new replies.