Hiding content classes and other conceptual info

Next topic

Author	Message
Tristan Koen	Thursday 12 June 2003 2:28:22 am From what I can tell of the ezPublish product, all objects that are created fall somewhere in the tree hierarchy below the root folder. I have a couple of questions on this though. 1. Are users on the system stored as part of this tree hierarchy? 2. If one were to create a user under a folder together with an article, what does this mean conceptually? Is this user the same as any other user created using the admin interface? 3. When creating new objects in the admin interface, it is possible to hide some of the classes from a particular user? For example, if I were to create an author class that I relate to articles using the "related object" attribute, I wouldn't want any users to be able to see or create instances of that class except for me. Also on systems with large numbers of user-defined classes, the dropdown list would become very large indeed. 4. Similar to (3). If I create some custom classes that are only to be used by a module extension, I don't want users to see or touch them. Can they be hidden? Any advice here will be appreciated.

Author

Message

Thursday 12 June 2003 2:28:22 am

From what I can tell of the ezPublish product, all objects that are created fall somewhere in the tree hierarchy below the root folder.
I have a couple of questions on this though.
1. Are users on the system stored as part of this tree hierarchy?
2. If one were to create a user under a folder together with an article, what does this mean conceptually? Is this user the same as any other user created using the admin interface?
3. When creating new objects in the admin interface, it is possible to hide some of the classes from a particular user? For example, if I were to create an author class that I relate to articles using the "related object" attribute, I wouldn't want any users to be able to see or create instances of that class except for me. Also on systems with large numbers of user-defined classes, the dropdown list would become very large indeed.
4. Similar to (3). If I create some custom classes that are only to be used by a module extension, I don't want users to see or touch them. Can they be hidden?

Any advice here will be appreciated.

eZ debug

Timing:	Jan 18 2025 11:15:52
Script start
Timing:	Jan 18 2025 11:15:52
Module start 'layout'
Timing:	Jan 18 2025 11:15:52
Module start 'content'
Timing:	Jan 18 2025 11:15:53
Module end 'content'
Timing:	Jan 18 2025 11:15:53
Script end

Main resources:

Total runtime	0.7585 sec
Peak memory usage	4,096.0000 KB
Database Queries	46

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0056	589.4922	152.6406
Module start 'layout'	0.0056	0.0038	742.1328	39.4766
Module start 'content'	0.0095	0.7472	781.6094	401.0859
Module end 'content'	0.7567	0.0017	1,182.6953	8.1250
Script end	0.7584		1,190.8203

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	0.3900	16	0.0002
Check MTime	0.0012	0.1583	16	0.0001
Mysql Total
Database connection	0.0009	0.1145	1	0.0009
Mysqli_queries	0.7215	95.1278	46	0.0157
Looping result	0.0004	0.0570	44	0.0000
Template Total	0.7233	95.4	2	0.3616
Template load	0.0025	0.3237	2	0.0012
Template processing	0.7208	95.0363	2	0.3604
Template load and register function	0.0002	0.0295	1	0.0002
states
state_id_array	0.0020	0.2592	1	0.0020
state_identifier_array	0.0010	0.1264	2	0.0005
Override
Cache load	0.0020	0.2674	10	0.0002
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0646	1	0.0005
Fetch class attribute name	0.0006	0.0802	1	0.0006
XML
Image XML parsing	0.0001	0.0119	1	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0009	1	0.0000
General
dbfile	0.0005	0.0717	10	0.0001
String conversion	0.0000	0.0014	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
1	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 5 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs