snubbr.com

Everytime I log into Myspace I get an Verisign SSL alert. Encryption algorithms...? HELP!?

Get a Verisign SSL certificate for 30 days FREE. Click here to use coupon...

Get a free trial of Verisign SSL certificates. Click here for this special deal...
My first question is Everytime I log into Myspace I get an Verisign SSL alert. Encryption algorithms...? HELP!? Looking forward for any answer or 2. Another question... Hi,.

I'm having some issues with the search function in my test shop and I would really like to have it working properly before launching..

First issue is when the keyword starts the products description with a Capital (as in Computer for gaming purposes ...) search does not return anything on 'computer'. However, if I search on 'omputer' I get the Computer as a result. Also, if I use a description like 'This computer is ...' I get a hit on computer as well. This seems to be a case sensitivity matter, but where to go from here?.

Second, I have figured out that quick find only(?) looks in products_model column of products table. This will not help the average user much since products_model are the part #'s of my shop items. The average user will probably not know what part # (s)he's searching for..

Trying to help up the situation a bit I enabled 'Search in description' as default so now we also search the product_description column of the products_description table (my conclusion)..

In my case this is not totally satisfying either since a lot of items are and will be described by their relations to other products in the shop, i.e 'This item will fit this unit and that unit'. As a result, a search on 'This item' also brings up 'this unit' and 'that unit' as well so the user will be presented a lot of irrelevant search results..

My conclusion is that the best way would be to search the products_name column in the products_description table since the items names are very relevant to their respective functions and probably very well recognised among the customers. Beeing a wrench head just tripping out in the binary world I started to look how this could be done, but I've come to a dead end understanding that because the product_name is defined as varchar(64) it cannot be searched (easily?).

Shop is 2.2rc2a on wamp server with utf8bin charset..

I would apreciate any help in any of the above matters, please be gentle since I'm a true beginner..

Comments (98)

That's a good question. I'm not sure what is the answer. I'll do some investigation and get back to you if I bump into an useful answer. You should email the people at Verisign as they probably could answer your Verisign question..

Comment #1

Just made some tests in phpadmin; LIKE%computer% returns any record with computer within the description, LIKE%Computer% returns any record.

Starting.

With capital [C]omputer in description..

So it is obviously case sensitive. Charset is when setting up the db was chosen to be utf8_bin, localhost has xp os in swedish, if that makes any sense ....

Quick search or quick find or whatever, is the box in the left column. Result is the same even with advanced search...

Comment #2

Take the input "Computer" and make sure to change it to lower case "computer" before the database search is started..

Add.

$search_keywords = strtolower($search_keywords);.

Before this.

If (isset($search_keywords) && (sizeof($search_keywords) > 0)) {.

Something like that MIGHT work...

Comment #3

Burt is a wise man!.

Still seems weird, but we atleast have located it as a database "problem"..

My database use latin1_swedish_ci, so you could try creating an "test" table with that charset to see if the problem is located within utf8_bin?..

Comment #4

Burt, I made the mod per your advice in advanced_search.php, the result were hits on every item in the db ....

I may have to point out that the search result in phpadmin differs from the result in my shop, the shop does not return anything when keyword has a starting capital..

Can I change charset on the existing db? It is still a test setup and I (of course) have backups to restore very easily if needed..

Comment #5

Ah well, try the strtolower elsewhere..

As this doesn't (appear to) happen in any other osCommerce shop, suggests to me that you have non-standard codebase - what changes have you made to your shop, or is this a template?..

Comment #6

Wex, you tempted me to go ahead a little so I exported the db just in case, changed charset to utf8_swedish_ci and now I get relevant results both when looking in descreption and when not (i.e. select from product_name seems to work). Neither search is case sensitive, so thats' also good.

As I said, I'm a newbie with a lot to learn. Thanks to both of you!..

Comment #7

Ah, that's interesting about the charset. Good work for getting it sorted anyway...

Comment #8

Burt, when browsing for a crasch course on the subject I have found out that there is more to it. Charset could (should?) be set on server level, db level or table level depending on needs and application..

Of course this makes sense in general to me, but I'm not able to sort out exactly how it works. Anyone who feels for it may step forward and explain the basics to me with regards to osC.

What I did was to change charset on table level, i.e products_description and products_name in products_description table, maybe this should have been done at db level instead..

Also, I wonder if the charset is optimal since I may have visitors from other Scandinavian countries like Denmark or Norway .....

Comment #9

Hi,.

I'm having some issues with the search function in my test shop and I would really like to have it working properly before launching..

First issue is when the keyword starts the products description with a Capital (as in Computer for gaming purposes ...) search does not return anything on 'computer'. However, if I search on 'omputer' I get the Computer as a result. Also, if I use a description like 'This computer is ...' I get a hit on computer as well. This seems to be a case sensitivity matter, but where to go from here?.

Second, I have figured out that quick find only(?) looks in products_model column of products table. This will not help the average user much since products_model are the part #'s of my shop items. The average user will probably not know what part # (s)he's searching for..

Trying to help up the situation a bit I enabled 'Search in description' as default so now we also search the product_description column of the products_description table (my conclusion)..

In my case this is not totally satisfying either since a lot of items are and will be described by their relations to other products in the shop, i.e 'This item will fit this unit and that unit'. As a result, a search on 'This item' also brings up 'this unit' and 'that unit' as well so the user will be presented a lot of irrelevant search results..

My conclusion is that the best way would be to search the products_name column in the products_description table since the items names are very relevant to their respective functions and probably very well recognised among the customers. Beeing a wrench head just tripping out in the binary world I started to look how this could be done, but I've come to a dead end understanding that because the product_name is defined as varchar(64) it cannot be searched (easily?).

Shop is 2.2rc2a on wamp server with utf8bin charset..

I would apreciate any help in any of the above matters, please be gentle since I'm a true beginner..

Comment #10

Seems strange, test on my own shops and the "demo" shop here on Oscommerce..

All handled the capital without case sensivity..

Have you tried using the Phpmyadmin on your wamp server and do a LIKE %computer% - to see if it's the database/charset..

Where do you setup "Quick Search"? Seems to search product name/model/description/manafacturer here..

Comment #11


This question was taken from a support group/message board and re-posted here so others can learn from it.

 

Categories: Home | Diet & Weight Management | Vitamins & Supplements | Herbs & Cleansing |

Sexual Health | Medifast Support | Nutrisystem Support | Medifast Questions |

Web Hosting | Web Hosts | Website Hosting | Hosting |

Web Hosting | GoDaddy | Digital Cameras | Best WebHosts |

Web Hosting FAQ | Web Hosts FAQ | Hosting FAQ | Hosting Group |

Hosting Questions | Camera Tips | Best Cameras To Buy | Best Cameras This Year |

Camera Q-A | Digital Cameras Q-A | Camera Forum | Nov 2010 - Cameras |

Oct 2010 - Cameras | Oct 2010 - DSLRs | Oct 2010 - Camera Tips | Sep 2010 - Cameras |

Sep 2010 - DSLRS | Sep 2010 - Camera Tips | Aug 2010 - Cameras | Aug 2010 - DSLR Tips |

Aug 2010 - Camera Tips | July 2010 - Cameras | July 2010 - Nikon Cameras | July 2010 - Canon Cameras |

July 2010 - Pentax Cameras | Medifast Recipes | Medifast Recipes Tips | Medifast Recipes Strategies |

Medifast Recipes Experiences | Medifast Recipes Group | Medifast Recipes Forum | Medifast Support Strategies |

Medifast Support Experiences |

 

(C) Copyright 2010 All rights reserved.