Thread

Hi,

I’m experiencing the exact same problem here:

http://ellislab.com/forums/viewthread/199671/

I have limited ability to troubleshoot (I just have access to the EE CP and templates), so there’s not much I can do except share more details on other problems I’m finding that I suspect is caused by the same issue that’s breaking the search module.  Hopefully you can see my description of those issues and confirm exactly what the solution is:

- is running on 1.6.0, I cannot upgrade - limited access as I said, and client does not want to upgrade, they plan to revamp the site entirely in a cleaner, new EE environment

- am getting this error whenever changing admin settings or creating a new template (removing some directory names, leaving the important part):
Warning: Cannot modify header information - headers already sent by .../ee/index.php:2 in .../ee/core/core.functions.php on line 296
The changes do go into effect - ie., a new template is created, the admin settings change, this error is not interfering with my ability to make changes, it’s just spitting out this error message every time.

- when hitting the submit button on search form, it redirects to the home page, with no search information in the URL and the homepage is completely blank.  For example, let’s say it’s on acme.com/search and redirect is set to acme.com/results/ but instead it’s going to acme.com/ and loading blank.  However, when we go to acme.com by itself, the homepage loads fine.

Hope these details will help pinpoint the exact problem so I can tell the client what to do on the server end. 

Thanks!

Elise

One more issue I forgot - debugging output is turned on and I see it in EE CP, but it’s not rendering on templates (front end).

Hi, Elise.

Double check that you really are logged in when you’re viewing the main site. It may be as simple as the difference between calling the page with or without wwww. in it.

Is there an .htaccess at play? Is this something that just started happening? What about extensions?

There is an .htaccess file, client insists that it’s not the problem.  He said no changes have been made to it.  However a server upgrade was done a little while ago, they have not told me what precisely the upgrades were, so I can’t really investigate specific potential conflicts.

My gut feeling is that new server updates - ie., a new version of PHP, may be interpreting the .htaccess commands a little differently. Or due to it being an outdated version of EE, a conflict with new version of server software.  It’s a little frustrating when I have limited ability to troubleshoot. 

Yes I -really- am logged in on front end when I am trying to view the output debugging.  Good suggestion, though about trying it with or without the www. - didn’t think of that, will try that.

The assignment is to troubleshoot the search results.  If I can get that working, client will be happy and we can forget about all the other issues.  They only care about the front end working for website visitors, everything else will be resolved with a clean, new site that we migrate to in the (hopefully near) future.

Any suggestions for hacking the search module files, tweaking the parameters, anything - would be appreciated.  Basically anything file related, I can troubleshoot.  Except the .htaccess, I can’t touch that, I can find it and post the commands that are in there for you to peruse, though, if you think that’ll help.  If there definitely is a problem there I can request that be fixed.

Ok, so to be clear, this:

- when hitting the submit button on search form, it redirects to the home page, with no search information in the URL and the homepage is completely blank.  For example, let’s say it’s on acme.com/search and redirect is set to acme.com/results/ but instead it’s going to acme.com/ and loading blank.  However, when we go to acme.com by itself, the homepage loads fine.

is what you need to focus on?

Can you post the entire contents of the .htaccess file?  We normally see this when ‘www’ is either forcibly added or removed as it causes a form mismatch.  If we can see the entire .htaccess file it may give us a clue into what is going on.

Thanks!

Hi,

Sorry for the delay in response—been a very busy week! (I changed the actual dir name to “dir” on line 2 below).

Here’s the htaccess contents:

RewriteEngine On
RewriteBase /dir

# Any file that exists on disk will be served directly
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d

# Otherwise map to EE index.php
RewriteRule ^(.*)/?$ index.php/$1 [L]

An update: they increased the memory size on PHP and that did not do the trick.  And I got permission to share links for you to see where the bug is - I wanted to respect their privacy until I got confirmation that they’re OK with it.

http://www.utexas.edu/cie/informalclasses
http://www.utexas.edu/cie/learn

Note: both search forms use different parameters, so it is not an embed where it is one instance of the code having the problem, but two different instances having the same problem.

I quickly created a not pretty test template where I copied the more complicated search code they’re using on the live pages above on top, and plain simple search code with minimal parameters at the bottom:
http://www.utexas.edu/cie/InformalClasses/test-search

You can see that all three instances of search have the same problem.

Hey Lisi -

If you temporarily remove .htaccess and add index.php back in - does the search form work?