Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Advancend search results, url problem


Juto

Recommended Posts

Hi, The problem is that somehow the url for the search terms containing foreign characters gets encoded like so:

 

Searching for åäö gives

 

 

/advanced_search_result.php?search_in_description=1&keywords=%E5%E4%F6&x=8&y=11

 

which should have been

 

/advanced_search_result.php?search_in_description=1&keywords=åäö

 

I have googled and tried to find where to fix it, but no succes.

 

Anyone know something about this?

 

Thanks

 

Sara

Link to comment
Share on other sites

I'm no expert, but I thought the url is correct, just that you need to decode the keyword string before searching

KEEP CALM AND CARRY ON

I do not use the responsive bootstrap version since i coded my responsive version earlier, but i have bought every 28d of code package to support burts effort and keep this forum alive (albeit more like on life support).

So if you are still here ? What are you waiting for ?!

 

Find the most frequent unique errors to fix:

grep "PHP" php_error_log.txt | sed "s/^.* PHP/PHP/g" |grep "line" |sort | uniq -c | sort -r > counterrors.txt

Link to comment
Share on other sites

Hi Carine, yes you are correct. But where do the string get encoded? The db is in iso-8859-1 as well as the defines in the language files.

It's an RC2a shop, upgraded to 2.3.1 running php 5.3

Looking into advancend search results, there's this:

 

tep_db_input($keyword)

 

is it in that function?

 

Sara

Link to comment
Share on other sites

I suppose you need to call urldecode for $_GET['keywords']

 

googling on oscommerce url decode, you find this example:

 

http://phpxref.com/xref/oscommerce/catalog/includes/header.php.source.html#l72

KEEP CALM AND CARRY ON

I do not use the responsive bootstrap version since i coded my responsive version earlier, but i have bought every 28d of code package to support burts effort and keep this forum alive (albeit more like on life support).

So if you are still here ? What are you waiting for ?!

 

Find the most frequent unique errors to fix:

grep "PHP" php_error_log.txt | sed "s/^.* PHP/PHP/g" |grep "line" |sort | uniq -c | sort -r > counterrors.txt

Link to comment
Share on other sites

Goodmorning Carine and thanks for the link. Yes, I think that I have to as a last resort. Before that I will try to follow the search process to so what's happening and where.

I have look at keukenlust. It's a very nice site, I like it, and the index page is loading very fast despite all the images. Good work!

 

Sara

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...