Locking Object in content tree

Previous topic

Suggestions

Next topic

Author	Message
Gurudutt Verma	Friday 08 December 2006 4:36:12 am Hello, I guess we should make some kind of lock for each object, and after the object is locked then it will not be allowed to delete the node without unlocking it by admin. Any how it should be possible to edit the object. It is because several sites we are creating several nodes and in the template we use the node_id of several nodes, for e.g. top menu or contact info or left menu etc. In some cases where we have to use the node_id in template to fetch content or sub tree but after handingover the site to customer it is possible to delete those nodes and create newone, in that case the site dosen't works because of missing node_id in content tree. If we can lock such objects and add some info in text box why that is locked then that will be easier for future enhancement to developer and also to admin/editors to understand it why they can't delete that object and why it is locked. Also in admin interface all locked objects should display little different. I guess it is a future enhancement request.

Author

Message

Gurudutt Verma

Friday 08 December 2006 4:36:12 am

Hello,

I guess we should make some kind of lock for each object, and after
the object is locked then it will not be allowed to delete the node without
unlocking it by admin.

Any how it should be possible to edit the object.

It is because several sites we are creating several nodes and in the template
we use the node_id of several nodes, for e.g. top menu or contact info or left menu etc.

In some cases where we have to use the node_id in template to fetch content or
sub tree but after handingover the site to customer it is possible to delete
those nodes and create newone, in that case the site dosen't works because of
missing node_id in content tree.

If we can lock such objects and add some info in text box why that is locked
then that will be easier for future enhancement to developer and also to
admin/editors to understand it why they can't delete that object and why it is locked.

Also in admin interface all locked objects should display little different.

I guess it is a future enhancement request.

eZ debug

Timing:	Jan 18 2025 11:09:07
Script start
Timing:	Jan 18 2025 11:09:07
Module start 'layout'
Timing:	Jan 18 2025 11:09:07
Module start 'content'
Timing:	Jan 18 2025 11:09:07
Module end 'content'
Timing:	Jan 18 2025 11:09:07
Script end

Main resources:

Total runtime	0.5690 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.0075	587.9141	152.6250
Module start 'layout'	0.0075	0.0034	740.5391	39.4453
Module start 'content'	0.0109	0.5564	779.9844	443.3594
Module end 'content'	0.5673	0.0017	1,223.3438	8.1641
Script end	0.5690		1,231.5078

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	0.6167	16	0.0002
Check MTime	0.0016	0.2790	16	0.0001
Mysql Total
Database connection	0.0012	0.2097	1	0.0012
Mysqli_queries	0.5241	92.1089	46	0.0114
Looping result	0.0004	0.0745	44	0.0000
Template Total	0.5356	94.1	2	0.2678
Template load	0.0021	0.3717	2	0.0011
Template processing	0.5335	93.7578	2	0.2667
Template load and register function	0.0001	0.0225	1	0.0001
states
state_id_array	0.0016	0.2845	1	0.0016
state_identifier_array	0.0009	0.1635	2	0.0005
Override
Cache load	0.0017	0.3047	20	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0012	0.2113	1	0.0012
Fetch class attribute name	0.0007	0.1216	2	0.0003
XML
Image XML parsing	0.0005	0.0870	1	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0008	2	0.0000
General
dbfile	0.0008	0.1398	16	0.0000
String conversion	0.0000	0.0012	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/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
4	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 13 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs