Search the FirstSpirit Knowledge Base
Hello,
I am using the <CMS_INPUT_TEXT quite a lot and set convertenties=standard to convert the special characters like ö ü ä to html spechial chars.
unfortunately this does not work 😐
Is there any help for me?
Thanks
Hello Christoph,
did you define a conversion rule for the appropriate template set?
Server and Project Configuration -> project properties -> template sets -> properties of the template sets
The conversion rule defined here should be used to convert the special characters.
Best regards,
Holger
Hi Holger,
The Templateset HTML has the conversion rule Unicode to HTML4 set. (this should to the trick as far as i know - and i can't find out why it is not)
Regards
Christoph
Hello Christoph,
so let us check the circumstances:
- which FirstSpirit version do you use?
- where do you use the CMS_INPUT_TEXT component?
- how do you define the output of the component?
- how do you check, if the conversion was done? [hint: e.g. the firefox reconverts the entities within the source code]
best regards,
Holger
Server-Version: 4.1.46.34485
input in a headline section template (and several others):
<CMS_INPUT_TEXT
name="st_headline"
convertEntities="standard"
hFill="no"
length="40"
maxInputLength="100"
noBreak="no"
useLanguages="no">
<LANGINFOS>
<LANGINFO lang="*" label="Überschrift:" description="Bitte geben Sie den Text ein"/>
</LANGINFOS>
</CMS_INPUT_TEXT>
output:
$CMS_VALUE(st_headline)$
Writing ä ö or ü does not result in &äuml; ... the output is the plain ä
Umlauts don't need to be escaped if you're using HTML4 with an UTF-8 recording. If you want to, you can always add them to the standard conversion rule or use a new one.
we are using an ISO encoding - so i need to convert.
-> i clicked around, changed configs on the server and set it back to normal and now it surprisingly works -> strange things
Thanks a lot
Clicking around doesn't help in my case by now.
Is there any hint for me? I have exactly the same problem in FS 4.2.454 and 4.2.484.
My tests have shown that this problem only in the link-templates occurs.
Please contact our helpdesk, referring to the internal issue-ID #134441