XML block, links and related objects

Previous topic

Suggestions

Next topic

Author	Message
Xavier Dutoit	Tuesday 03 October 2006 9:25:09 am Can the same object be related to the same node both as, say, link and attribute ? Otherwise, it looks like a nice improvement. I have another problem: when I add an image (upload new embedded), it creates a new node under media/image and create a (embedded) relation to the object I'm editing. So far, so good. However, when I delete the relation, it doesn't remove the object and I end up with lots of images/documents that aren't used anywhere, and I don't know which one are/aren't used. This can be really confusing, especially when most of the users don't know that uploading a document/image create a node under the media folder. Anyway of flagging the nodes created as related ones or make it easier to find these orphaneous ones ? http://www.sydesy.com

Author

Message

Xavier Dutoit

Tuesday 03 October 2006 9:25:09 am

Can the same object be related to the same node both as, say, link and attribute ?

Otherwise, it looks like a nice improvement.

I have another problem: when I add an image (upload new embedded), it creates a new node under media/image and create a (embedded) relation to the object I'm editing.

So far, so good.

However, when I delete the relation, it doesn't remove the object and I end up with lots of images/documents that aren't used anywhere, and I don't know which one are/aren't used.

This can be really confusing, especially when most of the users don't know that uploading a document/image create a node under the media folder.

Anyway of flagging the nodes created as related ones or make it easier to find these orphaneous ones ?

http://www.sydesy.com

eZ debug

Timing:	Jan 30 2025 21:34:15
Script start
Timing:	Jan 30 2025 21:34:15
Module start 'layout'
Timing:	Jan 30 2025 21:34:15
Module start 'content'
Timing:	Jan 30 2025 21:34:15
Module end 'content'
Timing:	Jan 30 2025 21:34:15
Script end

Main resources:

Total runtime	0.0268 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0060	588.6797	151.2109
Module start 'layout'	0.0060	0.0045	739.8906	221.1484
Module start 'content'	0.0105	0.0143	961.0391	998.0938
Module end 'content'	0.0248	0.0019	1,959.1328	29.9922
Script end	0.0267		1,989.1250

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	12.1009	14	0.0002
Check MTime	0.0012	4.6014	14	0.0001
Mysql Total
Database connection	0.0008	3.1012	1	0.0008
Mysqli_queries	0.0032	11.7739	3	0.0011
Looping result	0.0000	0.0517	1	0.0000
Template Total	0.0013	4.9	1	0.0013
Template load	0.0010	3.7328	1	0.0010
Template processing	0.0003	1.1733	1	0.0003
Override
Cache load	0.0007	2.4811	1	0.0007
General
dbfile	0.0004	1.3648	8	0.0000
String conversion	0.0000	0.0303	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