Thread

Sorry, got busy and then had to go to class…ipower told ME that it was the fact they changed nameservers - and that we needed to change the nameserver to the new one - that was doing this.

They changed the fraking NAMEserver!!! Oy.

??  That… doesn’t make sense to me.  But I’m not a server guru, so if it works, I won’t complain. 

ericlerner, I strongly suspect your issue is different.  But layout the details of what version/build of EE your using, the exact error you get, how consistent the error is and whether it worked before and just started acting up.  I’ll likely split it off to a new thread, so treat it as such.  The more detail you can give, the better.  And asking the host about a mysql error like that is definitely a good idea.

Everything was working fine for my client’s site until last week/the weekend. I also know other people with WordPress installations on ipower which got really, really screwed up, due to all this whatever-the-heck ipower is doing. But that was last May/June, unless they are doing some sort of migration server by server and they just got to my client’s server.

Anyway, I do think it’s an ipower problem. There’s been nothing but headaches with them for several friends of mine in the last three months.

Oh, and RE

then the question is why is EE incompatible with 2 popular servers?

Godaddy is a pain in the butt to install EE on because of how they set their server software. It can be done, but there’s workarounds you need to do. Godaddy is a pain anyway. I had a client on GoDaddy and we successfully installed EE, but it was painful.

RR, You need to iron out the database connection problems first.

I do want to check this with the updated version of EE before switching servers.  anyway, as you know, I had this extra /log/ folder with the old version (focusfusion.org/log/index.php). 

I’m wondering if I can install the new ee version 1.6.4 in the main folder, give the system folder a different name, run the install wizard and connect it to the database to see if this works.  They are separated by that /log/ folder, so the versions should be walled off from each other.

I’m just worried that the install.php thing will overwrite parts of the database.  I’ve backed it up, but still, no need to aggravate things.  Does the install thing just connect you to the database or do more?  Or should I run it as an upgrade, even though I’m moving it to the base folder? 

Don’t want to muck things up more than necessary.

Also, it seems that migrating over to a new server requires similar connecting to existing, migrated database, so I’ll face this same issue either way.

Thanks 4 your help!

Just to confirm, running install.php will install EE anew and the content of your database would be lost. As to running update.php you only need that when the EE files and database are not in sync. Otherwise all you need to do is install the files in a directory where EE can find them, and change config.php accordingly.

Just to confirm, running install.php will install EE anew and the content of your database would be lost. As to running update.php you only need that when the EE files and database are not in sync. Otherwise all you need to do is install the files in a directory where EE can find them, and change config.php accordingly.

OK, so nix on install.php

The thing is, I’ve looked into the new config.php files and they are blank.  So some kind of installation is required.  And I assume the files and database will be out of sync, since i’m going from 1.4.2 to 1.6.4

The issue, as mentioned, is that I’m installing this in a new directory.  The root, I guess.  in public_html/.. rather than one folder deeper like before public_html/log/...

So, it’s a whole new version of ee, in a different location, blank config file.  Do I copy the config file from the old location into the new location and then run update?  The old config version was a lot more complex than the new versions are.  All the info was kept in them.  (I run another site, have noticed the streamlined config file). 

So…what to do?

Make a backup of all your files and the database, upload the 1.6.4 files, copy the old (“long”) config.php and make sure the db user, password etc are still correct, then run update.php. That will update the database, and shorten config.php to the new standard (provided config.php is actually writeable).

Thanks!  That worked remarkably well.  As for mySQL problems, I’ve just switched over to expression engine hosting.  It seems to be working fine so far!

Thanks again for all your help.

No problem. Since your issue seems to be resolved, I am going to close this thread now, if anything else comes up, please simply start a new one. Thanks.