I don't even know if this is strictly speaking a Drupal issue. We have a Drupal site where things appear to be running properly. We are in the process of moving the site to a new (Windows) server, which we have endeavored to make as much the same as the old server as possible, same versions of Windows, IIS, PHP, etc. Same database, which is not being moved. On the new site, search works fine from all pages EXCEPT the home page. On the home page, if you enter anything in the search field and submit, the home page is reloaded, rather than you being taken to the results page (i.e., /search/node/[search-term]). If we go to /home, which is an alias for the same home page as /, the search form works.

We switched back to the old server, where it continues to work properly from the home page (as well as all others) but cannot figure out what is different between the two servers.

Has anyone had anything like this? Any idea why the search form would behave differently on the web root (home page)?

--
Henry

Comments

jhodgdon’s picture

Status: Active » Fixed

It looks like you need some web server configuration support.

I'm sorry, but although you can create issues in Drupal Core and mark the category as "support request", we don't really handle support requests in the Drupal Core issue queue as a regular practice (that option is mostly there for filing support issues for contributed modules and themes).

There are several support options listed if you click on "Support" at the top of Drupal.org, which will take you to:
http://drupal.org/support

There you can find out about the Drupal IRC channels, and the Forums, which are our two main support mechanisms in the Drupal community. You might also try http://drupal.stackexchange.com/

Good luck with your issue!

ps: For debugging... You might try putting a different block on the Home page with a form submit in it and see if that works -- something like the user login block? But the Search block is unique in Drupal Core, because when it submits it actually redirects to a different URL. Maybe something in the Windows server config is preventing that redirect from happening? Anyway, good luck and please try a different support channel.

HenryHartley’s picture

Status: Fixed » Active

Thanks for your reply. Yes, I know posting this here was a long shot but we were having a tough time figuring it out and I though it worth the chance. I also suspected (and even said so) that this was a server configuration issue, not strictly a Drupal problem. Because we are running on a Windows server, a less widely used platform, there are fewer people who will run into this issue than if it were on LAMP. In any case, I'll post our findings here for future reference in case anyone else runs into the same issue (which IS a server configuration issue, for the record).

We changed the app pool’s .NET version to ‘No managed code’. It had been mistakenly set to v4.0 on the old production server and we carried it over to the new server. Some code handler must have been set differently on the old server allowing the code to work properly there. On the new server, we changed it from v4.0 to No Managed Code and the search form on the home page began working properly (with no other obvious change). I'm not sure why the .NET version would have any effect on PHP code, but clearly it did in some way. So, if you are running on IIS/Windows, set the .NET Framework to No Managed Code.

jhodgdon’s picture

Status: Active » Fixed

Updating this issue is a great idea in case someone else comes across the issue, but leaving it "active" isn't. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.