Problem logging in after moving files – it's not my url settings

  • Resolved pam

    (@manabeads)


    10 years, 8 months ago

    I have a live site at example.com. I created a redesigned site with wordpress at example.com/blog. It’s fabulous and ready to replace the current design. I planned and researched the migration (moving the wordpress site from ../blog to the root) but it hasn’t gone very well and now I can’t access the admin panel.

    Here’s what has been done:

    -Read lots of documentation
    -Changed the urls for site and home in the admin panel
    -Copied all the wp files to the root (I copied rather than moved in case I needed them later, but renamed the “blog” folder “blog1”)
    -Went to log back in, couldn’t do it.
    -Messed around with the various ways of changing the site urls (through the template functions.php file, the wp-config file, etc)
    -Was able to login.
    -Ran blue velvet plugin to address orphaned links
    -Changed permalinks through a code fix to web.config (because I’m not on linux, if I remember correctly) This code fix was found in the WP codex
    -Everything worked fine except for some images.
    -Turned off my computer & went to work
    -Home from work… Can’t log in. Hmmmph.

    When I try logging in I do so from the ‘example.com/wp-admin’ page but once I click the “submit” button it takes me to ‘example.com/blog/wp-login.php’ which is a 500 error. This makes me think it’s a site url issue, but that is changed everywhere and I have checked the database to be sure.

    I feel like it’s some tiny line of code that got screwy when I was moving/copying/tinkering with files. Does anyone have an idea what files I should look at? Also, is it possible (or advisable) to re-install wordpress and somehow save my content?

Viewing 6 replies - 1 through 6 (of 6 total)

  • @pam
    Kindly let me know
    1.Was your live site previously designed on WordPress?
    2. Was the site using any database?
    3. After finishing your design on example.com/blog had you installed “WordPress on your live site?
    4.After copying the files, had you created any database?
    5. After creating the database had you configured the wp-config.php file.

    Thread Starter pam

    (@manabeads)

    1. No, it was mostly html
    2.Yes, the site includes a shopping cart that uses a database, but I believe it’s a separate SQL server db, not the MySQL
    3. The live site is at example.com; wordpress was installed on example.com/blog. I moved the files from ../blog to the root according to the directions (at least I thought I did it accordingly), but never installed wordpress a second time.
    4. After copying the files, I did not create a new database. I backed it up once I couldn’t login so I could go in and verify the site url, but no new db was created.
    5. n/a since I didn’t create any new database.

    Also, the WP site was running great from ../blog. The plan was to get the content all completed and then make it my “index” page, redirecting old files to the new WP pages.I kept it in a “maintenance mode” while I worked on it and tested it live every day. I thought maybe the plugin was an issue, but I was able to get on the admin panel that one time, so I don’t think that’s it.

    (Thanks for helping)

    Thread Starter pam

    (@manabeads)

    I have now tried to revert everything back to the /blog directory.
    I renamed all the wp files in my root to “hide” them.

    I can get into the admin panel, and I’ve turned off the maintenance mode. The site url and home url are both pointing to /blog.

    Everything works except I can’t visit my site. It should be available at
    https://manabeads.com/blog

    I get the following error involving the index.php file. Maybe that’s where the error is? I changed that once when I was trying to direct to the correct folder…

    Warning: require(D:\Hosting\7741694\html\bloghttps://www.manabeads.com/wp-blog-header.php) [function.require]: failed to open stream: Invalid argument in D:\Hosting\7741694\html\blog\index.php on line 17

    Fatal error: require() [function.require]: Failed opening required ‘D:\Hosting\7741694\html\bloghttps://www.manabeads.com/wp-blog-header.php’ (include_path=’.;C:\php\pear’) in D:\Hosting\7741694\html\blog\index.php on line 17

    Thread Starter pam

    (@manabeads)

    By the way, line 17 of my ..blog/index.php file is:

    require( dirname( __FILE__ ) . ‘/wp-blog-header.php’ );

    Try to disable all the plugins, Then see if the same error is still there. Once resolved try to enable plugins one by one.

    Thread Starter pam

    (@manabeads)

    As a follow up for people who are curious:
    I had to re-install everything in my desired directory and saved most of it through import/export. I think I had three issues – which started to cross-pollinate, so to speak.

    1. I originally wanted my wp files in a non-root folder, but my home page in the root folder. I may have confused the “site” and “home” definitions.

    2. I had a page called “blog”. But the folder my wp files were in was also called “blog”. So when looking for https://www.mysite/blog it could have meant my wp page OR my ftp folder, causing a problem for the browser looking for that url.

    3.I had a screwy plugin. It wasn’t screwy when I started the migration. But in the midst of all this, when I had a glimpse of my dashboard, there was an update available – which I thought might help. That update screwed up websites all over the world.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Problem logging in after moving files – it's not my url settings’ is closed to new replies.