Plugin Author
Ajay
(@ajay)
Hi, the plugin “modifies” the wp_posts table to convert it to myISAM if you’re using mySQL version less than 5.6 or InnoDB for post 5.6. The reason being, as you said above, is the support for fulltext.
However, it either case, I’m surprised that the database cannot be exported.
Are you using https://en-gb.ww.wp.xz.cn/plugins/updraftplus/ ? I haven’t used them before. I normally backup by database using cPanel itself and not with any plugin.
Do you mind pasting me the exact reply you got from UpdraftPlus support?
Database export was fine.
Actually I try with other most popular plugins too like WP Migrate DB, All-in-one WP Migration, all fail.
The full message from UpdraftPlus below :
Thank you. The error message and log indicate that on your destination webserver, the InnoDB engine does not support full text indexes, but that your source WordPress database uses these.
From Googling, it looks like the plugin “Contextual Related Posts” has adjusted the “posts” table in the WP database, to use this feature on the source site. It might be best to ask them for guidance on the exact requirements, when migrating to a new site, to make sure that the destination MySQL server is compatible.
The log is here : https://www.dropbox.com/s/5dudexvzz2hhk2g/log.9b8f786be000.txt?dl=0
Only problem when import. No matter manual or plugins. It must be problem with mysql like you said.
Plugin Author
Ajay
(@ajay)
The log helps. But, I think the clash could be because of the different mySQL versions.
What’s the mySQL version of your source server? Is it greater than v5.6? If so, that would explain why you have a FULLTEXT index there.
And, is the destination is less than v5.6?
What I am trying to get at is, does the source use an InnoDB or a myISAM table format? And, what is the destination be.
Ideally this should both be the same and then that would in theory work. The updraftplus plugin is failing because it’s running a mySQL query to create a FULLTEXT index on the InnoDB which is failing.
Source server is MySQL 5.6.24
Destination server is MySQL 5.5.49
Plugin Author
Ajay
(@ajay)
Hi, that is the issue. The source supports fulltext for innoDB and the destination doesn’t.
As you mentioned, one option was to disable and delete the plugin. The other option would be to convert the source table to myISAM.
The last and preferably alternative is to have the same version on your destination server
Yes I did that. Uninstall before migrate and install it later on the destination.
Suggestion. This plugin should have Export/Import as it has many settings options and we would like to use the same settings for anothers. I think it could be very useful if you put add this option. 😉
By the way. Thank you very much for your kindness and my all time favorite plugin!
Plugin Author
Ajay
(@ajay)
Hi, that is one of the options that I plan to add in a pro / addon feature
Really that is great idea. Please add more templates for the pro/addon too. I will looking forward for it.
Thanks a lots.
Plugin Author
Ajay
(@ajay)
Thanks for confirming. It’s good to hear that there is a market for the pro. The templates are also one of the things I plan to add into a pro version.
