GUI All-in-One WP Migration vs wp-cli ai1wm backup/restore

  • Resolved svorobyov

    (@svorobyov)


    6 years, 7 months ago

    Greetings!

    I am experiencing problems with a WP site migration when using wp-cli and ai1wm:

    1. while the GUI version of the All-in-One WP Migration plugin works correctly,

    2. its command-line analog with
    wp ai1wm backup
    and a subsequent
    wp ai1wm restore
    produces a broken (almost correct, but flawed in some random places) target web site.

    3. I checked the resulting *.wpress files produced by the GUI version of the All-in-One WP Migration Export-to-file with the wp ai1wm backup outcome. The *only* difference is the database.sql file (extracted from *.wpress files using wpress-extractor) with apparently *minor* differences in some transient values.

    4. My CLI restore on the target looks like as recommended:
    wp ai1wm restore <.wpress backup file>
    wp rewrite flush
    wp rewrite flush
    (the last two commands are “recommended” for permalinks)

    I am out of ideas. Maybe
    wp ai1wm backup
    should be preceded by some cache save/cleanup commands?

    Many thanks for any pointers!

    PS: both source and target are latest Amazon Linux instances with the same versions of WordPress, Plugins, PHP, and Apache

    • This topic was modified 6 years, 7 months ago by svorobyov.
Viewing 1 replies (of 1 total)

  • Hello,
    Thank you for your question.
    In order to be able to solve the issue, we will have to look into it more closely.
    Can you please contact us to [email protected] and provide us with a .wpress backup that contains the unexpected changes in database.sql file as well as the backup that is correct.

    Thank you in advance
    Anna

    • This reply was modified 6 years, 7 months ago by annaangelova.
Viewing 1 replies (of 1 total)
  • The topic ‘GUI All-in-One WP Migration vs wp-cli ai1wm backup/restore’ is closed to new replies.