Inglat NULL value causing migration problems

  • Resolved kwebdesign

    (@kwebdesign)


    4 years ago

    I’m using WP Migrate DB Pro to migrate between local and remote, but this issue is likely to cause problems with other migration tools as well.

    WP Migrate DB Pro fails to migrate WP Google Maps data, but handles everything else I’ve tried without a problem.
    Adding the following stops the migration failing, but the map data still doesn’t get migrated.
    define( ‘WPMDB_STRIP_INVALID_TEXT’, true );
    Thanks to some guidance from WP Migration DP Pro, I’ve discovered that replacing the NULL value in Inglat with the following, resolves the issue and the map data migrates successfully.
    POINT (0 0)

    Would you advise otherwise and would you consider placing a default value other than NULL into that column for future versions?

Viewing 2 replies - 1 through 2 (of 2 total)
  • stevendebeer

    (@stevendebeer)

    Hi there,

    Thank you so much for getting in touch, we really appreciate it.

    Could I kindly ask if you perhaps attempted making use of the Compatibility setting in Migrate DB via -> Migrate DB -> Settings -> Compatibility and checking any plugins that start with WP Google Maps and then clicking save?

    Kindly then perform the export and process the import as this should then allow any spatial data, which is how this specific data is stored, to be encoded on the export, and decoded on the import which should allow the import to work correctly.

    Kindest Regards,
    Steve

    Thread Starter kwebdesign

    (@kwebdesign)

    Hi Steve,

    That worked great… Many thanks for taking the time to help.

    Regards,

    Kirk

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Inglat NULL value causing migration problems’ is closed to new replies.