Errata for released packages, please

Next topic

Author	Message
zurgutt -	Monday 15 September 2008 9:41:23 am I have just finished forum post about making the dynamic treemenu in the latest ezp release to work. One part of the solution is to download correct version of the file from svn, as the one in distribution apparently is broken. Most probably there are other things too in the distribution that are clearly broken. Why isn't there a errata document next to download file on download page listing those, and solutions?? It is a good tradition to do so. In this case I found that fact mentioned in a tiny script in middle part of upgrade instructions after hours of headbanging. It would be polite to have errata page prominently linked right next to download link, so thousands of users who download ezp would not have to waste massive amounts of time for tracking down major known bugs. Or at least enable commenting on download page. Certified eZ developer looking for projects. zurgutt at gg.ee
Heath	Monday 15 September 2008 11:06:12 pm <i>I have just finished forum post about making the dynamic treemenu in the latest ezp release to work. One part of the solution is to download correct version of the file from svn, as the one in distribution apparently is broken.</i> While it would be great to have this right away from the eZ Crew <i>Anyone</i> at or in <i>any time</i> can always can create and <i>preserve</i> documentation of this nature simply by creating an http://ezpedia.org documentation page. Forum posts are moderated, harder to locate and have a shorter half life than eZpedia documentation pages. <i>Most probably there are other things too in the distribution that are clearly broken. Why isn't there a errata document next to download file on download page listing those, and solutions?? It is a good tradition to do so. In this case I found that fact mentioned in a tiny script in middle part of upgrade instructions after hours of headbanging.</i> Perhaps eZpedia could support version specific documentation in a organized manner ... Cheers, Heath Brookins Consulting \| http://brookinsconsulting.com/ Certified \| http://auth.ez.no/certification/verify/380350 Solutions \| http://projects.ez.no/users/community/brookins_consulting eZpedia community documentation project \| http://ezpedia.org
Andrew Duck	Wednesday 17 September 2008 11:52:33 pm zurgutt I totally agree. Whilst eZpedia is a great resource and I believe that it could include such information, if you are shipping out 4.0.1 download packages then please notify people of issues like the dynamic treemenu. It is mentioned in the upgrade instructions... but why would you expect new users to even consider looking at the 4.0.x to 4.0.y upgrade instructions... I'm pretty sure those are prerequisite materials for a new installation. Errata documents associated to every release for new users would at least allow people to correctly install and configure eZ Publish, rather than resorting to the forums for support or worse still, giving up on eZ Publish and poorly reflecting to the community/product as a whole. Regards, Andrew. Andrew Duck, Executive Director, Quiqcorp Limited eZ Certified Developer and Trainer. Member of the Community Project Board http://quiqcorp.com \| http://twitter.com/andrewduck
André R.	Thursday 18 September 2008 12:36:43 am The treemenu issue is commented on the 4.0.1 news page as well, I agree that there should be some kind of link list of known issues next to the download link. But the treemenu is a bit of a chicken and egg issue, you won't be affected by the index_treemenu.php issue unless you fix your rewrite rules. eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom
zurgutt -	Tuesday 30 September 2008 1:17:39 am Adding the errata page is absolutely trivial (create page, enable commenting, link next to download link on download page). I would very much like to see some kind of authoritative statement from eZ crew about when the errata page will be added or a good argument about why users should be unaware about problems with release they download. Certified eZ developer looking for projects. zurgutt at gg.ee

eZ debug

Timing:	Jan 18 2025 04:30:18
Script start
Timing:	Jan 18 2025 04:30:18
Module start 'layout'
Timing:	Jan 18 2025 04:30:18
Module start 'content'
Timing:	Jan 18 2025 04:30:19
Module end 'content'
Timing:	Jan 18 2025 04:30:19
Script end

Main resources:

Total runtime	1.2503 sec
Peak memory usage	4,096.0000 KB
Database Queries	67

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0075	588.0156	152.6250
Module start 'layout'	0.0075	0.0043	740.6406	39.4453
Module start 'content'	0.0117	1.2371	780.0859	663.5469
Module end 'content'	1.2488	0.0015	1,443.6328	16.1563
Script end	1.2503		1,459.7891

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0036	0.2840	16	0.0002
Check MTime	0.0016	0.1266	16	0.0001
Mysql Total
Database connection	0.0010	0.0814	1	0.0010
Mysqli_queries	1.1767	94.1116	67	0.0176
Looping result	0.0007	0.0551	65	0.0000
Template Total	1.2174	97.4	2	0.6087
Template load	0.0037	0.2942	2	0.0018
Template processing	1.2137	97.0692	2	0.6068
Template load and register function	0.0001	0.0082	1	0.0001
states
state_id_array	0.0003	0.0218	1	0.0003
state_identifier_array	0.0011	0.0887	2	0.0006
Override
Cache load	0.0033	0.2613	34	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0012	0.0957	4	0.0003
Fetch class attribute name	0.0020	0.1616	9	0.0002
XML
Image XML parsing	0.0029	0.2312	4	0.0007
class_abstraction
Instantiating content class attribute	0.0000	0.0017	10	0.0000
General
dbfile	0.0012	0.0969	39	0.0000
String conversion	0.0000	0.0009	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
5	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
5	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
7	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	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: 21 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs