Forums / Setup & design / header level='3' gets formatted to header level='1' in xml text field
bisk
Monday 08 September 2003 3:28:32 am
Hi, I'm adding products and when I specify <header level='3'>a h3 header</header> in the description xml text field Exponential formats this to <header level='1'>a h3 header<header> after publishing. I don't want this as there are already h1 (pagetitle) and h2 (producttitle) tags on the page. So for a correct structure the next header tags which are in the description should be h3 tags and not h2.
Is there a way to fix this?
thanks :)
------------------------------- http://www.kookfijn.nl & http://www.magento.be
Bjørn Kaarstein
Monday 08 September 2003 4:42:47 am
This thread might help you.
http://ez.no/developer/ez_publish_3/forum/developer/contributed_documentation_problem
Seems like you have to override an ezxmltag.
Regards Bjørn
laurent le cadet
Monday 08 September 2003 5:10:57 am
I meet the same problem and I skip it when I need a <h2> first for example by wrinting empty tag. <header level="1"></header><header level="2>my texte</header>
It's not really "clean" but it works.
Hope this help.
Laurent
Monday 08 September 2003 6:40:26 am
Although I did a search on the forum, I didn't come across that thread. So thanks for the link Bjørn.
Laurent, I'll do an overrride to keep things clean ;)
Georg Franz
Tuesday 07 October 2003 1:42:16 am
Hi,
I think the "cleanest" solution is to create an own tag like "<subtitle>" to format the text as you like.
Kind regards,Emil.
Best wishes, Georg. -- http://www.schicksal.com Horoskop website which uses eZ Publish since 2004
Paul Forsyth
Tuesday 07 October 2003 2:18:30 am
Since we are using xml to write html is there a recommended way we do this? It seems a common occurence people fall into when first using ez.
The online editor simplifies this process a *lot* for end users but without it mistakes are easily made.
The documentation here:
http://ez.no/developer/ez_publish_3/documentation/customization/components/datatypes/ezxmltext/tags
mentions that the text processing is loosely based on xhtml 2.0. maybe there should be options for the xml field to determine which transformation will take place when the field is submitted to the xml parser. With this we would understand the mechanics better.
I believe Paul Borgermans and his team are working on things like this:
http://ez.no/developer/ez_publish_3/contributions/xslttemplate_operator
I should buy a decent xml book to learn all of the terminologies :)
Paul