Closed sha-one closed 5 years ago
I am new to WordMove but my first push to remote did this, yesterday.
I pushed --all
and it worked well, but overwrote my remote TLD with the local TLD. I corrected it in my DB on the remote and all is fine, but I am unclear if I did something incorrectly or if this is a bug.
Very similar to what is described here, but without the subdomain.
This is what I get using wp search-replace
simulating what Wordmove does under the hood (plus activating logging and dry runing the command)
And well...it sounds all good to me. Could you try to do the same simulation? The command I used is
wp search-replace http://domain-name.domain.com http://domainname.local --skip-columns=guid --all-tables --dry-run --report-changed-only --log
Hey @LaurenaRehbein are you sure to have the domains correctly reported inside movefile.yml
including the exact protocol? Is wordmove doctor
complaining abut something?
Closing since abandoned. Sorry
I've encountered an issue where I run a DB Pull and the URL is not being rewritten correctly, for example...
What I get in the DB after pulling to local is: http://domain-name.loc rather than http://domainname.local which is what I'm expecting.
I've never encountered this problem before, any ideas? Note: staging is setup as a subdomain (I don't have control over this) and it is a single-site install
Thanks!