Site Package Import Stuck at 100%

Avatar
Leonardus
Follow

You can try to install and activate this extra plugin before importing Covid-19 site package:
https://import.wp-migration.com/all-in-one-wp-migration-file-extension.zip

The "stuck at 100" during importing is a common problem with many migration plugin, usually due to low PHP limit, or the add one above wasn't installed..

If the addon has been installed then the only thing which cause the upload still stuck, is the hosting PHP limit low preferences.

If you can increase the limit of these 4 PHP settings:

max_execution_time
upload_max_filesize
post_max_size
memory_limit

To increase the limit:
- Login to cPanel
- Find the "Select PHP Version" menu: https://prnt.sc/r5q9a8
- Click the Swith to PHP Options button: https://prnt.sc/r63kqo
- Then there will be an options to adjust/increase those 3 settings above

Recommended VALUE:

c19-value3.png

PS. If you have the Cloud4WP hosting on us recently, you don't need to do anything. Those higher PHP value is already set by default.

 

Have more questions? Submit a request

6 Comments

Date Votes
  • 0
    Avatar
    Prasun

    max_execution_time-600
    upload_max_filesize-64
    post_max_size-128

    memory limit is -512

    these are the figures in my cPanel I think its ok, but if it still not solved I will come back again

  • 0
    Avatar
    Prasun

    It's not going through, I have tried please suggest how to install the package

  • 0
    Avatar
    Viju Rao

    Hi Leonardus for me it struck 35.99% after that it is showing unable to upload. I raise the support ticket but there is no reply, Could you please check? I agree that the current situation of all world is not good. (Covid-19). But If you clear our problem might give you good sales.

     

  • 0
    Avatar
    Viju Rao

    Hi @prasun is your problem solved? could if yes could you help me?

  • 0
    Avatar
    Viju Rao

    My problem is resolved thanks I just changed the values according to the above one.

  • 0
    Avatar
    Leonardus

    The fix already explained above.

     

     

Please sign in to leave a comment.
Powered by Zendesk