|
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.
|