Thread

Been all through the forums for this one and nothing seems to be working. I just got trying this one for the 4th time to no avail: Here

Short version of what’s happening:

Moved the site from a testing server on Bluehost, to another server also on Bluehost.

Moved the files, made the databases as written in the file I linked to above, etc. All that is good to go, but once I get to the login screen here, it obviously isn’t quite what it should be. Nor can I log on. When I put in the proper user name and pass and it doesn’t report any errors, it just stays on the same screen and appends this garbage to the end of the address: index.php?S=7d6a755fbd7f31cdcc7b7326cfccdb6c59ecc38a

Oh…and I’m running 1.6.7

Any ideas? Thanks, gang!

This “garbage” is a session id. If you don’t like it switch to using cookies exclusively. Also, see this article.

Thanks for that, Ingmar. The real issue though is that I can’t log in to the Control Panel at all. Even using usernames/passwords that I KNOW are correct, it’s giving me one of two errors:

1. It’s not an actual user (which it is) and can’t be found in the database
2. When I use the 100% correct user, it seems to accept the data nad not throw any error messages, but the screen never moves past login screen into the actual CP. So…I’m basically dead in the water at the login screen.

Try adding this to your config.php for now, see if that changes anything:

$conf['secure_forms'] = "n";
$conf['debug'] = "2";
$conf['allow_extensions'] = "n";
$conf['cookie_domain'] = ".example.com";
$conf['cookie_path'] = "";
$conf['cookie_prefix'] = "";
$conf['admin_session_type'] = "c";
$conf['require_ip_for_login'] = "n";
$conf['require_ip_for_posting'] = "n";

Be sure to change example.com to your domain. Moving to Tech Support.

Yeah, that did something:

Notice: unserialize() [function.unserialize]: Error at offset 158 of 3525 bytes in /home7/createa3/public_html/proassisting/ee/eecp/core/core.prefs.php on line 129

Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /home7/createa3/public_html/proassisting/ee/eecp/core/core.prefs.php on line 129

Warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home7/createa3/public_html/proassisting/ee/eecp/core/core.prefs.php on line 129

Notice: unserialize() [function.unserialize]: Error at offset 577 of 1929 bytes in /home7/createa3/public_html/proassisting/ee/eecp/core/core.prefs.php on line 129

Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /home7/createa3/public_html/proassisting/ee/eecp/core/core.prefs.php on line 129

Warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home7/createa3/public_html/proassisting/ee/eecp/core/core.prefs.php on line 129

Warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home7/createa3/public_html/proassisting/ee/eecp/core/core.prefs.php on line 129

Warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home7/createa3/public_html/proassisting/ee/eecp/core/core.prefs.php on line 129

Warning: Cannot modify header information - headers already sent by (output started at /home7/createa3/public_html/proassisting/ee/eecp/core/core.prefs.php:129) in /home7/createa3/public_html/proassisting/ee/eecp/core/core.functions.php on line 726

You did not, by any chance, perform a search & replace on the database, did you? I so, you broke a serialized array. See this thread for more info.

No, sure didn’t. Wouldn’t even know how to do that 😊

Hey Ingmar, I don’t mind doing another install from scratch. I’m just worried about the license and having to buy another one for the new site. I mean, this looks to me like I’ve got a big problem and I have no clue what happened cause I followed those simple instructions in the “how do I migrate to a new server” post. So…anything that gets my site off the testing server to the new one is fine with me and I am open for any suggestions.

Thanks!

Hey Ingmar, I don’t mind doing another install from scratch.

That would be the recommended approach, yes. At least replace all of your EE files with known good & fresh copies.

I’m just worried about the license and having to buy another one for the new site.

I don’t see this is a licensing issue, no. One license gives you the right to one public site, but it’s not tied to a particular domain or anything like that.

Alright then. Maybe that’s the shot. I’m just not sure how to get all the posts, theme updates, pages, etc. from the test site. I mean, I’ve exported that database a gazillion times now with all sorts of different options, and each one just leads to an error.

Do you recommend I just do a fresh install on the new site WITHOUT actually bringing over any of the testing server’s files? So…just a fresh EE_Core1.6.7 install? And then…try somehow to bring over the theme files and database? If that’s your idea, want to point me in the right direction?

Thanks again, Ingmar!

No, my suggestion would be to install EE on a brand new site, then import the database from the old site. See if we get any errors after that, and fix them one by one.