Contributed documentation problem

Next topic

Author	Message
Paul Forsyth	Thursday 27 March 2003 5:48:57 am Ive been trying to edit the article: http://ez.no/developer/ez_publish_3/documentation/ez_publish_3/howtos/getting_the_latest_ezpublish_source but am having problems with the xml text field. not sure if its something odd happening with my browser cache or theres perhaps a clash going on with the stylesheets used for the page or with the data field itself... The first funny is the initial heading value for 'Install'. When i edit it is set to 1. This turns out to be a regular sized heading, which is blue. I change the value to 2, which is what the other headings are set, which are black, to but find after I post that the value has reverted back to 1... Looking at the source it seems a heading value of 1 is actually a h2 and 2 is h3. Im not clear on how to get proper spaces working with the literal tag. The gap from the text above it seems to large. Is there a way to position better from within a xml data field? Have a look and see what you can do with the article. Im a little stumped. Paul
Jan Borsodi	Thursday 03 April 2003 3:02:01 am The XML format is designed with content in mind, this means that there is no direct mapping between an XML header and an HTML header. Our default templates has this but on ez.no for instance the <h2> tag is used for header level 1. If you wanted you could render level 1 as bold, level 2 as italic and level 3 with texttoimage. This also means that you cannot skip levels, ie going from 1 to 3. When writing documentation you should think about the structure of the document instead of it's appearance. If you feel that the current setup of the tags leaves too much space then ofcourse we can adjust that. -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq
krish harry	Monday 26 May 2003 11:02:20 am Why skipping one level is not possible? If we directly want to use <h3> in the heads why we have to use <h1> and <h2> also in the document? Or have i misunderstood?
Karsten Jennissen	Monday 26 May 2003 11:55:59 pm I think that's XHTML standard. First use h1, then h2, then h3.
Paul Borgermans	Tuesday 27 May 2003 1:41:51 am For this discussion, xhtml is just html xml-ized. What Jan means is that <header level=xx> is used to structure your text-writing, not formatting/layout. Lots of people have difficulties to adapt to the idea of separation between content and presentation. Me too sometimes. On the other hand, I think specifying a level=2 to start should be possible for certain situations like when having multiple articles forming a larger structure (book-like). That really makes sense to me. Any thoughts from the ez team on this? Paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
krish harry	Saturday 14 June 2003 5:31:27 am >The XML format is designed with content in mind, this means that there is >no direct mapping between an XML header and an HTML header. Our >default templates has this but on ez.no for instance the <h2> tag is used >for header level 1. How to map <h2> to header level 1 like you are doing above? I tried but did not find the required setting file. Tx. Krish
Paul Borgermans	Sunday 15 June 2003 1:11:43 am You should look in design/standard/templates/content/datatype/view/ezxmltags/header.tpl Changes are best performed in your own design/<siteaccess>/override directory structure of course --paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans

eZ debug

Timing:	Jan 18 2025 02:49:50
Script start
Timing:	Jan 18 2025 02:49:50
Module start 'layout'
Timing:	Jan 18 2025 02:49:50
Module start 'content'
Timing:	Jan 18 2025 02:49:51
Module end 'content'
Timing:	Jan 18 2025 02:49:51
Script end

Main resources:

Total runtime	0.6381 sec
Peak memory usage	4,096.0000 KB
Database Queries	75

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0057	589.0391	152.6250
Module start 'layout'	0.0057	0.0023	741.6641	39.4609
Module start 'content'	0.0080	0.6286	781.1250	691.9766
Module end 'content'	0.6366	0.0015	1,473.1016	16.1563
Script end	0.6380		1,489.2578

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.5096	16	0.0002
Check MTime	0.0013	0.2108	16	0.0001
Mysql Total
Database connection	0.0009	0.1487	1	0.0009
Mysqli_queries	0.5784	90.6441	75	0.0077
Looping result	0.0006	0.1017	73	0.0000
Template Total	0.6098	95.6	2	0.3049
Template load	0.0020	0.3138	2	0.0010
Template processing	0.6078	95.2591	2	0.3039
Template load and register function	0.0002	0.0354	1	0.0002
states
state_id_array	0.0009	0.1377	1	0.0009
state_identifier_array	0.0015	0.2302	2	0.0007
Override
Cache load	0.0017	0.2667	42	0.0000
Sytem overhead
Fetch class attribute can translate value	0.0007	0.1026	5	0.0001
Fetch class attribute name	0.0011	0.1766	9	0.0001
XML
Image XML parsing	0.0014	0.2174	5	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0031	10	0.0000
General
dbfile	0.0009	0.1338	24	0.0000
String conversion	0.0000	0.0011	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
7	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
8	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
3	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
4	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 24 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs