Support

I am trying to move a J1.5.15 site from IXW Hosting (Linux) to Go-Daddy Linux (Economy). I have backed up database and files using JP1.2.4 .jpa format (abt 26Mb) and tried to restore on Go-Daddy using KickStart 2.4.1.

I had set up a new database on Daddy and tested my connection through Go-Daddy's phpAdmin.

KickStart shows the in optional error message that Display Errors is On - I have not been able to find a way to turn this off even though I included display_errors = off in the php.ini file in the root directory.

On the Kickstart database details page I have tried several versions such as localhost and the full server address listed in phpAdmin, and also the short and long form db and db user names (taken from the phpAdmin screen). In all cases there are no explicit error message returned when I click on Next, but nothing is written to the database (according to phpAdmin) and there are no superadmin users showing the the dropdown on the next KickStart page.

Kickstart proceeds merrily to completion without reporting any errors. All the files seem to be in place as expected. But no database tables and :

1. The site and admin backend (viewed through GoDaddy's preview URL) both return error messages - firstly a 500 error (until I correct the next point) and then a database connection error.
2. The .htaccess file includes a few lines of IXW PHP version redirect code which when removed gets rid of the 500 error
3. The configuration.php file still includes references to the old database connection values - but even when I change these the same database connection error remains ( not surprising I guess if the database is empty...)

I am at my wit's end at present. I am new to Go-Daddy so may be missing something. Their phone support was not able to get me through this problem.

What might I be missing? Is there a workaround to upload the database directly?

GoDaddy is a little different on the database. They do not use "localhost", they use the server address. They do not prefix the database and user names with the host account name. The user name is always the same as the database name and they have to be unique (among the MySQL server or all of GoDaddy, I never figured out which).

Technically, kickstart has handed off to the JPI4 installer at that point, so it is the installer that is messing up. It should not go merrily on, it should stop with a "can't connect" error.

Yes, you can manually restore the database. It needs to be edited first to restore the table prefixes. There are some instructions for that in the Manual Restore documentation.

Thank you both for your replies.

Quick answers to Nicholas' questions. Yes JP2.4.1 - dyslexia as well, what hope is there for me? And the JPI4 installer shows no progress bar at the database stage.

I will try your suggestions and report back here.

OK, I have achieved success, but not without some interesting stages on the journey and heavy dependence on your advice.

First I tried the standard JPI4 route this time with the full db server name and short form db name and db user name. No difference - no progress bar, no error messages, some pause and then presenting the next JPI4 page with a message saying the the FTP connection was fine. No writing to database. Tried again with db server IP address - same difference. Tried reducing the two max size parameters (down to 128,000 and 100) - longer pause but no other difference.

Second I tried to get rid of the Display Errors warning - and with a bit of luck found the hidden php.ini file that was used (in the case of php 5) rather than the one in the root directory. Tried the above again - no difference.

So it appeared to be manual database restore. Downloaded Notepad++ and it worked beautifully. With trepidation went phpMyAdmin and imported the 1.2Mb edited SQL file. GoDaddy's import page suggested a file size limit of 1Mb - but its suggested zip file upload was not recognised - so I tried the uncompressed file. It came back with a timeout error message but the data tables were now all there (or appear to be).

Edited the configuration.php to show the new db parameters, killed the installation folder and the site and the backend both are now visible and appear to be complete.

I would appreciate it if you could suggest any ways I can ensure that the last part of the sql file was successfully restored - but basically it appears to be all fine.

Thanks again for your great support. There are a few screen shot attachments.

David

David,

You can break that SQL file in two. Just make sure you break it so that the second file begins with a CREATE TABLE line. That keeps the CREATE and the INSERT for a single table together and if you reverse the files, it still works.

Thanks Nicholas. It was solely Linux server, but I was using FireFox 3.6 with a number of developer addins, though I have not had the JS problem before. Next time I will use IE as an alternative.

And thanks Dale. That gives me a good workaround the next time I have this issue. So far there doesn't seem to be anything missing from the new site.

Thank you both for your great support. The site is the FreeWorldFoundation.org (a Ghanean charity registered with the UN online volunteer organisation - should be live within the next week.