Hi almendron,
I have seen that issue once before, but its with really large DB files. Right now the routine uses file_put_contents, but there are some other techniques we might be able to use to work with larger databases. I have added this item to our work queue to look into improving.
In the meantime you may have to up your values a bit more, I would double them, I have found that the memory_limit setting doesn’t always correlate I believe the amount that it shows you in tried to allocate xxxx bytes is the amount over and above the memory limit in PHP. Also another process you can try is before you build the DB is run a plugin like wp-optimize.
Cheers~
1.- Wampserver: change version of PHP from 5.6.19 to 7.0.4
2.- Default values PHP.INI: memory_limit (128M), post_max_size (8M), upload_max_filesize (2M),….
3. phpmyadmin.conf:
php_admin_value upload_max_filesize 700M
php_admin_value post_max_size 750M
php_admin_value max_execution_time 5000
php_admin_value max_input_time -1
And all perfect except an error
**ERROR** database error write ‘Incorrect string value: ‘\xF0\x9F\x98\x89″ …’ for ...., pero esto es debido a problemas con el juego de caracteres.
Solution: edit file “my.ini” and add to the section [mysqld] the following line:
sql_mode = NO_ENGINE_SUBSTITUTION
Finally .. I guess there will be an explanation and I guess not so much related to the values of PHP.INI as the “file_put_contents” command.
The NO_ENGINE_SUBSTITUTION fix we haven’t really found a way to at this point to fix via code, but the other issue you had with the size problem we believe we may be able to enhance some to not require as much memory… Thanks for posting your solution and reading the other threads…
I’m happy to help,
regards
Closing down topic thread…
Cheer~
