jReviews Support Forum

Hi, the only thing I saw reading the Docs, KB, and forums was an article about checking server for iconv support, and uncommenting two lines in the xajax code.

Well, the lines are already commented, and I didn't do anything.

Heres the problem.
Seems that the hyphen and slash characters if used in a custom field cause no results to be returned.
So say you have a list of options in a select field
Option 1 Mike
Option 2 Tom
Option 3 Mary-Lou

If you do a search on this custom field, doesn't matter whether you choose Mike, Tom, or Mary-Lou, no results are found.

Any suggestions?  Besides not using - and /?

Just to add, don't seem to have the problem in the demo site, so maybe something wrong on the server/install side??

After some further investigation, I think its options with a space in them.
Although I can't duplicated the behavior on the demo site.

Sorry, just been a long and frustrating day, and nothing seems to be going right tonight.
Don't even seem to be able to login to the ticket system.

You should not have non characters as the option values. That is why there's a text and value fields for the options. If you use the click2add feature it should automatically strip some characters, but the list is not comprehensive. It is the value that is used for the search, not the text. You can see this if you enter something different for the value and click on the click2search link for the field.

I mean this:

Option1
Text   Value
Mike   mike123

The click2search link will show mike123 instead of Mike.

Not sure if that's any help though. Use the contact menu if you can't submit a ticket.

I think i've narrowed down the problem.

When adding new fields, the value is automatically formated. ie: lowercase, no spaces, special chars.

When you add an option from the admin backend, Nothing is done to what you enter in the value field.
From the front end some trimming is done, but white spaces was something I noticed didn't get Trimmed.

Seems like something that should be implemented, especially since the code must be somewhere.

Right, the changes in the frontend are mostly to account for what users in general might enter. Since you are the admin, you know what to do. But point taken.

However, white spaces don't need to be trimmed. This works fine on the demo site with select lists:

http://demo.reviewsforjoomla.com/reviews/list/movies/movies/jr_dvdactors,Audrey+Tautou/order/alpha/

I just confirmed that this is a bug with 1.2.07! :( I tried it on my local install and it doesn't work and the demo has not been upgraded yet.

I will find out where the problem is and post a temp fix here.

Ok, I think I have a fix for this. If you are having this problem, please submit a ticket for a replacement file to help me test it and make sure everything else search related still works with this fix.

I have upgraded my test environment and have also this adv search problem...

I know, If you want to test the new version you need to submit a ticket.

I can't create a ticket   :'(  I got an error in the client area when I click on submit a ticket:

ERROR: You do not have enough permissions to access this page. Please log in by entering your Email Address and Password.

try again now and if it doesn't work then use the contact menu at the top.

Thanks for the files but the search problem is still the same...
Example:

...option,com_jreviews/task,list/criteria,/jr_format,CD/order,alpha/Itemid,57/
Gives:

Your search did not return any results. Try adjusting your search values.

Click here to go back.