Powerstore 3: nice � intsead of "é" when using accordion sidebar !

Hi Dani and Jason,

I purchased Powerstore 3 a few days ago and started today with testing the new beast from WA.

Powerstore 3 is a very interesting solution, much better and stable than Powerstore 2 as far as I’m running the tests!
To adapt this solution for using foreign accented characters (French and German), I have changed all the charset=utf-8 to charset=ISO-8859-1 and added <?php header('Content-type: text/html; charset=ISO-8859-1'); ?> to Products_Detail_Lookup.php to help Products_Detail.php to display the foreign characters accordingly when selecting either an option or a value (works fine !)
On the front end, the new accordion sidebar challenges a new minor problem in displaying the foreign characters:
If you issue a product search using the menu bar, the product displays fine like shown in slide 1. BUT if one selects e.g. JURISNEWS in the accordion sidebar , then the “é” are displayed with these lovely &#65533; (that I hate so much!!!). Please look at slide 2.
I noticed that the page is not refreshed entirely but only the variable data on the Products_Results page. If you are on another page and click on the accordion sidebar you are “redirected” to Product_Results BUT WITHOUT any changing of the URL in the browser address.
So this seems to lead to a script that point to Products_Results without going through the whole Products_Results page, thus bypassing the ISO-8859-1 character decoding/encoding and OF COURSE giving this nice &#65533; instead of “é”.
For your better understanding please take note that I created the database using UTF8 and UTF8_unicode_ci. The same for the tables and their content (I modified the db.sql accordingly prior to run the automated INSTALL which is a nice and well designed feature by WA. Congratulations).
Actually I test PW3 on my home PC (localhost), so there are no clues on my website at the moment.
May I request your legendary help to solve this MINOR problem quickly? Many thanks.
Dan

I am only able to reproduce the problem if I make the changes you mention of changing the charset to charset=ISO-8859-1, If I leave the charset as utf-8 the accented characters display correctly for me.


you should not need to change the character set being used. you may need to modify your database encoding type. make sure it is using latin1 as the encoding type.

Hi Jason,
You’re right. Keeping utf-8 doesn’t make a problem in this case.

But you get the trouble in the charts, especially the charts related to the products.
When using utf-8 the name “société” is stored like “société” in the database (also when using utf8 as the database and table charset and utf8_unicode_ci as the collation).

Because I need foreign dates (for a French and a German edition) I use mysql_query("SET lc_time_names = 'fr_FR'"); in the Products_Data_Chart1.php to get the French date as “fév 2010” instead of “Feb 2010” (English date). This of course disables the chart build up when you keep <?php echo "<" . "?xml version=\"1.0\" encoding=\"utf-8\" ?".">"; ?><!DOCTYPE wa_dwc SYSTEM "wa_dwc.dtd">. Therefore I have to use ISO-8859-1 in this declaration. But if using ISO-8859-1 here, the name “société” is displayed like “société” in the tooltips a.s.o.

SO I NEED TO USE ISO-8859-1 throughout all pages to store “société” as “société” in the database table Products.

So I need to resolve the character translation (encoding-decoding) in the Products_Result.php to avoid the &#65533; when selecting an option or value of a product. To me the problem sticks in the script used to refresh the data in Products_Result.

Please also take note that when using utf-8 in the pages the problem of displaying the product “société” in the receipt email sent to several European email providers and even on 1&1.com (WA recommends !!!!) remains and displays like “société”. If I use ISO-8859-1 in all pages then the problem is solved because “Société” is stored as “Société” in the database field !!!

So please try to replicate this situation using all the infos I gave in my past posts and you will see that using ISO-8859-1 is a MUST for Europeans .

Dani Chankhour solved recently one of my concerns in Products_Detail (in Products_Detail_Lookup) in Powerstore 2. I think he should also look at the present issue, because it’s very similar.
Best regards
Dan

try adding:
<?php header('Content-type: text/html; charset=ISO-8859-1'); ?>


at line 1 of the Templates/Main.dwt.php page.

Sorry Jason but it doesn't resolve the problem.
Your development team should have a closer look at the script that refreshes when you click on the accordion tab in the sidebar.
Dan

I have created a support ticket so we can look into this issue further.

To view and edit your support ticket, please log into your support history:
login.php