Support » Fixing WordPress » Apparent phpMyAdmin file size issue

  • I develop my site locally using MAMP. Yesterday after updating to WordPress 3.1.3 and updating my plugins, I backed up my remote site’s database then I dropped the remote site’s tables so I could import the updated tables from my development site. The difference in sql file sizes between the old and the new were very small (7.7mb – 7.8Mb). But phpMyAdmin displays this message:

    “No data was received to import. Either no file name was submitted, or the file size exceeded the maximum size permitted by your PHP configuration. See FAQ 1.16.”

    I tried to replace the old sql file from my recent backup but it won’t import either. Not sure why it let me do it a month ago but not now because I don’t edit my site on the remote server. So that .sql file was that size when it was imported.

    I called my hosting company and they instructed me to increase the maximum file size in my php.ini file. They also recommended I change the file name to php5.ini. Even though it makes no sense, I did everu thing they recommended. My php5.ini file now reads like this:

    register_globals = off
    allow_url_fopen = off

    expose_php = Off
    max_input_time = 60
    variables_order = “EGPCS”
    extension_dir = ./
    upload_tmp_dir = /tmp
    precision = 12
    SMTP =
    url_rewriter.tags = “a=href,area=href,frame=src,input=src,form=,fieldset=”

    upload_max_filesize = 64M

    The last line, “upload_max_filesize” is the only edit.

    It isn’t working but GoDaddy claims I must wait 24 hours so the server has a chance to update. I have two suspicions:

    1. That this isn’t enough and there is something else I need to also do.
    2. That all my WordPress sites will need me to do this because sooner or later databases get bigger.

    Any recommendations? Is there anything I need to update within the WordPress files to help with this phpMyAdmin issue? Is this entirely a phpMyAdmin issue?

Viewing 3 replies - 1 through 3 (of 3 total)
  • @pcgs51

    I’m battling the same issue on GoDaddy with a WordPress site where I’m unable to import a SQL backup file.

    I also changed my PHP5.ini file to allow larger max_filesize and memory etc. but no immediate cure. I’m encouraged by your comment that you must wait up to 24 hours for the server to pick up the ini change. Perhaps this will work tomorrow?

    I recall having this problem a year or so ago with another site, and vaguely remember also having to increase parameters in a wp_config.php file as well, so I’ll look that up too.

    I’ll post back if I get the import working.

    After three days of pain I discovered the problem and it will probably fluster you as badly as it did me.

    First they told me to edit the ini file and I did. Then they told me I had to wait 24 hours for the servers to update (I knew this was wrong but what could I do?)

    NO, it WILL NOT work tomorrow. What I finally did was call support and bite my tongue until it bled so I wouldn’t swear at them and got the support dude to stay on the line until they gave me a believable answer.

    Here it is: You used to be able to import .sql files over 2MB in size but no more. GoDaddy is now cutting off shared server accounts (one by one without notice) from this ability and while editing the .ini file will help with FTP uploads it will not help you with the phpMyAdmin database imports. You must either break up your import to smaller sizes (which I have no idea how) or learn how to upload your .sql file to the _db_backups directory and then do restore of your database. It actually works great. You can do this through the panel just before you enter phpMyAdmin where you see the list of available databases.

    Anyway, if you are a GoDaddy shared hosting customer, that is the scoop as of June 2011. I just saved you a couple of days of waiting because not all the support people know about this so you could waste a lot of time begging for help.



    I am SO very grateful for you advice, you DID save me a couple days.

    I’ve had no problem with imports on GoDaddy before so this was a real mystery to me, until you provided all the new clues.

    Take care!

    Jonathan from

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Apparent phpMyAdmin file size issue’ is closed to new replies.