Install on Windows (IIS) Fails for WP 3.7 / 3.8

  • Hello,

    I’m just wondering what the significant difference between WordPress 3.6 and 3.7/3.8 is on a Windows IIS install.

    I can complete the web-based setup fine from start to finish with 3.6, but 3.7 and 3.8 won’t create the wp_config.php file.

    I can install 3.6 and update to 3.7 (or now 3.8) without issue, but a fresh install just won’t work without manually creating the wp_config.php.

    [It’s not a showstopper for me, since I can manually create the config, then carry on the install normally; however, it seems like a bit of step backward.]

    Other factors that may come in to play are that it’s an older server (Windows Server 2003, PHP/MySQL aren’t at the latest versions [but still meet WP requirements]), and PHP is installed as ISAPI rather than FastCGI; however, I’m not sure why/how things changed.

    Is anybody else seeing this?

    I can’t seem to find anything via Google, forums or WP trac.

    Any thoughts on the matter would be warmly received.

Viewing 2 replies - 1 through 2 (of 2 total)

  • Any possibility of testing it on Server 2003 and Server 2008 to see if it’s a Server OS issue? Interestingly enough I ran across Stack Overflow question here: https://stackoverflow.com/questions/20573618/drupal-7-and-wordpress-3-8-on-a-windows-production-server
    I’m not sure how credible that answer is though.

    Thread Starter floatingpointmatt

    (@floatingpointmatt)

    Many thanks for the StackOverflow link!

    It’s recent, but seems to be rooted in some legacy thinking.

    My understanding is that Apache on Windows has historically been a “bad idea”, though it works.

    Also MS have put a lot of effort into recent versions of IIS to handle PHP ( see https://php.iis.net/ ) and have put some effort into tools as well ( see https://www.microsoft.com/web/webmatrix/ ).

    Putting that aside, I did try a run on Server 2008 R2 (with PHP set up as FastCGI) and results were better. Permissions are a little tighter there, but the install didn’t bail at the wp-config set up.

    Overall, I’m not surprised to see older architectures falling by the wayside, but I’m still curious as to what changes occurred between 3.6 and later versions to the install.

    I may pull out WP_DEBUG, etc. to see if I can’t sate my curiousity…

    EDIT: Cleaning URLs for auto-link (so they work).

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Install on Windows (IIS) Fails for WP 3.7 / 3.8’ is closed to new replies.