17488 Posts in 4473 Topics by 1978 members
Page: 1 2
|Go to End||Next >|
16 May 2008 at 8:38pm
I'm building a German site - in German we have "Umlaute" (special signs) such as "ÃƒÂ¤ ÃƒÂ¶ ÃƒÂ¼ Ãƒâ€ž Ãƒâ€“ ÃƒÅ“ ÃƒÅ¸".
I want to integrate a Site Search. I followed the intstructions on the Tutorial and implemented the search.
Now I have the problem, that the Umlaut "ÃƒÂ¤", written as entity "ä" in the content gets re-escaped to &auml; when the search results are displayed - how can I overcome this problem that all ampersands (still those in entities too) get "escaped"?!
Can anyone please help me?!
17 May 2008 at 9:07pm
same problem, also by a sent newsletter - thanks for help
19 May 2008 at 10:18pm
so you've followed our search tutorial? http://doc.silverstripe.com/doku.php?id=tutorial:4-site-search
it outputs the content summary as $Content.LimitWordCountXML, which triggers Convert::raw2xml(). so far so good, no double htmlentities encoding. can you make sure the content is stored without being escaped into htmlentities?
as for the newsletter: we need more info, the source of the sent mails is helpful. i suspect you're sending unicode characters in a iso8859-1 (latin1) encoded mail.
5 June 2008 at 7:43am
if I useinstead of
$Content.LimitWordCountI get the correct Umlaute.
But in the database Content is stored escaped! Is this right?
...searches for words with Umlaute fail. How can I get this work?
5 June 2008 at 9:47am
hm database content is stored in utf8 (so don't be fooled by phpmyadmin giving you garbled output, its html encoding is mostly set to latin1).
can you try to get the sql-query thats generated (in SearchForm.php), append a COLLATE utf8 statement (see http://dev.mysql.com/doc/refman/5.1/en/charset-collate.html), and execute it manually? if it still doesn't work, can you post the query thats failing here? (-> http://pastie.caboo.se)
5 June 2008 at 5:28pm
No no, content is stored escaped (with html_entities I think)!
ist immer ein Kompromiß aus Funktionalität, Wirtschaftlichkeit und Sicherheit.
I started to work with 2.2.0 and updated last week to version 2.2.2!
What can I do now?
1 July 2008 at 3:07pm
Same problem, also by a searches for words with Umlaute fail.
How can I get this work?
20 July 2008 at 5:44am
I've got the same problem, so what can I do?
Page: 1 2
|Go to Top||Next >|