Tagged: Migrate DB Pro FontAwesome
April 14, 2018 at 12:49 am #36713callmesbMember
WP Google Maps Pro was working wonderfully on both local and remote sites until upgrade to v.7.0 Now, when I push my DB using Migrate DB Pro, I get the following error:
The “wp_gmza” table contains characters which are invalid in the target database.
Migrate DB Pro support says, essentially, that it could be due to features that use extended character sets (font awesome?): https://deliciousbrains.com/wp-migrate-db-pro/doc/invalid-text/
I updated to v.7.0.01 on both local and remote sites, but the error persists.
Thoughts?April 16, 2018 at 8:25 am #36736PerryModerator
Thanks for getting in touch and thank you for reporting this,
Version 7 uses MySQLs spatial types to store marker coordinates (as opposed to text) for performance reasons, this is stored as binary data which isn’t human readable and which in most cases produces invalid UTF-8 text if it’s not converted to text.
I’ve looked into their documentation on how to convert this programatically and didn’t see anything mentioned there, I’ve e-mailed the plugin author to ask if there is anything we can hook into to get this working,
In the mean time please bear with us, is there an alternative plugin you could use whilst we get this solved?
– PerryApril 16, 2018 at 6:40 pm #36796callmesbMember
Thanks, Perry…are you asking if there is another migration plugin I can use, or another map plugin?
Side note: I also exported my map data from my local install as a .csv, then uploaded that csv into my remote install. This fixed the map and zoom, but my markers are still missing on the remote install.April 17, 2018 at 9:17 am #36822PerryModerator
If there’s another migration plugin you can use whilst we wait on their reply that would be great.
If there are any options within that plugin to exclude columns, please exclude wp_wpgmza.latlng
Does that help?
- You must be logged in to reply to this topic.