basilv

I’d like to thank everyone again for their feedback. I’ve made more changes – mostly adjusting the horizontal spacing and adding more whitespace as per everyone’s suggestions. I’d like to make more of your changes, but just don’t have the time right now. I’ve written an article about my changes and your feedback – see https://www.basilv.com/psd/blog/2006/website-changes-and-the-value-of-feedback

If you have more feedback, I’d love to hear it.

miklb, thanks – especially under IE, the lines look a little close. I’ve slightly increased the spacing between lines.

Thanks for the feedback.

As a quick fix for the width issue, I’ve reduced the width of the main text column and shifted it to the sidebar.

lhk, I assume by colored candy-style buttons you mean the subscribe buttons in the sidebar in the Feed section?

First impressions of the home page were that it looks quite busy. There seems to be too many navigation options, and its not clear which ones do what. I.e. Browse in top horizontal navigation menu I expected to use to browse articles, but instead it lets you browse the member list.

The Blog Search on the left sidebar background color doesn’t render properly for me (Windows, Firefox 1.5.0.2, large resolution – 1024×533 viewport). Part of this gray background seems to wrap around to the right sidebar on the other side of the page.

I like the article rating system – I hope that works out well in practice.

I like the site – it looks great.

On the archives page, I don’t like how the article category is displayed above the article title in a larger font. This is especially weird since categories are not displayed on the home page or in the sidebar (it appears you’re not using them).

When viewing the archives pages, most of the sidebar is not displayed (just the archives section). I think this looks too bare / empty.

Best of luck with your health.

Hmm, I’m not sure what’s going on. It looks like IIS isn’t picking up your php.ini file – it may be in the wrong directory. I believe it needs to be in your root website directory.

I’m glad you found my article. There is apparently a free version of ISAPI_rewrite you could try. I’ve seen another article that mentioned using 404 error code rules in IIS to handle things, but this requires direct access to the IIS server settings, which is not something I have access to so I didn’t investigate this option (or keep the link).

The problem is as follows: the web server needs to execute the index.php file no matter what your URL is. The remainder of the URL after the index.php is read by the WordPress code and the correct data is returned to be displayed in your browser. With permalinks, the index.php file is not included in the URL, so you need to rewrite the URL to include the index.php, so the web browser knows to execute it.

This is why your home page works, but not the rest. Going to the page https://www.foo.com causes index.php to be invoked by default, which displays the home page. As an example of this, instead of trying a URL https://www.foo.com/category/some-article.html, try inserting index.php after the foo.com like so:
https://www.foo.com/index.php/category/some-article.html. This should correctly display the desired content, because URL rewriting is no longer needed because you manually rewrote the URL to include the index.php.

– Basil

I’ve got WordPress 2.0 running under IIS, including proper permalinks. Check out my article on it: Running WordPress 2.0 under IIS

The access log produced by IIS will show each URL accessed after rewriting and the HTTP status code associated with it. I’m not sure if you can access the raw log or not (My hosting company does provide such access). That may help a little, although its hard sometimes which line in the log corresponds to what experiment you tried.

Glad I could help. Unfortunately, I too could have used a way of debugging the rewrite rules, but didn’t find an approach. The <a href=”https://dev.wp-plugins.org/browser/dump_env/
“>Debug Env plugin may help with your blank page problem, but I haven’t tried it myself.

It should be fairly easy to modify index.php to log or write out in a html comment the full URL. Of course, if a rule is wrong, index.php may not be invoked.

I suspect getting IIS or the ISA_Rewrite module to log what its doing (if it can) is the way to go, but I don’t know how or whether its possible in a hosted environment.

I’m running WordPress 2.0 on IIS 6.0, and had problems with not getting emails as well. Installing the wpPHPmailer plugin worked. Thanks for the help.

The solutions in the above posts by dieterich and Viper007Bond worked for me as well. (I’m running WordPress 2.0 under IIS). Thanks very much.

Thanks to your post, I just discovered that I have the same problem. For testing, you could change the Discussion options to always send an email when a comment is entered, and then just enter in comments.

I’ve recently gotten WordPress 2.0 working under IIS with permalinks. My blog article has all the details.

I found a better plugin that is more flexible (can change the # in the admin | options) menu. It is called Custom Query String