Need more information about “Table data type issue on export/import” 6.8.8

  • Resolved ronherren

    (@ronherren)


    6 years ago

    Sorry to ask in the support forum, but I couldn’t find any details about the issue in ai1wm-6.8.8, “Table data type issue on export/import.”

    I completed an import last night(20190331) using ai1wm-6.8.7, and encountered a 404 when I clicked on the link to save the permalink settings twice. Not until I saved the permalinks again this morning and purged all caches via W3TC did the permalinks get correctly refreshed and all pages appear correctly.

    I had recently installed the Autoptimize plugin along with its’ CriticalCSS powerup extension, and also have W3TC running. This was the first export/import from our DS to our PS (dev server to production server) since installing Autoptimize + powerup on both servers; so I suspected it may be a caching issue. However, the Table Data Type issue fixed in ai1wm-6.8.8 concerns me.

    Could you please point me to any additional information I could use to determine if I need to backout and try again with newer version of All-in-One WP Migration (ai1wm-6.8.9)??? What types of potential issues do I need to worry about? Database table data type issues?! YIKES!

    • This topic was modified 6 years ago by ronherren.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Yani

    (@yaniiliev)

    It is an issue that has been reported to us recently. It is a very rare situation (corner case). It affects varchar type columns in the database that have leading zeros. On import, the leading zeros will be removed. If you import/restore with the most recent version, it corrects this defect.
    Example:
    Exported Data: 0123456789
    Imported Data: 123456789

    Numbers are usually not stored as varchar datatype with leading zeros.

    Thread Starter ronherren

    (@ronherren)

    Ah, thank you for your immediate reply Yani! Yep, it’s affected us. We have zip codes that have leading zeroes in Massachusetts, Connecticut, etc., and they’re affected. Although, I’m not sure why some uses of the exact same variable retained the leading zero while another use lost the leading zero, on the same page for the same value no less!

    I’ll let you know how the restoral works out… just planning to update the plugin and reimport same file I imported last night.

    Thanks again!
    Ron

    Optimizing Matters

    (@optimizingmatters)

    small late-to-the-party clarification; Autoptimize (and the power-up) do not do page caching, only front-end JS and CSS optimization ??

    frank (ao dev)

    Thread Starter ronherren

    (@ronherren)

    @optimizingmatters, I understand Frank, I should have been more specific; that I suspected a conflict with W3 Total Cache and Autoptimize… which may have caused a caching issue. When the permalink URL 404’d, I visited it via “Settings->Permalinks” in another tab I had open; then saved twice… but it must not have completed correctly for some reason… (a caching issue? Who knows.)

    Anyway, I just finished reimporting after updating to ai1wm-6.8.9, and this time I didn’t encounter anything unusual; however, the leading zeroes that had been removed from the ACF zip code field were still missing – so I edited those pages to add the zeroes back into those field values.

    Thank you all,
    Ron

    Optimizing Matters

    (@optimizingmatters)

    w3tc is another thing indeed; that one does do page caching ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Need more information about “Table data type issue on export/import” 6.8.8’ is closed to new replies.