search

jeffcoughlin / farcrysolrpro

FarCry Solr Pro plugin Supports: Solr 3.5, FarCry 7.0+, 6.2+, 6.1.4+, 6.0.19+
http://jeffcoughlin.github.com/farcrysolrpro
Other
9 stars 8 forks source link

Server error occurs when searching using wildcards * or *:* #52

Closed tHeSmUrF closed 12 years ago

tHeSmUrF commented 12 years ago

When using the SOLRPro webskins on a FarCry 6.2 project and you enter a wildcard for the search (* or :) you get a server 500 error. If I have FarCry email errors to me, I get the following:

ERROR OVERVIEW Machine: WIFWC9 Instance: coldfusion Message: Element SPELLCHECK is undefined in STRESULT. Browser: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0) DateTime: {ts '2012-10-23 17:31:02'}

HTTPReferer:
QueryString: q=*&operator=any&lContentTypes=dmHTML&orderby=rank&objectid=185C0160-1CD9-11E2-A5330050569007A3 Bot: not a bot

ERROR DETAILS Exception Type: Expression Tag Context: * Q:\inetpub\Develop\FarCry_6\plugins\farcrysolrpro\packages\forms\solrProSearch.cfc (line: 136) * Q:\inetpub\Develop\FarCry_6\plugins\farcrysolrpro\webskin\solrProSearch\displaySearch.cfm (line: 67)

I was getting this same error in a project that has custom search pages but in the above I've created a brand new empty site and used the search pages from the plugin (v1.2.1)

seancoyne commented 12 years ago

Are you sure you're on v1.2.1? I ask because the stack trace and the lines in packages/forms/solrProSearch.cfc don't line up. I think I found the issue, but can you check? What is on line 136 in your copy?

seancoyne commented 12 years ago

@tHeSmUrF I just pushed up a fix to "master". Can you pull from git and let me know if it fixes the problem for you? I was able to recreate it so I'm sure it is fixed, but it's always good to get confirmation. If it does, I'll push out version 1.2.2.

tHeSmUrF commented 12 years ago

Sorry Sean, I've just realised why the line numbers wouldn't match. I had added a couple of lines earlier in the file to try and catch and log the error. Without my code it would have really been around line 118 - 120. Sorry about that.

I'll grab a new copy from git and test it very shortly.

tHeSmUrF commented 12 years ago

Hi Sean. The spellcheck error is now fixed with 1.2.2. Thank you!

seancoyne commented 12 years ago

Great, I'll push a new version out today