Good at First

dual_alliance · #1 04-01-2007, 04:45 AM

I've been with Host Gator a month and a bit and l was really impressed with their service until my phpMyAdmin broke.

Ticket ID: KLO-785645

I emailed support, they emailed back quite fast, emailed back my password for cPanel.. after a while Level 3 Support reply saying they have fixed the problem.

Log into cPanel, go to phpMyAdmin and then l get the same error! I cant edit any rows in phpMyAdmin (which is rather annoying) so l emailed support back, and its been over 24 hours and if you add to when l first submitted the ticket its probably been about 32+ which is not good at all seeing as l need to be able to update the rows manually.

I'm now looking for a new host that can actually get the problem fixed the first time, without replying that the problem is fixed when it indeed isn't.

In the end, if your looking for a host and you rely on using phpMyAdmin dont go with hostgator.

Update: I received a reply after sending 2 more emails back and forth about they have reinstalled phpMyAdmin, go on it and its still not fixed get the same error.

***GatorBrent*** · #2 04-17-2007, 07:30 PM

Hi There,

I reviewed this ticket and didn't see any bad responses by our support.

What Tim Greer said to you looks to be exactly what the problem was.

" Perhaps importing the database via shell and bypassing the phpMyAdmin interface will remedy the problem? We could try that. If it doesn't help, you might consider having a script set up to execute the database query and not mess with phpMyAdmin to do it, if possible, since phpMyAdmin is an existing tool intended for a general usage and sometimes will not meet the desires or needs of some formats or functions. I'd assume that there are version differences between this install and the other host you used. Finally, you could always install your own phpMyAdmin scripts on your account and modify it as needed, or install the version that does work if it's a version issue."

Did this not solve your issue? I hope you understand this wasn't anything to do with us but looks to be a compatibility issue between the host you came from and us.