WordPress.org

Ready to get started?Download WordPress

Forums

Local to server ... can't get past the install page... (12 posts)

  1. matius
    Member
    Posted 3 years ago #

    Having a hard time understanding this process, but I need to know once and for all. "Moving WordPress" in the codex is just plain not helpful.

    Site works great on localhost... so what's wrong with my move logic here?

    1. Export local database ... updates paths/variables
    2. Create database on server, import tables from updated file
    3. Upload files from localhost
    4. Update wp-config.php with the new server variables
    5. Enjoy your work on a live server??

    Nope, just takes me to the install page.

    Which step and/or instruction am I missing? I really appreciate any help & clarification for the future.

  2. matius
    Member
    Posted 3 years ago #

    Guys, thinking about this more ... is there something in a file somewhere that might cause activation issues between hosts? Something that's not in the database?

  3. If it's hitting the install page, then it can't see the database. Are you sure that's set up right in wp-config?

  4. matius
    Member
    Posted 3 years ago #

    Hi ipstenu, thanks for the reply. About at my wits end - should be such a simple process.

    Yep everything is right & I even recreated the user in my database again with the password just to make sure.

    I've noticed this struggle with 3.01, didn't happen with the earlier versions.

    Maybe the .htaccess?

  5. No, you're not at a point where the .htaccess matters yet. This really is just a case of wp-config cannot see the database. So.

    Are you pointing to 'localhost' for your database? I know you know the drill :) But for sanity's sake:

    // ** MySQL settings - You can get this info from your web host ** //
    /** The name of the database for WordPress */
    define('DB_NAME', 'MYDATABASE');
    define('DB_USER', 'MYUSER');
    define('DB_PASSWORD', 'MYUSERs PASSWORD');
    define('DB_HOST', 'localhost');
    define('DB_CHARSET', 'utf8');
    define('DB_COLLATE', '');

    Also, is your wp-config.php in the right folder? I've accidently put in wrong a couple times.

  6. matius
    Member
    Posted 3 years ago #

    Yea, honestly everything looks right. wp-config just sits in 'public_html', the structure should be exactly the same... Even had my host take a look at everything just to make sure I wasn't climbing up the walls.

    I had to install fresh on my server and transfer all of the information from my local server... until I figure out what's going wrong, this is what I'll have to do for every site. Which sucks.

  7. matius
    Member
    Posted 3 years ago #

    ...btw, thanks for eliminating the .htaccess as one source of the issue!

    Any chance that the auto-generated variables (sorry not in front the file - the "salt" portion) would be screw facing things?

  8. No, the salts just affect login and cookies.

    Something's not right with your database talking to your blog. You might want to pour over the two databases and see if you can find discrepancies. Maybe there's some typo when you did a search/replace that's gacking it?

  9. matius
    Member
    Posted 3 years ago #

    Thanks. I'm starting to understand.

    As for the typo - I won't count that out but instructions are fairly simple... open the SQL file and replace 'http://localhost/myfolder' with 'http://mydomain.com'.

    That's what's throwing me off. It's fairly straight forward.

    But I'll report back when I've found the solution...

  10. Yeah, but the simple steps are the ones I always screw up ;)

    In theory, all you have to do to move is copy the files, copy the database, make sure the wp-config points to the right new database, have a beer. You're right, it SHOULD be easy. Somewhere in there, the new database on the new server is just not friendly to the wp-config which for me has always meant it's a stupid-easy typo that my brain skips over because it's close ENOUGH. I end up copy/pasting info to make sure I don't have weird formatting, and re-doing all my single and double quotes, to ensure I don't have smart quotes or such causing me grief.

  11. matius
    Member
    Posted 3 years ago #

    hmmm... i suppose that does make quite a bit of sense. will check on it.

  12. bellarush
    Member
    Posted 3 years ago #

    If you use cut/paste to change the information, be careful there are no extra spaces inserted.

    As example, 'dbo445396373 ' is incorrect. The paste added an extra space after the last number.

    It should read: 'dbo445396373'

    Happened to me several times before I put on my glasses and checked everything carefully.

Topic Closed

This topic has been closed to new replies.

About this Topic