Upgraded Low Search & EE - Now getting "Content Encoding Error" on Results Page
Using EE 2.5.4, Low Search 2.1.2
I've upgraded my EE and Low Search software and now our search results page no longer works. In Firefox we are getting:
Content Encoding Error
The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.
Help?? It was working fine before.
Replies
Dustin Hansen 20 Dec 2012 23:53
Solved.
It was not related to Low Search... it was a parsing issue with Stash.
Low 20 Dec 2012 23:56
A Google search implies that this might be a FireFox issue. Can you confirm this happens in FF only, not in any other browser?
Chad Crowell 7 Jun 2014 00:05
Hey Low - I am getting this in FF and Chrome. Works fine on my local but not on the dev server @ Liquidweb. Version 3.1.5 http://cl.ly/image/2I2t1h3q3j0i
Very simple form for testing: http://pastie.org/private/wmy5dhwnlc6...
Error only shows up on results page, with encoded segment_3 or query string. Also with EE's gzip setting on or off.
Any ideas?
Low 7 Jun 2014 07:55
Hmm, seems an environmental issue.
Can you try stripping the Results tag and adding the code bit by bit to try and find out which part triggers the issue?
Chad Crowell 9 Jun 2014 16:47
Hi Low - probably env yes. Striped down to this, with the same result:
{exp:low_search:results query="{segment_3}" limit="10"}
{/exp:low_search:results}
Low 10 Jun 2014 09:52
And if you remove the Results tag altogether? Does it still happen then?
Low 10 Jun 2014 09:57
Also, what happens if you choose not to encode the query, and use GET vars instead?
Chad Crowell 10 Jun 2014 15:27
Removing the results loop takes the problem away.
Changing to no encoding doesn't change anything - with the results loop its broken, without it, no error.
Low 10 Jun 2014 15:29
I'll need to take a look myself. Please send SuperAdmin and FTP login credentials to hi at gotolow dot com if you can.