Renaming Processwire Site on Temporary Domain account to Permanent Domian account?

[John W.]

Summary: If I have a site sitting on a server called testing.com, then on the server change it to mycompany.com, do I have to modify any settings in ProcessWire?

After building several processwire for clients, the one question that I haven't had is about moving a processwire site from an old (temporary) domain to a new domain.

For instance, I typically setup development sites for clients and register a temporary domain (and lock with a password). For instance, thee client can go test.com and get all their content finalized, change wording, add news, swap out photos -- everything to make the site production read.  

Next, on my hosting account I can have testing.com renamed to theircompany.com - and change the nameservers.

A simple question here. If I have a hosting company rename the account from testing.com to theircompany.com, change my nameservers whereas going to theircompany.com loads the production site, Is there anything I need to change in the processwire configuration or in the PW database?

In the past, I've just manually copied the site, and fresh-installed PW, and imported the data. Seems like a lot of hassle.

I have a second part question about updating the PW core, however, after consideration I'll post it as a new topic.

[Sergio]

You don't need to change anything in the database. The only change needed in this case is the httpHosts array:

$config->httpHosts = array('testing.com'); 

in the config.php file. 

[rick]

If it is a new install, then the user salt (site/config.php) will be different, which affects the passwords.

[szabesz]

9 hours ago, rick said:

which affects the passwords

userAuthSalt: " it is forever tied to the passwords as a secondary salt."

But if you use the very same database and files normally you should only need to update $config->httpHosts as @Sérgio Jardim pointed it out above.

[NooseLadder]

Hi,

I have a site that I want to change the primary domain at the hosting level. All else remains the same. I read the above posts but I cannot find this in my config.php. It is an old version of PW 2.3.1. Am I safe just to make the domain change anyway?

On 5/31/2017 at 10:46 PM, Sergio said:

$config->httpHosts = array('testing.com'); 

[Soma]

PW 2.3 didn't have httpHosts config AFAIK.

[John W.]

On 11/11/2018 at 12:33 PM, NooseLadder said:

Hi,

I have a site that I want to change the primary domain at the hosting level. All else remains the same. I read the above posts but I cannot find this in my config.php. It is an old version of PW 2.3.1. Am I safe just to make the domain change anyway?

This was on old post. Actually, what I do is fresh install processwire on the server.  When I get ready to upload my project, I dump my local mySQL database, switch to the online site where I drop tables and import the database.  After that, I uncomment about 3 lines of code in my index.php file that changes the processwire admin password in the database. From there, I just login and also change the passwords for any other roles that my be set up.  Ryan pointed me to the info about setting the passwords via the PW api.

In the past I used phpMyAdmin to dump out the database, now I use the dbbackup() module, save the backup file, then switch to processwire on the server and use dbbackup() to import the dump.

Edited November 13, 2018 by John W.
metion module method of transferring mysql data

[NooseLadder]

Thank for replies. Just to let you know I changed the primary domain on my hosting and the site works without any major changes. Just a few hardwired hyperlinks to change that include the old domain name.

[NooseLadder]

Would the same apply if I changed the site from http to https. Ie no major changes required?

[szabesz]

23 hours ago, NooseLadder said:

if I changed the site from http to https. Ie no major changes required?

Normally this is what you should do:

• make sure templates are set to "HTTP or HTTPS" – which is the default – on the URLs tab and certainly not to "HTTP only"
• in .htaccess, uncomment the rules under "9. If you only want to allow HTTPS, uncomment the RewriteCond and RewriteRule lines below."
• and yes, a properly installed SSL is a must ? 
• recommended: also make sure you do not have any hardwired or third party http URLs