Hmm... I need to find out myself. I don't know what is the answer to that question. I'll do some research and get back to you if I find an useful answer. You should email the people at iPage as they probably can answer it..
WOW, quick reply. Thanks for the info, I'm sure it won't be too much hassle to get it running again (If the Host ever gets everything sorted.)..
The first error looks like your mysql username/password has changed, you should contact your ISP to get the new info (in the worst case scenario, they may have not moved your database over, if this is the case, I would demand them to move it over as they should NEVER move production servers without moving everything over)..
As for the other error, unsure... I had this same problem when my host moved because register globals was off. You could resolve this with either an htaccess turning register globals on (unsure, a search for htaccess register_globals on google should yield a result) or put.
In your configuration file..
Hope that helps...
Thanks for the advice James. I kinda worked out that they had changed my password. I've received an e-mail from the host informing me of my new FTP details and SQL passwords but unfortunately the FTP details are wrong. I'll give him to the end of the week to get everything completed (he's eventually getting around to installing DirectAdmin but won't be fiished until Friday) then I'll drop them another mail..
It looks like the easiest solution though is going to be a re-install or do you think this would be un-wise?..
Might be, depending on how many contributions you are using..
Our cart that was switched to a different server was heavily modified with 20 or so mods, as well as modifications made by myself to suit the client's tastes, so reinstalling was actually a bit harder than troubleshooting..
In our case, however, the Server 500 error was caused by register globals being off (and a malformed htaccess file)..
Thanks folks, like I say I'll give it to the weekend then I'll try sorting it out then. I'll let you know how I get on...
It may be something very simple indeed. Older servers frequently use the reference 'localhost' to connect to databases, where newer servers use '127.0.0.1'. If your iPage hosting company has either changed to new servers and a new operating system, or has simply upgraded the operating system on old servers e.g. RedHat Linux 9 to RedHat Enterprise Linux or RedHat Fedora then 'localhost' will have changed to '127.0.0.1' and you'll need to change these references in two files.
Try this and see what happens..
I'm quite a newbie to OSC but I think I've picked it up pretty quickly. I was working on my first OSC iPage site for a friend of mine and was almost finished modifing it (just had to secure it and find a way of linking it to a stock controll database I wrote some time ago) when the iPage hosting company moved to a new server..
Now when I goto the iPage site I get this....
Or when I goto admin directory I get this....
What's the best way to deal with this? Would I be better to fix it (I assume this requires only a few updates to a couple of files) or do a re-install of OSC and try to redo all of the changes I made?.
BTW: I do have several local back-ups of the iPage site so the latter may be pretty straightforward...
I can only suggest checking your configuration.php in catalog/languages and catalog/admin/languages..
I'm quite new to this aswell, but I would check there first..