URL's Not Resolving

Thankfully @themadproducer saved the day for me. The advice really worked after it appeared I had some how caused an infinte loop of redirects between each site while attempting to login.

Here’s what happened to me.

1. I installed WP-Clone on both sites. BackedUp on site A, restored to site B – new install WP 4.4 (different server)

2. Backup and restore worked with no errors but then I checked and all urls pointed to the old site – site A

3. I then tried to log in to site B but the login redirected me to site A login

4. So I changed the site URL and wordpress URL in site A and caused a whole heap of mayhem – when trying to log into either site caused a redirect to each other no matter what I tried – major panic set in, I couldn’t access either site!!!.

5. I then tried https://www.siteB.com/wp-login.php rather than https://www.siteB.com/wp-admin.php and I got in to the dashboard – phew!

6. I then changed both the site url and wp url to SiteB

7. I then followed @themeproducer’s advice:-

Via ftp, I added the following to wp-config.php: of the new cloned site…
define(‘RELOCATE’, true);

With that set, try to login to WP.
WP will detect the new location and update the URLs in the database.

Immediately remove the RELOCATE line via ftp and save.

And now I’m back in to both sites and no URL issues.

Thanks!!

Jonathan

I had the same problem as all of you, after restoring Site A to Site B, all Site B links (even login) would point to Site A instead.

Unfortunately i did not read this beforehand so i did not try the new fix, but themadproducer‘s fix worked really nice for me.

At first i thought it only half worked, because it allowed me to log into Site B but all of the page links were still to Site B, then upon closer reading i saw the changes he suggested in Settings->General.
WordPress Address (URL) had Site B’s address but Site Address (URL) still had Site A’s address, fixing that seems to have fixed everything.

I was using WP 4.4 and WP Clone v2.2 on both sites, and i also did not get any error messages while restoring, but i did get 20 identical warnings while backing up, saying:

Warning: Invalid argument supplied for foreach() in /home/hidden/public_html/username/wp-content/plugins/wp-clone-by-wp-academy/lib/functions.php on line 492

But i’m pretty sure that didn’t have anything to do with it because every version of WP Clone i used in the past 2 years always gave some kind of warning, for some reason.

If i can help in some way, by providing more details/information, let me know.

I too had the same issue as everyone else, the new cloned site links were all going back to the old original site. Just wanted to add my solution, which someone else I believe mentioned. Its the easiest and first thing to try I think, and that is to go to myPHPadmin to access the DB, then you will likly see that the website address and site address are still the old cloned site and not the new cloned site. I just changed those to the new site URL’s and all works perfect. Very simple and should be first try, all the links etc. now work perfect and do not bounce to the old site. For some reason WP Clone is missing the change of these two most important settings. Note this has happened several times on different sites and servers, don’t know why, but most times the clone works perfect without having to do this.

Jacson

SORRY! To continue the above post… Just realized that all the image links (and I am sure other links) did not change, so although the main nav links worked after changing the sites address I still had to go back and do a find/replace of the entire DB to change the old website to the new website URL. So the Author is correct in that for some reason the find and replace is not working in the plugin, this seems to be the culprit.

@jacguerrant
Thanks for the follow up report.

Have you tried the method I described. Seemed to work fine for me and @jlyon and @joegp.

Well I have to say that I am really disappoint that this issue is still not resolve is this plugin being abandoned by the developer if so he should let us all know so we can find other solutions.

This worked for me, two steps solution:
-clone to new wordpress installation as you usually would
-edit wp-config.php of new wordpress by adding these two lines at top of file, right after <?php

define('WP_HOME','https://example.com');
define('WP_SITEURL','https://example.com');

Of course, instead of example.com use your new website’s URL

Hope the author finds a way to fix this as it would be a shame plugins this useful loses any more credibility.

So this morning I tried your new update with all plugins that contain nay type of redirect feature deactivated.
Didn’t even make it to the back up without a fatal error message.

What do your notes mean on similiar url’s? Would that apply to subdomains?

/wp-content/plugins/wp-clone-by-wp-academy/lib/functions.php on line 1160

what’s the rest of the error?

“What do your notes mean on similiar url’s? Would that apply to subdomains?”
nope, it only applies when the URLs are 100% similar.

The beginning of the error message is:

Fatal error: Call to undefined method PclZip::addFile() in then folder destination mentioned above.

Could you define 100% similiar?

Like serviceAB.example.com vs service.example.com?

okay I see the problem. for the time being you could use the alternate zip method to get around it.

serviceAB.example.com is 100% similar to serviceAB.example.com, so search and replace won’t run.
service.example.com, on the other hand, is not 100% similar to serviceAB.example.com so search and replace will run.

That’s a contradiction.

service.example.com and serviceAB.example.com are too similar to run correct?

house.example.com and developer.example.com are ok to run?

let me put it in another way, there’s no point in doing a search for “https://site.com/path&#8221; and replacing it with “https://site.com/path&#8221;, so search and replace won’t run if the URLs are identical (for example, when you’re restoring an older backup on the same site)

Hey i just cloned a site using version 2.2.2 and while it took forever and ended up in a “connection timed out” (or reset) it worked perfectly.

I didn’t get any errors/warnings when making the backup file either something that’s never happened before).