Client does not support authentication protocol requested by server; consider upgrading MySQL client
and as usual the support site is down aswell
I'm not sure about this but I think they've upgraded SV5 from PHP4 to PHP5 as part of the "fix" for all of the issues they've had.
This has caused database errors for me to. I've just moved one site to another host and had to find out for myself what the differences were between PHP4 and PHP5 to get my site working again.
Like I say - I'm not sure about this but am quite confident that this is what's lost me a lot of money over the past couple of days.
Not sure what SV5 is, but moving from PHP4 to PHP5 is a big headache sometimes especially if you have scripts that use lots of memory as it's much better at spotting what you're using and stopping your script.
Also watch out for things like include("http:...") not working (needs tweaking in their server setttings).
Doesn't sound like they're really fixing things, just more breaking everything and trying something random to fix it. Glad I'm not with them.
- One being that by default URLs won't work in them anymore unless you tweak one setting (paths are unaffected)
- The other being the include() vs include_once() especially if the included file contains a function as it'll come back as function already declared.
It's also much better at counting memory usage which has caused all kinds of problems since the default amount isn't that brilliantly high and even 30MB per script which sounds a lot, isn't actually that much when loading CSV's.
Preg_match() and preg_replace() seem to have bizare problems whereby they just don't work if there's too much data. Found lots of people complaining about it, but no one seemed to know where the memory limits for those were. Preg_match_all() seems to have a much higher limit incase anyone runs into this problem.
Linear Mode
