If you want to make Firefox your default browser start it up, go to tools > options, and under system defaults click the button 'check now' which will ask you if you want to make firefox your default browser.

Did you know that drupal will run with IIS as a web server?

Matt Farina
Geeks and God Co-Host
www.innovatingtomorrow.net
www.mattfarina.com

This has still not corrected the problem as Firefox was already the default browser. Every other link or internet program opens with Ff except when I am in WAMP and click on the localhost/phpmyadmin or anything else in there. Not sure what to do other than reinstall WAMP.

Really? IIS? Fascinating! But, why would you ever want to do that?

Microsoft gets a lot of grief for their products. But, more recent versions of IIS are not to shabby. The biggest problem would be setting up what's normally in the .htaccess file in IIS.

Yeah, I'm an apache fan. But, it's not the only solid system or way to go. :-)

Matt Farina
Geeks and God Co-Host
www.innovatingtomorrow.net
www.mattfarina.com

Win2003 and up IIS is fine if you are running MS type web apps. I have had no serious issues with it in a long time.

I would't run apps like Drupal on IIS just because there isn't enough support in the app communities to support non-LAMP infrastructures. It is possible to run Drupal in IIS form what I understand. I just wouldn't recommend it.

Shrop

I actually support servers running IIS. I know it isn't too bad IIS 6.0 and up. For open source packages and things that have a community backing, you really can't beat Apache.

I had a Drupal 4.7 install on IIS once. Can't remember why I did that at the time. It worked fairly well for what was needed, but I never did get clean URLs working right. There are many workarounds for the .htaccess problem, but I couldn't get one that worked without spending money. It doesn't matter now, because that working group was dissolved and the web site has been mothballed.

I also had a friend who tried to get 4.7 running on IIS and never could get past an obscure login bug. He ended up switching his hosting over to Linux before his site would even work.

Given the choice, I'll always run Drupal on Apache in the future.

I do have a pretty elaborate installation of the MovableType blog engine running on IIS with ActivePerl. That has worked pretty well since I set it up five years ago, but we're outgrowing the site, and it needs to be moved to Drupal. Unfortunately, that site also has a bunch of really old asp pages with hand-coded VBScript. The oldest ones still have a Microsoft Access database for their back-end. Those are not going to be fun to rewrite in PHP.

Micah

Hello!

Question regarding what version of WAMP to be using...

should I use the most up-to-date version of WAMP possible
OR
should I use a version of WAMP that includes the versions of PHP and MySQL that
are closest to the versions of my webhost (for when I move the Drupal install to my webhost)?

Is it important that my development versions of PHP and MySQL NOT be newer than those that are in use by my webhosting company?

Thanks for the input in advance!

Pastor Greg,

It's always best to match your production environment as closely as possible. That way you won't have any surprises when you try to go live with the site. The versions don't necessarily have to be exactly the same, but they should be pretty close.

Both Date module and ImageAPI may spring some surprises on you if the versions are too far apart, especially if your hosting provider is way behind on versions. Those are the only two I can think of, but there may be more. If you're planning to run Drupal 7, in which case the database dependencies may also be a factor.

Chances are you'll be fine, but incompatibilities are never fun to find when going live.

Micah