MailPoet plugin’s tables are not using the InnoDB engine

Same here, message came up when updating from MP 4 to MP 5. The refered kind helps although manually changing the types manually for 25 + tables is not really convenient, especially for rather none technical MP users.

Also a little more information to this about the “performance and compatibility issues” would be nice and how it related to MP 5 update.

I have exactly the same message and am a little worried that sending newsletters will no longer work smoothly.

This situation is very stressful for me. I absolutely have to publish the next newsletter and I really don’t have time to carry out these measures on the database beforehand.

Sabiene

MailPoet obviously doesn’t want to offer a solution, so I solved the problem myself in the database. It doesn’t need so much time, but requires a certain understanding of the technology.

If you need more information, please feel free to contact me.

• This reply was modified 2 months, 3 weeks ago by Ulrich Kern.

FWIW, it’s easy to change a table to use the InnoDB storage engine. See https://kinsta.com/knowledgebase/convert-myisam-to-innodb/

I have updated all my Mailpoet tables to InnoDB, but when I access the newsletter I want to send, MailPoet is still giving me this message

Some of the MailPoet plugin’s tables are not using the InnoDB engine (“wp_mailpoet_custom_fields”, “wp_mailpoet_dynamic_segment_filters”, and 28 more). This may cause performance and compatibility issues. Please ensure all MailPoet tables are converted to use the InnoDB engine. For more information, check out this guide.

What do I do next?

• This reply was modified 2 months, 3 weeks ago by bluemoon2024.

I changed all my database tables from MyISAM to InnoDB.

Now I cannot see my subscriber list or my forms. The lists come up empty and I get this error message:

“An error has happened while performing a request, the server has responded with response code 200”

Trying to subscribe using my online form also produces an error along the lines of “There was an error.” Nothing useful. But when I check the database, the new subscriber has been added.

And emails are getting sent.

Due to time pressure I sent out my newsletter without changing the database first.
And it looks like everything is still working.

So what?

FYI. I had 41 tables in a Mailpoet installation, all of which, bar one, were set to MyISAM. I changed them all to InnoDB one by one using the phpmyadmin tool. When finished I logged into the site to check, and everything appeared to be fine. The warning message was still there, but this has a dismiss button rather than being automatically dismissed, so I dismissed the message and it hasn’t returned.

Tips:

1. When looking at the tables in phpmyadmin, use the filter at the top to find just the mailpoet tables (search for mailpoet).
2. There is a tick box on the left of each result. I ticked the first table, then held down the control key and clicked on the table name to open it in a new tab in my browser. I then changed the table engine by clicking on Operations at the top of that tables view. From there, you select the engine from the drop down list. With the done, don’t forget to click the GO button on lower right of that section of the options. You will know if it has succeeded as the window will change to show it. You can now close that tab, and return back to the main table and tick the next one, then ctrl + select to open that next table in a new tab.
3. Repeat step 2 until all tables have been done. Finally, I refreshed the tables page to check everything now shows InnoDB with no more references to MyISAM. That’s all I had to do. It was tedious, but done in 10 minutes. I haven’t yet sent any new newsletters, but everything looks to be fine.

Good luck.

I originally created this thread to make the plugin manufacturer aware that the users of the plugin should be better informed and not presented with a fait accompli.

For me it is no problem to work in the database, but I assume that many users have no experience with databases and do not make the necessary adjustments out of fear.

If you need help, please feel free to contact me at any time.

Hi @640521-1,

Thanks for bringing this to our attention. Just so we can reproduce the original error (and make sure it’s cleared by any changes we make), can you confirm where the original innoDB warning came from? If it’s still happening, a screenshot would be great.

Thank you!

I ended up restoring backups of my database and files prior to the upgrade to MP 5.1 or to the change from MyISAM to InnoDB. That was necessary in order to get things working again. I’m not uneasy about installing MP 5.1, so I’m sticking with 5.0.2 until I hear that everything is resolved.

Hi everyone,

Wrapping up this thread with some clarifications.

First, while we strongly recommend moving your database tables to InnoDB for performance reasons, it is not a strict requirement for MailPoet to function. While you may experience slow sending issues if you continue to use MyISAM, this will not block sending altogether. For now, at least, MyISAM is still supported although if you reach out to us with delivery issues, we may recommend converting to InnoDB.

More on that here:
https://kb.mailpoet.com/article/200-solving-database-connection-issues

If you wish to convert your database tables to InnoDB as per our recommendation, *always* take a full database backup first.

Then, you can convert either directly via phpMyAdmin on your hosting account, instructions here:
https://kb.mailpoet.com/article/200-solving-database-connection-issues

Or reach out to your web host or an experienced WordPress developer for assistance.

Hi @lynnjat7,

thank you for your answer. ??

But i have to agree with @640521-1:

It is only possible for a small group of users of your plugin to make changes in a database.
This is the reason why WordPress and plugin providers exist at all.

CMS systems are made to avoid such requirements as changes to a database.

Personally, I can manage this somehow, but I expect a little more customer service from a renowned company like MailPoet. Especially as I use the premium version for all my WP sites with MailPoet and also the sending service.

You wrote that it is not necessary to make these changes, but that doesn’t fix the small problem, does it?

Hey @volmering.

It is only possible for a small group of users of your plugin to make changes in a database.
This is the reason why WordPress and plugin providers exist at all.

Thanks for sharing your feedback. I agree, and most times, database changes are not needed for plugins to work. However, that’s sometimes necessary, given the variety of hosting configurations and plugins functionalities. When it does, and our users don’t have the technical knowledge to do it themselves, we recommend asking for host support, as they can usually assist with changes like this.

Personally, I can manage this somehow, but I expect a little more customer service from a renowned company like MailPoet. Especially as I use the premium version for all my WP sites with MailPoet and also the sending service.

Note that if you have a premium MailPoet plan you can get priority support.

You wrote that it is not necessary to make these changes, but that doesn’t fix the small problem, does it?

For users that are experiencing performance issues while using MyISAM, then yes, the issue wouldn’t be fully solved without the database change. However, as my colleague noted, this won’t keep things from working, it would only slow down the sending process.