Again Cyrillic entries error

WebsiteBaker Support (2.10.x) > General Help & Support

<< < (3/4) > >>

rumen:
I took the language file from another site with Bakery which works. But there is no such raw there. I put the raw there and now it works (just should not have , and . in the fields) but works and again the same problem with the mail confirmation like before .... both e-mails not readable:

--- Code: ---Здравейте Румен Запрянов

Благодарим Ви за поръчката от El Tempo.
Ето детайли за вашата поръчка:

Номер: 0002
Име: Пилешка супа
Хляб: Без хляб
Количество: 1
Цена: BGN 2.90
Доставка: BGN 1.00
Сума: BGN 2.90

-------------------------------------
Междинен сбор: BGN 2.90
Цена за доставката: BGN 1.00
Inclusive 0.0% Данък: BGN 0.00
-------------------------------------
-------------------------------------
Общо: BGN 3.90
-------------------------------------

Поръчката ще бъде доставена на адрес:

Румен Запрянов
Бусманци ул Циклама 2
1520 София
София

+359876415004

Вие избрахте да платите при доставката на куриера.

Благодарим Ви за доверието в нас.

Поздрави,
El Tempo
--- End code ---

rumen:
Like here https://forum.WebsiteBaker.org/index.php/topic,30597.msg213299.html#msg213299 , but now all DataBase tables are UTF8 for sure.

rumen:
Is there a difference for WB if some of the tables are UTF8_unicode_ci other tables are UTF8_general_ci? Because they have difference!

Gast:

--- Quote ---just should not have , and . in the fields
--- End quote ---

you need comma and the point? - If YES, which kind of field

--- Quote ---again the same problem with the mail confirmation like before .... both e-mails not readable:
--- End quote ---

jau, thats not utf8, thats htmlspecialchars
was the problem solved in last time?

can you make a export from the database table mod_bakery_customer - i need only one complete order from there in sql-format.
i'll look to the way from the invoice from the buy-button into the database and from there to the email and the bakery administration

for a first try, go to view_confirmation.p hp ~ line 160ff

Original-Code

--- Code: ---// Make email headers
if (defined('DEFAULT_CHARSET')) {
$charset = DEFAULT_CHARSET;
} else {
$charset = 'utf-8';
}
--- End code ---

change it to

--- Code: ---$charset = 'utf-8';
--- End code ---

it's not longer needed to use if/else here, because there is only one charset possible, and this is utf8

i did not found any code to change the content from the invoice on the way into the email, so i think, you have the htmlspecialchars also in the database, but i have to build a russian bakery page with russion items and descriptions, to check this

--- Quote ---Is there a difference for WB if some of the tables are UTF8_unicode_ci other tables are UTF8_general_ci?
--- End quote ---

yes, a small different, but it doesn't matter, what you use. both works
_unicode_ci is the default setting for WB and _general_ci is the default setting in your database. if some module not submit this character set, the database use the selected charset & collation

Some description from Stackoverflow

--- Quote ---For any Unicode character set, operations performed using the _general_ci collation are faster than those for the _unicode_ci collation. For example, comparisons for the utf8_general_ci collation are faster, but slightly less correct, than comparisons for utf8_unicode_ci. The reason for this is that utf8_unicode_ci supports mappings such as expansions; that is, when one character compares as equal to combinations of other characters. For example, in German and some other languages “ß” is equal to “ss”. utf8_unicode_ci also supports contractions and ignorable characters. utf8_general_ci is a legacy collation that does not support expansions, contractions, or ignorable characters. It can make only one-to-one comparisons between characters.
--- End quote ---

you can also use utf8mb4_unicode_ci

change the line in your config.php like this

--- Code: ---define('DB_CHARSET', 'utf8mb4_unicode_ci');
--- End code ---

and start the upgrade-script. there is no risk, if you have all table with one of the utf8-characters like utf8mb4_unicode_ci, utf8mb4_general_ci, utf8_unicode_ci or utf8_general_ci

if you use emoticons in ckeditor, utf8mb4_......_ci is neccesary

rumen:
I have changed the code with:

--- Code: ---$charset = 'utf-8';
--- End code ---

But no effect at all, same error.

I sent you by mail the data.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version