#1214 – The used table type doesn't support FULLTEXT indexes

Support has been upgraded!



The Support Forum is closed. Not to worry!  Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.

Premium Support

Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?

Please open a Support Ticket in your user account.

Click here to open a support ticket.

Free Support

Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.

Please open a new support topic in the WordPress support forums for Connections.

Click here to open a support topic.

This topic is: resolved

Tagged: , , ,

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • 04/25/2015 at 9:54 am #332427
    Serge Teweuchi
    Participant

    Hello I got this other problem !

    I was trying to move my website from WAMP to my staging url. However, when I went to import the SQL document to phpMyAdmin, it couldn’t import the Connections tables. This is the error I received:

    <h1>1214 – The used table type doesn’t support FULLTEXT indexes</h1>

    Is there something I’m doing wrong or is there no way to import the connections files from my localhost/WAMP?

    Thanks for your help !

    Attachments:
    You must be logged in to view attached files.
    04/25/2015 at 10:50 am #332431
    Steven Zahm
    Keymaster

    @ Serge

    re: Is there something I’m doing wrong or is there no way to import the connections files from my localhost/WAMP?

    The default table engine in your WAMP install supported FULLTEXT and the default table engine that your web host provides does not. Likely the web host running an older version of MySQL.

    What you likely need to do is make sure the tables are set to MyISAM before you import.

    Alternatively, on your WAMP install, disable the FULLTEXT search on the Connections : Settings admin page under the Search tab. Then export again. You should be able to do the import now because the FULLTEXT indices will not exist.

    Hope that helps!

    04/25/2015 at 11:13 am #332433
    Serge Teweuchi
    Participant

    I follow the proposed solution but same error msg…

    Is there any option to reset de system?

    Or am I constraint to delete all the datas in intered in connections?

    Thanks

    04/25/2015 at 11:47 am #332434
    Steven Zahm
    Keymaster

    @ Serge

    Sorry, it seems the FULLTEXT indexes are not dropped when disabling that option on the Connections : Settings. That is a bug. I just fixed it.

    The first solution should work just fine though.

    Another way to deal with this is to open the SQL files you exported and remove the lines that begin with FULLTEXT KEY search. There should be three instances if you exported all tables as a single export. If you exported the tables as individual SQL files then there will only be one instance in three of the connections table SQL files. Make sure to also delete the trailing , from the previous line otherwise you will end up with an invalid SQL statement.

    04/25/2015 at 12:07 pm #332435
    Serge Teweuchi
    Participant

    I where still having the same error and I proceed by deleting the three lines but end up with an invalid SQL statement

    Here is attached the test file.

    Thanks

    04/25/2015 at 12:12 pm #332436
    Serge Teweuchi
    Participant

    Here it is

    Attachments:
    You must be logged in to view attached files.
    04/26/2015 at 7:45 am #332532
    Steven Zahm
    Keymaster

    @ Serge

    Looking at the SQL file…

    The source DB on WAMP, the table engine in InnoDB which only supported FULLTEXT starting in MySQL 5.6. The host is likely on an older version.

    On you WAMP install, drop the FULLTEXT indexes manually in phpMyAdmin on the following tables:

    • wpeig_connections
    • wpeig_connections_address
    • wpeig_connections_phone

    OR

    Like I said before, manually edit the SQL file to remove the lines that begin with:

    FULLTEXT KEY search

    They are still in the sample file you attached.

    Also, as mentioned, make sure to also delete the trailing , from the previous line otherwise you will end up with an invalid SQL statement.

    04/26/2015 at 9:48 am #332537
    Serge Teweuchi
    Participant

    Ok this is solved.
    Thx

    04/26/2015 at 12:45 pm #332549
    Steven Zahm
    Keymaster

    @ Serge

    Great to hear!

  • Author
    Posts
Viewing 9 posts - 1 through 9 (of 9 total)

You cannot reply to this support topic. Please open your own support topic.