Redirected to Old Site after Completed Installation

  • Resolved CK MacLeod

    (@ck-macleod)


    5 years, 9 months ago

    I’ve lost count of how many times I’ve used Duplicator (and Duplicator Pro) successor, though I have also frequently encountered problems.

    This is a new problem for me: After completing the installation process, which seems to run without a hitch, on Admin Login I’m taken to the old site’s admin. If I try to visit the main URL, I’m also redirected.

    It seems that wp-config isn’t being handled correctly: Instead of replacing the database-related defines, the old ones are being left intact, and the new ones are pasted further down in the file, right above /* That’s all, stop editing! Happy blogging. */. However, if I move the new ones to the correct position, I get a blank page or, depending on other factors, a 500 or other error.

    I’ve tried making a new package with all plugins except Duplicator itself turned off and a vanilla WordPress theme enabled. I’ve also tried clearing cookies and using alternative browsers. I’ve checked the database options table for correct home and site url, and I have re-created databases several times before running installer again. I’ve checked DNS and control panel settings for other redirects, and found nothing of interest.

    At this point, I may try a “2-part install” because I might as well – and because in the past that’s always solved problems, though none like this one. It’s only a middle-sized site, and I have run two other successful duplications of similar sites via this same cPanel to similar subdomains in the same hosting account.

    Any ideas? If the 2-part install doesn’t work, then I think my next step will be to do it the very old-fashioned way, with a fresh WordPress installation, and a WP Import of posts and pages.

    • This topic was modified 5 years, 9 months ago by CK MacLeod.
Viewing 9 replies - 1 through 9 (of 9 total)

  • Hey @ck-macleod

    If you want to submit a support ticket for this issue we can have a closer look at your setup. Please provide a link to this thread when submitting the ticket.

    Thanks~

    Thread Starter CK MacLeod

    (@ck-macleod)

    Submitted the ticket over there – am really curious about the cause of this problem!

    Thanks, we will have one of our devs look into the issue as soon as they can get to it.

    Cheers~

    Thread Starter CK MacLeod

    (@ck-macleod)

    Just thought I’d note, for anyone who happens to arrive here, that Snap Creek tech support was very helpful, and solved the mystery: Due to a peculiar bug (possibly originating in the Filezilla FTP program), the wp-config.php file in the original installation was missing new-line characters – as though minified. It was, however, written in such a way that it kept functioning anyway though Duplicator was unable to handle it properly.

    I was able to edit the file, replace the wrong db settings with the right ones, and re-upload using an alternative FTP program (WinSCP). Snap Creek support suggested that a future version of the plugin may handle this odd issue, though I’m not sure it’s really their problem.

    Excellent plugin – great support. If I didn’t already review it once upon a time, I’ll do so later.

    Thanks for the feedback @ck-macleod! We appreciate it!

    CK MacLeod can you tell a bit more what you did, because i have the same problem.
    Thank you

    Thread Starter CK MacLeod

    (@ck-macleod)

    @eva73

    I performed the normal duplication, but the corrupted-but-functional wp-config.php file couldn’t be handled properly by Duplicator. So, it failed at the last step.

    In order to get the site up and running, I had to download the wp-config.php and fix it, 1) manually adding new lines in my code editor (Notepad++), 2) removing the database “define” statements left over from the old installation, 3) replacing them with the ones for the new installation – which Duplicator did add further down in the file – and 4) uploading using WinSCP instead of FileZilla.

    The defines come in a set of four – db user, db name, db password, and db hostname, with the last one most often simply “localhost.”

    You could probably do the same thing using File Manager at your host, if a cPanel installation, instead of an FTP program.

    You can probably see immediately if your issue is of the same type: Open the new, Duplicator-made wp-config.php and see if all of the lines run together. On Notepad++ or other code editor, it may all register as one very long line.

    If it’s something different, but possibly related, check to see whether there is only one set of db define statements.

    If it’s something else, I’d recommend sharing the specifics with Snap Creek support. They seem very responsive, and interested in continually improving their product via user feedback – so may have an answer for you relatively quickly, even if you’re only on a free account.

    • This reply was modified 5 years, 9 months ago by CK MacLeod.

    @ck-macleod
    Thank you for very much. All went well for me until i want to see my webpage.. That’s where it redirects to my old Site.

    Thanks again

    Thread Starter CK MacLeod

    (@ck-macleod)

    To my understanding the reason for the redirection to the old site in cases like this one will be that, whatever else is going on with the config file, the old db info is still intact and readable, and the db includes the old site’s URL.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Redirected to Old Site after Completed Installation’ is closed to new replies.