Posted by gábor hojtsy on August 30, 2010 at 4:01pm
I've tried to stear the issue of web.config inclusion in D7 towards a D6 backport before, but people did not pick that up, and found other bugs. I've reopened http://drupal.org/node/567072 and would welcome your testing feedback. If you have issues with the D7 web.config (which I suspect can be used for D6 directly, no?), then we could even fix some D7 bugs. Your feedback is welcome.
Comments
Yes web.config should ship with all Drupal versions
I actually read this comment a couple of weeks ago and then there were several replies to the comment.
It took me some effort to get Drupal running satisfactorily under iis. One problem being getting clean urls to work and web.config is the key. But my view is that I shouldn't need to know this, I should be able to install Drupal and it should work out of the box.
It seems to me that the world of Drupal and the world of windows are like poppers frameworks with little overlap.
Windows practitioners are interested in getting their applications up running and getting revenue.
Drupal practitioners seem interested in how to get them up and running.
Me discovering I needed web.config to get the iis rewrite module to work properly wasted time and I would have rather it been a part of a package that loads Drupal onto a Windows platform without any intervention.
I'm absolutely of the mind that web.config be included in the standard Drupal package.
perfect
You are a perfect candidate then to help test the latest incarnations of web.config at http://drupal.org/node/567072, so we can ensure it works and contains best practice. It can only get in if it is well tested. Shipping with broken integration code is worse then shipping with none I'd say. Thanks for your help!
Here to help if I can
This coming week I've got to add a Drupal envornment to an MS SBS2008 installation that does not currently run PHP or SYSQL, so this could be a test bed for this exercise.
I know what I would like to see and that is that I run one single install script and the process runs through from beginning to end. At the start to allow the user to ask if they want a recommended configuration, a minimum configuration or a custom configuration. If the choose recommended then the process proceeds with no intervention.
This may not mesh with your goals, so....
Just tell me what you'd like me to do and what documentation I need to collect as I go through the process.
Let us know how it goes
Or let us know if you need any help.
Installing on a SBS should be the same as any Windows Server.
Thanks for the information.
Thanks for the information. It turned out to be something related to clean URLs and how that is run under IIS 6. I'm actually not in charge of the hosting environment, which means I would be of little help. I'd be happy to otherwise. I even have some of shared space and can at least put up something there.
Clean URL's on IIS 6 is different
Unfortunately it wasn't until we rewrote IIS 7 that Clean URLs' became easier. There is however some alternatives for Clean URL's in IIS 6. One of them is here. It's free and is open source and pretty much supports the .htaccess right out of the box. http://iirf.codeplex.com/ There's other ISAPI modules as well you can use certainly.
hope that helps.