Impressions of ezp3 after 3 days of testing ...

Author Message

Volker Lenz

Monday 27 January 2003 4:02:54 pm

1. I tested with register_globals off and all worked fine. This is a remarkable security improvement in ezp3. Thanks a lot.

2. I took some time to become familiar with the new object model. No doubt, the redundancies of ezp2 have been eroded with great rigor. This is appealing. However, I think in one case the goal to achieve an object model as compact as possible has been driven a step too far: In the treatment of users and user groups as instances of "CONTENT". User accounts and user groups, having "draft" and "publishing" state buttons assigned to them on the admin console, are a funny thing in first stance, but irritating and annoying in the long run. I recommend to review this. I further think there should be no direct assignment of roles to individual user accounts. Instead I suggest to replace the still too UNIX-like concept of a "User Group" with an object pattern "User Profile". Instances of "User Profile" should then become the only entities carrying role assignments. And there should be a n:1-relation between users and such profiles. So we get back what we can do with a "user group", just by assigning the same pattern of roles (now as a permission profile) to a multitude of users. And what else should we need "groups" for, if not to attach or detach individual user accounts to (from) permission patterns ?

3. The new template engine is a powerful, but also a heavyweight tool. For people like me - familiar with the template rendering model of ezp2 - it's a major paradigm shift to swallow. Oops. For people familiar with putting tiny php-snippets into HTML-pages it looks like "yet another proprietary scripting language on top of php." Most of all i hope it becomes no serious obstacle for future approaches to strengthen the role of XSLT in rendering. Concerns like this have already been reported in this forum and I do share them. However, the template engine is a tool with thorough and intelligent design. It's much faster than the former template utility and suitably stable yet, as far as I see. So it's hard for me to find out whether I love it or not.

4. I still don't know how to customize policies in the admin console.

Summary: I like ezp3 and will move my new site to this crazy tool. See the outcome within the next 10 days, if I have not fallen into dispair with templates by then ;-)

Regards to you all out there.

Volker

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 30 2025 21:39:17
Script start
Timing: Jan 30 2025 21:39:17
Module start 'layout'
Timing: Jan 30 2025 21:39:17
Module start 'content'
Timing: Jan 30 2025 21:39:17
Module end 'content'
Timing: Jan 30 2025 21:39:17
Script end

Main resources:

Total runtime0.0235 sec
Peak memory usage6,144.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0044 588.3828151.2422
Module start 'layout' 0.00440.0031 739.6250220.7500
Module start 'content' 0.00750.0145 960.3750997.7734
Module end 'content' 0.02200.0015 1,958.148429.9922
Script end 0.0235  1,988.1406 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002611.1240140.0002
Check MTime0.00104.3591140.0001
Mysql Total
Database connection0.00052.114610.0005
Mysqli_queries0.00177.105830.0006
Looping result0.00000.034510.0000
Template Total0.00114.510.0011
Template load0.00083.353510.0008
Template processing0.00031.128310.0003
Override
Cache load0.00052.259710.0005
General
dbfile0.002811.927680.0004
String conversion0.00000.026440.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs