Issues moving from IIS localhost machine into Windows Server production
By
Matt Cohen, in General Support
-
Recently Browsing 0 members
No registered users viewing this page.
-
Similar Content
-
By NooseLadder
Hi,
I've been out of the game for a number of years (6/7). I have a few projects lined up. I used to use XAMPP on my Windows PC back then. I have a Windows 8.1 laptop atm. Is XAMPP still ok or can you recommend anything better? I used to upload files to server using FileZilla. Thanks.
-
By Peter Knight
Hi all
My .htaccess file is correctly redirecting all requests to
https:// www. That's great until I want to work locally.
I thought I had seen a blog post by Ryan where there was a new config setting to ignore both of these if working from localhost?
I can't find it now so wondering if I was imagining 😕
-
By joeck
Hi there,
I'm trying to have a multi-site (multiple databases) setup on a IIS (Microsoft) server.
I know that IIS is not officially supported by ProcessWire but customer is insisting on IIS.
I get an 500 Error when trying to access the sub-domain/other processwire site.
Did somebody do this before or is it not possible at all to have a multi-site setup on IIS?
Thanks
-
By kongondo
So, all of a sudden, Chrome is blocking all of my localhost sites, claiming my connection is not Private, blah blah..Here is the full text of what Chrome is telling me.
I get no option to 'continue to this unsafe site'.
It seems I have no option but to install SSL on my local sites. I have seen some articles on how easy it is to do in a Mac but I am on Windows. Anyone has pointers on how I can do this? Alternatively, anyone knows what this Chrome error is about? Bottom line is, unless I change browsers, I am not currently able to develop and test stuff locally. Grr!
Thanks.
-
By 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.
-