unusable with non-ASCII characters.

This is reproduceable on a Apache2 server with

* PHP Version 5.2.6
* MySql Server Version: 5.0.67

I don't know how often we, the clients, have urged WA to check for inconsistencies in their UTF-8 product - implementations. Because if this is not done correctly, all non US-ASCII characters are diplayed incorrectly or replaced by � characters, estimada Se�ora.
óíáñéúü¿ show up as ��������. Very funny.
Quel Hors d’�uvre. How come, wikipedia, vBulletin and countless others can display this correctly as Hors d’œuvre and Site Sculptor, PowerGallery ... can't?

All pages in Sitesculptor have correct UTF-8 settings:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

But in the moment we need content management, a key feature of Site Sculptor, chaos reigns. No idea how this could pass any quality control at web assist after so many months of claiming?

Database creation in Site Sculptor uses latin-1 collition! How can this work when each page is UTF-8 encoded?

It does not. It is the same with PowerGallery and maybe many other WA products which need foreign characters to be stored and retrieved in a mysql database.

Mysql and php even handles Chinese kanji character sets correctly if setup with UTF-8.
Kanji.

Sorry for putting all my frustration about this but its been simply too long that this was known and nothing was changed.

Currently support for the UTF characters and other high level ASCII characters is not available by default. To store this information in your db you will need to make updates to the encoding that is used for the db and table.

As you can see, the UTF-8 characters are correctly saved in the database. Why is the display incorrect on the public page as well as on the cms page?

Writing this is almost like posting in an open source forum with the difference that we all paid for this extension ...
Anyway.

After some tries I found a solution which works with UTF-8 as far as I checked it.
In the subdirectory /Connections there is the file "PowerCMSConnection.php" which contains the following code:

<?php
# FileName="Connection_php_mysql.htm"
# Type="MYSQL"
# HTTP="true"
$hostname_PowerCMSConnection = "myhost";
$database_PowerCMSConnection = "mydatabase";
$username_PowerCMSConnection = "myuser";
$password_PowerCMSConnection = "mypassword";
$PowerCMSConnection = mysql_pconnect($hostname_PowerCMSConnection, $username_PowerCMSConnection, $password_PowerCMSConnection) or trigger_error(mysql_error(),E_USER_ERROR);
// make sure UTF-8 is connected correctly
$result0 = mysql_query('SET NAMES utf8');
if (!$result0) {
die('invalid request: ' . mysql_error());
}
?>

It seems that "SET NAMES utf8" does the trick. What else needs to be done is changing all the wrong latin-1 collition settings in the database tables starting with "pcms2_" and wa_settings. Please tell me if I missed something.

Guys, could you fix this in an update?

PS.: Web-assist developers:
can you check your files in the /install/scripts/ folder?
db.sql file contains the latin1 settings

I hope this extension does not go up in price as it truly supports UTF-8 now ;-) since Eric wrote "Currently support for the UTF characters and other high level ASCII characters is not available by default."