Two weeks ago I got it in my head that it was time to learn everything there was to know about WordPress. So, I decided that I would install the product on a Windows 8.1 Machine under IIS 8.5. Most installations of WordPress uses Linux and the LAMP tech stack. I decided to use Windows instead because that is what I'm most familiar with.
Needless to say, this was an exercise in frustration...
Initially, I tried to go the simple route and use Windows' WebMatrix tool. This tool theoretically should locate and install everything needed to run WordPress. After successfully installing the Prerequisites, it failed when trying to install WordPress itself. I spent hours trying to figure out what the problem was - the WebMatrix log files were no help. Even after posting them on the Microsoft forums, no one could help - it was a complete mystery. So, I did the next best thing and attempted a manual install.
Since WebMatrix had installed most of the prerequisite software I figured it was best to just remove them all. So, I uninstalled MySQL and any other components that weren't on the machine before I attempted this project. Ultimately I was able to follow most of the steps in the documentation with some very glaring exceptions. Most times, when attempting to install a component I found that I needed to manually install an update from Microsoft such as MSVC 2013 and MSVC 2012. Here is a [long] summary of the steps that worked for me:
WordPress has the ability to run multiple websites from one installation. This has numerous benefits with one big drawback. The drawback is this - if something goes wrong with your main WordPress install, all associated sites go down with it. I chose to activate the Multi-site option though because a good backup strategy will mitigate this drawback enough for my purposes.
So, things get really fun from here on out.
You thought we were done, huh? But, no website is complete without activating SSL. For a Multi-Site install on Windows IIS, this took many many days of research to figure out. Here is a summary of the steps.
3. Now you have to redirect all http calls to https: To do this, add the following code in the config.web file, ABOVE the existing WP rewrite rules:
Note that you would only do things this way if you want ALL Your pages to be SSL enabled. If you want only some pages SSL enabled that's a different ball game.
After figuring out all these steps, I was almost there. The biggest problem was installing multiple SSL certificates in IIS all pointing to the same IP address where WP was installed. There are THREE things that need to be done to make this happen:
At this point, everything should be working well. Except if you try to navigate to a sub-domain directly. i.e. trying to type http://subdomain.yourdomain.com will result in a "too many redirects" error. All sub-domains MUST have a top level domain mapped to it in both IIS and the WPMU Domain Mapping Plugin. I am still researching this issue.
All told - about 2 weeks worth of time to figure this out. The famous WordPress 5 min install doesn't quite work out that simply when performing the installation on Windows and IIS.
Nigel Bahadur's normal market observations - usually about the US Futures market. Occasionally though, he will express thoughts on individual stocks and FOREX cross rates.