• Hello

    Is anyone aware of problems installing and configuring WordPress on IIS/Windows? Is there is any documentation or guidance available specifically describing the procedure for installing on a Windows server?

    Thanks

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter mikedorey

    (@mikedorey)

    I am still struggling with this.

    I have upgraded to 3.0 and am running on Windows (Not Linux).

    When I go to Super admin, I can create a new blog, and can see it under ‘list of sites’. Clicking on ‘Edit’ shows its details OK, but clicking on backend or view gives 404 errors.

    The original Blog is fine.

    Any thoughts? It looks as if it ought to be easy to solve?

    I can provide more details and screen grabs if needed.

    Mike

    Hi mikedorey, the easiest way to install WordPress on Windows/IIS is to use the Web Platform Installer, http://www.microsoft.com/web/wordpress.

    However, the version we have up there is 3.0.1. So you can either install via Web PI and just upgrade it or if you want to use the latest version from scratch you can install it manually and use these instructions here, http://learn.iis.net/page.aspx/280/install-wordpress-on-iis/ The version numbers are out of date but the guidance is the same essentially.

    If you have questions ping me on Twitter, markjbrown.

    -mark

    Thread Starter mikedorey

    (@mikedorey)

    Hi Mark

    I have worked through this, but no joy. Also, I don’t seem to have a php.ini file. Is this global to the server (in which case maybe I don’t have access to it and need my ISP to make the changes)?

    I have also noticed that if I go to ‘Super Admin’ -> ‘Update Network’ I get this error message:

    Warning! Problem updating http://www.mysite.com/blog/thenewblogname. Your server may not be able to connect to sites running on it. Error message: Could not open handle for fopen() to http://www.mysite.com/blog/thenewblogname/wp-admin/upgrade.php?step=upgrade_db

    My wp-config.php file looks like this:

    <?php
    // ** MySQL settings ** //
    define('DB_NAME', 'database');    // The name of the database
    define('DB_USER', 'username');     // Your MySQL username
    define('DB_PASSWORD', 'password'); // ...and password
    define('DB_HOST', 'db-f2s');    // 99% chance you won't need to change this value
    define('DB_CHARSET', 'utf8');
    define('DB_COLLATE', '');
    
    // Change each KEY to a different unique phrase.  You won't have to remember the phrases later,
    // so make them long and complicated.  You can visit http://api.wordpress.org/secret-key/1.1/
    // to get keys generated for you, or just make something up.  Each key should have a different phrase.
    define('AUTH_KEY', 'put your unique phrase here'); // Change this to a unique phrase.
    define('SECURE_AUTH_KEY', 'put your unique phrase here'); // Change this to a unique phrase.
    define('LOGGED_IN_KEY', 'put your unique phrase here'); // Change this to a unique phrase.
    
    // You can have multiple installations in one database if you give each a unique prefix
    $table_prefix  = 'blog_';   // Only numbers, letters, and underscores please!
    
    // Change this to localize WordPress.  A corresponding MO file for the
    // chosen language must be installed to wp-content/languages.
    // For example, install de.mo to wp-content/languages and set WPLANG to 'de'
    // to enable German language support.
    define ('WPLANG', '');
    define('WP_ALLOW_MULTISITE', true);
    define( 'MULTISITE', true );
    define( 'SUBDOMAIN_INSTALL', false );
    $base = '/blog/';
    define( 'DOMAIN_CURRENT_SITE', 'www.mysite.com' );
    define( 'PATH_CURRENT_SITE', '/blog/' );
    define( 'SITE_ID_CURRENT_SITE', 1 );
    define( 'BLOG_ID_CURRENT_SITE', 1 );
    define( 'NONCE_KEY', 'H~FS&pafKSO9{!imO|03QTY#2-VNYKDWF&T.KE}uAQch>L6]<rzJoKTvC=%YiF2f' );
    define( 'AUTH_SALT', '{%9Zm^Ctj1%q8>sU$&S6.?ay%C^XU-y<$}VODit.E;5|Dn}xO

    OY:mAr2(2D[ik7′ );
    define( ‘SECURE_AUTH_SALT’, ‘A<DZuZ|>p$ERkCGc&YqtwYto$<#$eFmDqvV{Yv2#S5{.{g5^:;Y5.tF5o#Rvw ‘ );
    define( ‘LOGGED_IN_SALT’, ‘?%k6XxqJy*aq%$<P1cLxO#<iizRPqU3seyE!q$G</L{D:_wPDHIKlAG10!p9!s’ );
    define( ‘NONCE_SALT’, ‘E:J[~7]JUN%K{W^JW=WEPPn.0qo |w?Bfq@r#:9_^xS^B.tTC* `01U[y!c<k,S:’ );

    /* That’s all, stop editing! Happy blogging. */

    if ( !defined(‘ABSPATH’) )
    define(‘ABSPATH’, dirname(__FILE__) . ‘/’);
    require_once(ABSPATH . ‘wp-settings.php’);
    ?>

    And my web.config file looks like this:

    <?xml version=”1.0″ encoding=”UTF-8″?>
    <configuration>
    <system.webServer>
    <rewrite>
    <rules>
    <rule name=”Main Rule” stopProcessing=”true”>
    <match url=”.*” />
    <conditions logicalGrouping=”MatchAll”>
    <add input=”{REQUEST_FILENAME}” matchType=”IsFile” negate=”true” />
    <add input=”{REQUEST_FILENAME}” matchType=”IsDirectory” negate=”true” />
    </conditions>
    <action type=”Rewrite” url=”index.php” />
    </rule>
    <rule name=”WordPress Rule 1″ stopProcessing=”true”>
    <match url=”^index\.php$” ignoreCase=”false” />
    <action type=”None” />
    </rule>
    <rule name=”WordPress Rule 2″ stopProcessing=”true”>
    <match url=”^([_0-9a-zA-Z-]+/)?files/(.+)” ignoreCase=”false” />
    <action type=”Rewrite” url=”wp-includes/ms-files.php?file={R:2}” appendQueryString=”false” />
    </rule>
    <rule name=”WordPress Rule 3″ stopProcessing=”true”>
    <match url=”^([_0-9a-zA-Z-]+/)?wp-admin$” ignoreCase=”false” />
    <action type=”Redirect” url=”{R:1}wp-admin/” redirectType=”Permanent” />
    </rule>
    <rule name=”WordPress Rule 4″ stopProcessing=”true”>
    <match url=”^” ignoreCase=”false” />
    <conditions logicalGrouping=”MatchAny”>
    <add input=”{REQUEST_FILENAME}” matchType=”IsFile” ignoreCase=”false” />
    <add input=”{REQUEST_FILENAME}” matchType=”IsDirectory” ignoreCase=”false” />
    </conditions>
    <action type=”None” />
    </rule>
    <rule name=”WordPress Rule 5″ stopProcessing=”true”>
    <match url=”^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*)” ignoreCase=”false” />
    <action type=”Rewrite” url=”{R:2}” />
    </rule>
    <rule name=”WordPress Rule 6″ stopProcessing=”true”>
    <match url=”^([_0-9a-zA-Z-]+/)?(.*\.php)$” ignoreCase=”false” />
    <action type=”Rewrite” url=”{R:2}” />
    </rule>
    <rule name=”WordPress Rule 7″ stopProcessing=”true”>
    <match url=”.” ignoreCase=”false” />
    <action type=”Rewrite” url=”index.php” />
    </rule>
    </rules>
    </rewrite>
    </system.webServer>
    </configuration>

    `

    Many thanks

    Mike

    Thread Starter mikedorey

    (@mikedorey)

    Apologies that the previous post came out a bit haywire but hope you can still follow it OK.

    Got the same issue over here. Though the difference is that I’m using WampServer. I’ll be following this thread in case some expert shows up and says “Well, this is how you do it.” Something simple I’ll bet and we’ll all *facepalm*.

    Thread Starter mikedorey

    (@mikedorey)

    Yes. It’s very frustrating because my original Blog works fine. I have also enabled pretty permalinks which work a treat.

    The additional Blog looks as though it has been created though, and I can update details via SuperAdmin -> Edit. But I can’t browse to it or do anything else.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Problems running WordPress on IIS/Windows?’ is closed to new replies.