Moved WordPress From Local To Remote: Assistance Requested

  • Resolved velanche

    (@velanche)


    17 years, 10 months ago

    Greetings:
    My brain is a bit mushed right now, so I hope that I can get some assistance from the WordPress community.

    I’ve worked on WordPress on my laptop via MAMP on Mac OS X. After doing some work on the local machine, I’ve decided to upload it to my remote server. I’ve backed up my sql file, and then edited the file to reflect the remote URL. I’ve then uploaded the sql file to the remote under an existing database. That went smoothly with no errors.

    I’ve then created a wordpress directory on the remote, and then ftp-ed the wordpress directory from my local to the remote. Beforehand, I went into Options in the admin panel to update to the new url instead of localhost (the remote being http://www.urbanlandscapes.org/wordpress). I’ve also looked at the wp-config.php file and nothing needed to be changed there.

    So where am I now?? Well it seems that the WP database must not be talking with the data files somehow. The login screen and the index.php file are both without any use of CSS or of any of WordPress’s functionality. Running the install script produced a window that said that WordPress was already installed. Logging in takes me to the W3C site….whoa!

    I need to get away from this for awhile, but I’m very, very open to any assistance to help put the rest of the pieces together. By the way, I do not want the main index.php to be the root URL yet until all is done.

    Thanks very much.
    Velanche

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter velanche

    (@velanche)

    17 years, 10 months ago

    Okay, I’ve managed to copy the .htaccess file (which wasn’t on the remote) to the wordpress directory, and also changed the url in the two sections of the wp_options areas of my database.

    Still no change when attempting to access http://www.urbanlandscapes.org/wordpress. In fact, this is the 404 error I get…

    Not Found
    The requested URL /cgi-sys/php-fastcgi/wordpress/index.php was not found on this server.

    Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
    Apache/1.3.34 Server at urbanlandscapes.org Port 80

    Hope this will help move things along.
    Velanche

    yosemite

    (@yosemite)

    17 years, 10 months ago

    Take a moment to read this:
    http://codex.wordpress.org/Using_Permalinks
    (assuming you are using permalinks)

    Thread Starter velanche

    (@velanche)

    17 years, 10 months ago

    Yes, I’ve had permalinks turned on locally.

    But now I fear that I might have created a problem that I’m unable to get out of. I was following instructions somewhere in the Codex to change to my new domain address in two fields in the Options area of the WordPress Admin Panel before FTPing the WordPress directory to my remote.

    When I type localhost:8888/wordpress, I can see my chosen theme and pages. But when I try and access the admin window, it brings up the admin window on my remote server (because after all, I did change the site location per the pre-upload instructions).

    Can I change my local settings back by going into phpMyAdmin to the wp_options and setting the values to localhost again, or is there another way?

    But in the grand scheme of things, I don’t think that permalinks are the problem on the remote side. Any other ideas?

    Thanks,
    Velanche

    yosemite

    (@yosemite)

    17 years, 10 months ago

    A few thoughts:

    You should be able to change back to localhost on your home MAMP, so when you got to your MAMP site there are unique settings, and when you go to your remote/LAMP site there are other settings. Makes sure each respective wp-config.php is set accordingly. Use phpMyAdmin locally to change (back) URI’s. See http://www.tamba2.org.uk/wordpress/site-url/

    This path: /cgi-sys/php-fastcgi/wordpress/index.php looks really odd. Check your remote Apache configuration to confirm where the ‘public’ html directory is (lacking any other information, I’m assuming your remote is a dedicated server you maintain).

    If you don’t want index.php to be accessible, I suggest you add DirectoryIndex index.html to your .htaccess file and create a dummy/temp/construction index.html page, that will appear instead of index.php to anyone who simply goes to urbanlandscapes.org/wordpress without inserting index.php specifically.

    On your remote I suggest you update your permalink structure (to get fresh rewrite rules) and make sure these get into your remote’s wordpress/.htaccess.

    Report back ;’)

    Thread Starter velanche

    (@velanche)

    17 years, 10 months ago

    I will have a look at the above later on…thanks for sticking with me.

    The path:

    /cgi-sys/php-fastcgi/wordpress/index.php

    is on the remote server; however, my account is shared hosting as opposed to my own dedicated server. So any further insight as to what I should be looking for would be good.

    My host’s Apache installation appears to be in /usr/local on my host provider’s UNIX server, if that helps.

    Any further insight on this? Meanwhile, will check the other items later. Thank you.

    Thread Starter velanche

    (@velanche)

    17 years, 10 months ago

    Damn, damn, and triple-damn….

    I did it!!

    Thanks to your suggestion, I was able to get localhost working again.

    In addition, I’ve found in my remote that for some reason, both siteurl and home had an extra http:// next to the remote web address. Not sure how it got there, other than…*cough*…user error.

    And it only took me no more than about 20 minutes.

    I will take your suggestion on changing the index within th next few days. Again, permalinks are already in place.

    Thanks very much for the help. Now I can focus on putting the rest of the pieces together.

    Peace out,
    Velanche

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Moved WordPress From Local To Remote: Assistance Requested’ is closed to new replies.