Please no more newness until reaching a stability

Next topic

Author	Message
Zoltan Szabo	Sunday 02 November 2003 10:24:24 am Some comments about 3.2-3. During the Summer (and Autumn) I had a bad feeling about eZp, that there is not exist a "new, but stable" version. I didn't want to begin to build my site with 2.2, because there were a lot of good things in 3. But I had to discover that the 3 series are in a "development" stage, even the "stable" versions. I always had to do some bug fixes manually, even in the new versions again and again. [Let me not to mention the things concerning to my beloved PostgreSQL... ] So I was very glad when I read that the eZp crew changed it's way and tried to make a "really stable" version. But my first impressions were not very fine. Maybe it's just the surface, but... Please give a grep ezcontentobject.section ezcontentobjecttreenode.php command in kernel/classes. Do you think that $filterField = 'ezcontentobject.section'; (twice) is not a typo? (The name of this field is section_id in the table...) I wrote a bug report about this for some weeks, but it remained the same in 3.2-2 and 3.2-3 too. Another one: For me the quality of the postgresql updates shows if it worth to change to this new version, or was it done precipitately, quickly. Usually postgresql is not as well maintained as mysql :( Is it a correct database update in 3.2-3? (This is the ONLY line in dbupdate-3.2-2-to-3.2-3.sql) UPDATE ezsite_data SET value='2' WHERE name='ezpublish-release'; Of course, it's not a serious bug, but in mysql it's fine (value='3'), and the posgresql side is motherless again. What is this AvailableEventTypes[]=event_ezpaynet in workflow.ini? And why can't I find a AvailableEventTypes[]=event_ezpublishontime line in it? I suggest you to release a 3.2-4 without any other changes but with a lot of bug fixes.
Paul Borgermans	Sunday 02 November 2003 12:47:44 pm From what I see, the 3.2-3 is there to weed out a pretty long list of critical bugfixes which was originally not planned at all (straight to 3.3 instead). Not everything was fixed according to my own priorities for 3.2-3 either. There are no new features, only bug fixes. I can imagine quite a few bugs did not receive the attention required, but I don't mind non-criticals are left out for now. (disclaimer, I don't know how postgress is faring) With respect to the overall state, for me it is only from 3.2 I feel it is on firsts steps out of the development stage and into maturity. Luckily, the development is not to stop with respect to fundamental missing features --- which can be even more annoying if you try to implement what you think should be obvious or trivial. The event types about paynet should not be there, that's part of some custom-contract work. The publishontime event indeed is missing in the basic workflow.ini (which should include all standard available types) Keep on bug-reporting, if possible with a fix. It's open source after all -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
Paul Borgermans	Monday 03 November 2003 2:08:22 pm Bumped on a nasty bug with ezmultiplexer (reported more than enough the past months), so forget fine grained workflow. Damn, delayed deployment until this gets fixed. -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans

Author

Message

Sunday 02 November 2003 10:24:24 am

Some comments about 3.2-3.

During the Summer (and Autumn) I had a bad feeling about eZp, that there is not exist a "new, but stable" version.
I didn't want to begin to build my site with 2.2, because there were a lot of good things in 3.
But I had to discover that the 3 series are in a "development" stage, even the "stable" versions.
I always had to do some bug fixes manually, even in the new versions again and again.
[Let me not to mention the things concerning to my beloved PostgreSQL... ]
So I was very glad when I read that the eZp crew changed it's way and tried to make a "really stable" version.

But my first impressions were not very fine. Maybe it's just the surface, but...

Please give a
grep ezcontentobject.section ezcontentobjecttreenode.php
command in kernel/classes.
Do you think that
$filterField = 'ezcontentobject.section';
(twice) is not a typo? (The name of this field is section_id in the table...)
I wrote a bug report about this for some weeks, but it remained the same in 3.2-2 and 3.2-3 too.

Another one:
For me the quality of the postgresql updates shows if it worth to change to this new version,
or was it done precipitately, quickly. Usually postgresql is not as well maintained as mysql :(
Is it a correct database update in 3.2-3? (This is the ONLY line in dbupdate-3.2-2-to-3.2-3.sql)
UPDATE ezsite_data SET value='2' WHERE name='ezpublish-release';

Of course, it's not a serious bug, but in mysql it's fine (value='3'),
and the posgresql side is motherless again.

What is this
AvailableEventTypes[]=event_ezpaynet
in workflow.ini? And why can't I find a
AvailableEventTypes[]=event_ezpublishontime
line in it?

I suggest you to release a 3.2-4 without any other changes but with a lot of bug fixes.

Paul Borgermans

Sunday 02 November 2003 12:47:44 pm

From what I see, the 3.2-3 is there to weed out a pretty long list of critical bugfixes which was originally not planned at all (straight to 3.3 instead). Not everything was fixed according to my own priorities for 3.2-3 either. There are no new features, only bug fixes.

I can imagine quite a few bugs did not receive the attention required, but I don't mind non-criticals are left out for now. (disclaimer, I don't know how postgress is faring)

With respect to the overall state, for me it is only from 3.2 I feel it is on firsts steps out of the development stage and into maturity. Luckily, the development is not to stop with respect to fundamental missing features --- which can be even more annoying if you try to implement what you think should be obvious or trivial.

The event types about paynet should not be there, that's part of some custom-contract work. The publishontime event indeed is missing in the basic workflow.ini (which should include all standard available types)

Keep on bug-reporting, if possible with a fix. It's open source after all

-paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Paul Borgermans

Monday 03 November 2003 2:08:22 pm

Bumped on a nasty bug with ezmultiplexer (reported more than enough the past months), so forget fine grained workflow. Damn, delayed deployment until this gets fixed.

-paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

eZ debug

Timing:	Jan 18 2025 15:04:40
Script start
Timing:	Jan 18 2025 15:04:40
Module start 'layout'
Timing:	Jan 18 2025 15:04:40
Module start 'content'
Timing:	Jan 18 2025 15:04:41
Module end 'content'
Timing:	Jan 18 2025 15:04:41
Script end

Main resources:

Total runtime	0.6528 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0052	588.0625	152.6406
Module start 'layout'	0.0052	0.0027	740.7031	39.4766
Module start 'content'	0.0078	0.6436	780.1797	547.6406
Module end 'content'	0.6515	0.0013	1,327.8203	12.1250
Script end	0.6528		1,339.9453

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.5210	16	0.0002
Check MTime	0.0015	0.2288	16	0.0001
Mysql Total
Database connection	0.0007	0.1129	1	0.0007
Mysqli_queries	0.6017	92.1668	57	0.0106
Looping result	0.0005	0.0711	55	0.0000
Template Total	0.6241	95.6	2	0.3121
Template load	0.0021	0.3287	2	0.0011
Template processing	0.6220	95.2728	2	0.3110
Template load and register function	0.0002	0.0241	1	0.0002
states
state_id_array	0.0014	0.2181	1	0.0014
state_identifier_array	0.0012	0.1774	2	0.0006
Override
Cache load	0.0018	0.2826	43	0.0000
Sytem overhead
Fetch class attribute can translate value	0.0008	0.1155	2	0.0004
Fetch class attribute name	0.0010	0.1541	4	0.0003
XML
Image XML parsing	0.0007	0.1025	2	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0020	5	0.0000
General
dbfile	0.0008	0.1238	17	0.0000
String conversion	0.0000	0.0010	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
3	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
5	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 20 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs