wp_login goes in loop

Hi update:

I got in, have no idea why I was in the endless loop, tried a different browser in case it was a cache issue.

I still have a question about, I need the /DD install on the root. Should I have put it there to start with? I tried but it said all the wordpress files already there could cause a problem so I was noticing the path the person used in your video and used a similar one.

Is it best to just wipe all files in a root folder before bringing in the installer and zip files from the previous backup? (after saving all wanted files)

Thanks

Hey @gleg,

It is best to start with an empty directory this way you won’t have lingering files from the old install that might cause conflicts. It’s not required but is a good practice. As far as where you place the files, I usually never put them in the root public_html. I would create a folder with your site name and place them in there. This way if you want to add additional WP sites to your host you can do it easily.

Hope this helps~

Hi..Thanks for the info. If I start with and empty folder off the public_html root, like /AA and not move the files to root after building the site. The path would be https://www.mysite.com/AA seems like. That would not work, seems like once /AA is looking the way I want, I would move it to root so the site location would be https://www.mysite.com.

In some cases, you might want to do that through an add-on domain, such as here:
https://www.inmotionhosting.com/support/edu/cpanel/cpanel-manage-domains/adding-addon-domains-in-cpanel

In most cases, I would contact your host because they all have different ways of setting up the domain.

Hope that helps~

Hi, I’m using duplicator plugin “to” redesign/rebuild the wordpress install on root. Once /AA is looking and operating the way I want, what is the best way to move to root so all the linking and functions work correctly after the move.

Thanks!

Hi I might have it now. After I have /AA looking and operating the way I want. I just save it using duplicator and reinstall on root using duplicator (after storing files on root before removing) and should be good to go.

Thanks!

• This reply was modified 6 years, 6 months ago by gleg.

I am offering this comment simply because my understanding of what you want to accomplish is a sequence I follow perhaps 50% of the time I use the plugin. Very often when making substantial changes to an existing website, I create a subdomain that is easy for people to remember (e.g. domain_name/test) and move (duplicate) a full copy of the original website for further development or changes. Often that subdomain is password protected.

When complete and approved, I move the new site to the original domain as you describe. Tips from my experience: delete everything from the domain site folder EXCEPT the subdomain (folder); make sure you are using two unique databases for each. Often I even leave the /test domain live for a short period for comparison. More than once I’ve had someone tell me they “remembered” something different between the test and live sites, so having the test site continue to be available for a while is a good way to keep the peace without finger pointing. Sometimes they are right, too. If your sites are very big and especially with lots of assets/content, perhaps having two full sites and databases exceeds a limit. I haven’t reached that situation yet even with economy hosting, but I have no doubts it can happen.