Tried it without HTTPS at all and still froze adding UTF data.
Next step is to try it on a different server. I'm continuing to suspect it's an issue with 1&1. They lock down a number of things that I have found irritating to get around (like no remote MYSQL access so I can only work with the database through their myphpadmin portal).
Ok, I tried running pretty much the exact same install on a different server (BlueHost) this time and the database step ran in a matter of seconds with no problem. So, I think that means I will need to ask the client to put in a support ticket with 1&1. Is there anything I would want to advise him to ask them to look at?
The ironic thing here is that 1&1 is basically forcing him to upgrade to ZC 1.5.5 because of their forced upgrade to php7 in May. But if some setting on their server is tripping this up and preventing him from doing this upgrade then they're planning to charge him extra money for staying on php 5.x![]()