Evaluating eZ - couple questions

«

Previous topic

|

|

Next topic

»

Author	Message
Tom Dellaringa	Tuesday 18 May 2004 6:26:48 am Hi everyone, We're evaluating eZ Publish as a possible solution for an internal portal. Couple questions about the file uploading capabilities: 1. Is there any versioning of files? 2. Do the files merely get dumped into one central folder, or can you specify a file structure for uploads? Thanks Tom
Paul Borgermans	Tuesday 18 May 2004 7:08:39 am Hi Tom 1) Yes, older versions are preserved as long you do not hit the configurable version limit. 2) If you mean folder like: yes you can structure, but it is abstracted. eZ publish handles this for you. regards -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
Tom Dellaringa	Tuesday 18 May 2004 7:25:24 am Hm, so do we know what this configurable limit is? This portal would have quite a bit of content. What do you mean by abstract for the file system? Can I have a file upload widget in each section where I want files uploaded? I assume that way files would be in their proper places...
Paul Borgermans	Tuesday 18 May 2004 7:49:23 am >Hm, so do we know what this configurable limit is? This portal would have In priciple there are no limits and is a configurable in the content.ini file, defualt is: [VersionManagement] DefaultVersionHistoryLimit=10 VersionHistoryClass[1]=5 >quite a bit of content. What do you mean by abstract for the file system? All content is stored in a node tree, which is in certain aspects the equivalent of a hierarchical file system. However the relation between the location of a file in that node tree and where it is physically stored is maintained in the ez publish database. >Can I have a file upload widget in each section where I want files >uploaded? I assume that way files would be in their proper places... Yes, no problem. You can specify where the files should be in your widget (a small form in a template actually). See the docs for more. -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans

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 18 2025 19:23:43
Script start
Timing:	Jan 18 2025 19:23:44
Module start 'layout'
Timing:	Jan 18 2025 19:23:44
Module start 'content'
Timing:	Jan 18 2025 19:23:44
Module end 'content'
Timing:	Jan 18 2025 19:23:44
Script end

Main resources:

Total runtime	0.0176 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0065	589.0469	152.6250
Module start 'layout'	0.0065	0.0035	741.6719	39.4609
Module start 'content'	0.0100	0.0054	781.1328	93.3359
Module end 'content'	0.0154	0.0022	874.4688	34.3047
Script end	0.0175		908.7734

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	14.6893	14	0.0002
Check MTime	0.0011	6.5135	14	0.0001
Mysql Total
Database connection	0.0006	3.4657	1	0.0006
Mysqli_queries	0.0044	25.2819	3	0.0015
Looping result	0.0000	0.1425	1	0.0000
Template Total	0.0017	9.8	1	0.0017
Template load	0.0009	4.8607	1	0.0009
Template processing	0.0009	4.9001	1	0.0009
Override
Cache load	0.0006	3.4101	1	0.0006
General
dbfile	0.0003	1.9066	8	0.0000
String conversion	0.0000	0.0570	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs