• Resolved yavuzyayla

    (@yavuzyayla)


    I’m trying to restore a 6.5 GB big archive but at the user import step I’m getting a runtime error. Lot of plugins got restored and such but it fails at the end.

    What should I do?

    View post on imgur.com

    A few minutes after this step.

    • This topic was modified 2 years, 3 months ago by yavuzyayla.
    • This topic was modified 2 years, 3 months ago by yavuzyayla.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Hi Yavuzyayla,
    Thanks for using Prime Mover! What’s the runtime error? Can you please send the runtime error log details via our official contact form.

    Usually at user import step – the primary cause of runtime error is illegal offset type – if you are getting similar errors like this and you are using PHP 8.0 – try downgrading to PHP 7.4 and see if it helps.

    If you already tried the workaround and you still have issues – can you provide us a link to download the WPRIME package (you can share in Gdrive) – we will try to check if the runtime error is reproducible in our test server.

    Please send the link via our contact form. This way we will know if the error is server or package-related. Thanks!

    Thread Starter yavuzyayla

    (@yavuzyayla)

    Hey Emerson, thank you for anwsering.

    I’m actually on 7.4.

    View post on imgur.com

    I’m sending you the details over the support forum.

    Thread Starter yavuzyayla

    (@yavuzyayla)

    Just send you a zip file containing error log Emmerson.

    Thanks again.

    Plugin Author Codexonics

    (@codexonics)

    Hello Yavuzyayla,

    Thanks for the log! We’ve checked the log and you are getting out of memory runtime errors. This is usually caused by a large imported user data that exceeds your current WP memory limit: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes)

    Can you please raise your memory limit in the target site wp-config.php? Let’s try increasing this to somewhere 256M to 512M to see if your server can handle it.

    define("WP_MEMORY_LIMIT", "256M");
    define("WP_MAX_MEMORY_LIMIT", "512M");

    Once the memory limit is raised – please try the restore again to see if it outputs the same error. If you still get memory errors – try raising the memory limit to somewhere 1GB:

    define("WP_MEMORY_LIMIT", "512M");
    define("WP_MAX_MEMORY_LIMIT", "1024M");

    Once the site is restored – you can re-adjust the memory limit to something sensible during it’s operation.

    If the issue does not fix with any memory limit adjustments – please share the link to download WPRIME package (e.g. in Gdrive or DropBox) via our contact form – we will diagnose this package and see why it requires this much memory requirements. Thanks again and let me know how it goes.

    Cheers,
    Emerson

    • This reply was modified 2 years, 3 months ago by Codexonics.
    Thread Starter yavuzyayla

    (@yavuzyayla)

    Indeed that worked Emerson, have successfully migrated the site, thank you.

    Plugin Author Codexonics

    (@codexonics)

    Hi Yavuzyayla, that’s great to hear 🙂 Thanks for the update.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Runtime Error On Installation’ is closed to new replies.