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 = relay-hosting.secureserver.net
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:
- That this isn’t enough and there is something else I need to also do.
- 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?
- The topic ‘Apparent phpMyAdmin file size issue’ is closed to new replies.