Table prefix issue

  • Resolved juansandro

    (@juansandro)


    1 week ago

    For some reason, it seems that Fluent Form has trouble installing on a website where the table prefix in the database has been changed. In other words, it’s not the default wp_ prefix — for example, it’s skhw_ instead. The plugin installs, but it never fully creates all the necessary tables required for proper functionality.

    I read somewhere that this could be the cause of the problem.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Amimul Ihsan

    (@amimulihsanmahdi)

    1 week ago

    Hello @juansandro,

    Thanks for reaching out. A custom database prefix can sometimes cause this type of issue.

    To help me troubleshoot, could you please provide:

    1. A list of the Fluent Form tables that failed to create.
    2. Your database engine name(e.g., InnoDB or MyISAM).
    3. Any relevant errors from your PHP or WordPress debug logs.

    In the meantime, please try deactivating and then reactivating the plugin. This often forces the tables to be created correctly.

    Thank you

    Thread Starter juansandro

    (@juansandro)

    5 days, 17 hours ago

    To asnwer your questions:

    1. Only one table was created
    2. MyISAM
    3. There was a lot of errors

    ….reinstalling, deactivating, then activatating did not help.

    However, in the mean time, what I did is imported all the tables from another installation, and installed the plugin again….and it worked.

    Thank you! Done.

    Plugin Support Amimul Ihsan

    (@amimulihsanmahdi)

    4 days, 6 hours ago

    Hello @juansandro,

    Thank you so much for the detailed follow-up and for sharing your solution. I’m glad to hear you were able to get it working!

    Your information was very insightful and helped us confirm the root cause. The problem wasn’t the custom table prefix as initially suspected, but rather the MyISAM database engine your site is using.

    Fluent Forms, like many modern WordPress plugins, is designed to work with the InnoDB engine because it supports more advanced features like foreign keys and transactions. The limitations of MyISAM are why the process failed after creating the first table.

    While your manual import was a clever workaround, we highly recommend converting your database tables from MyISAM to InnoDB for better long-term stability and compatibility. This is the standard for modern WordPress sites and will prevent similar issues with other plugins in the future.

    Thanks again for bringing this to our attention. Please feel free to reach out if you have any other questions!

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

You must be logged in to reply to this topic.