Quentin Pain

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.

Everything Thomas Geiger says is correct. @trin – Your 1 star review is inappropriate, but I understand your annoyance. I felt like that when I first implemented GTM on a site manually (without using this excellent WordPress plugin) and got the same message. Google acknowledge this is almost always a false positive if you check the error in GTM – and they add that it’s not going to fixed anytime soon, as there’s usually nothing wrong.

Thank you.