Share » Forums » Setup & design » HTML code is no longer interpreted

HTML code is no longer interpreted

HTML code is no longer interpreted

Friday 19 December 2008 2:24:53 am - 6 replies

Author Message

B. Nkengsong

Sunday 04 January 2009 10:30:29 am

Hello,

Can you be more clear ? Which editor do you use. ezoe4.x, ezoemce or FCKEditor ?

Br
Beegee

Sanagha Technologies Corp.
http://www.sanagha.com | http://www.sanagha.net | http://tourisphere.sanagha.net | http://education.sanagha.net
IT Consultant

Benjamin Lemoine

Wednesday 07 January 2009 3:02:40 am

Hello,

I'm using eZ Online Editor 4.2
And eZ Publish 3.9.2.

Benjamin Lemoine

Sunday 11 January 2009 11:34:11 pm

Please, can someone help me ?
I don't know what to do anymore ...

Marco Zinn

Monday 12 January 2009 11:56:24 am

Hi,

you write, that your settings/content.ini has this:

[literal]
AvailableClasses[]
# The class 'html' is disabled by default because it gives editors the
# possibility to insert html and javascript code in XML blocks.
# Don't enable the 'html' class unless you really trust all users who has
# privileges to edit objects containing XML blocks.
#AvailableClasses[]=html
CustomAttributes[]

If this is true, then try removing the # in the line AvailableClasses[]=html

Should be like this:

[literal]
AvailableClasses[]
# The class 'html' is disabled by default because it gives editors the
# possibility to insert html and javascript code in XML blocks.
# Don't enable the 'html' class unless you really trust all users who has
# privileges to edit objects containing XML blocks.
AvailableClasses[]=html
CustomAttributes[]

I guess, you did an update. Since some 3.x version, the HTML class has been disabled by default (as the comment says).

Marco
http://www.hyperroad-design.com

kracker (the)

The Doctor

Tuesday 13 January 2009 5:48:49 am

I also tried to reproduce this feature and only get the same response as <i>Benjamin Lemoine</i>

<i>grrr,
//kracker

Kanye West : Say you will ...</i>

Member since: 2001.07.13 || http://ezpedia.se7enx.com/

Benjamin Lemoine

Wednesday 14 January 2009 8:14:59 am

Hi
I finally solved my problem.
It wasn't due to settings/content.ini but to the extension "ezsh" (used to colorize literal text).
So the html tag wasn't interpreted.
I disabled the extension and everything came back to normal.

Thank you !

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu