A MOVE function

Next topic

Author	Message
Tonny Laursen	Wednesday 21 January 2004 11:28:16 am It would be nice if there could be an easy way to move e.g. articles, pictures and so on from one folder to another. Tonny
Marco Zinn	Wednesday 21 January 2004 12:38:13 pm What is wrong with the current "move"-Function? Marco http://www.hyperroad-design.com
Alex Jones	Wednesday 21 January 2004 1:18:00 pm While I cannot speak for Tonny, I think it would be nice to have the capability to move and/or add locations to multiple articles at one time. Alex Alex [ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ] <i>When in doubt, clear the cache.</i>
Tonny Laursen	Wednesday 21 January 2004 10:35:12 pm It would be nice, if it was possible to select an article or multiple, click on a "move"button and then select the new location (in the admin interface). The reason why I want this is because that at the end of every year we have to move a lot of aticles to a archive folder.
Balazs Halasy	Thursday 22 January 2004 12:44:34 am Hi, I guess massive move is not 100% supported from within the admin interface. However, archiving could be easily solved by setting up a workflow that goes through your articles and moves old ones to an archive folder. Balazs
Zoltan Szabo	Thursday 22 January 2004 1:42:34 am I have a similar problem with "Add location". A would like to create a "link" to a folder somewhere, but it's not possible ( not even in demo.ezpublish.no site ) - "Add Location" copies only the folder, but not the children. Can anyone describe the way of creating a workflow (as a "workaround" ) that copies time by time the children of a folder to another folder?

eZ debug

Timing:	Jan 18 2025 15:10:37
Script start
Timing:	Jan 18 2025 15:10:37
Module start 'layout'
Timing:	Jan 18 2025 15:10:37
Module start 'content'
Timing:	Jan 18 2025 15:10:38
Module end 'content'
Timing:	Jan 18 2025 15:10:38
Script end

Main resources:

Total runtime	0.9437 sec
Peak memory usage	4,096.0000 KB
Database Queries	72

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0052	588.9063	152.6094
Module start 'layout'	0.0052	0.0029	741.5156	39.4297
Module start 'content'	0.0081	0.9340	780.9453	675.8984
Module end 'content'	0.9421	0.0016	1,456.8438	12.5078
Script end	0.9437		1,469.3516

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.3347	16	0.0002
Check MTime	0.0013	0.1375	16	0.0001
Mysql Total
Database connection	0.0006	0.0666	1	0.0006
Mysqli_queries	0.8779	93.0219	72	0.0122
Looping result	0.0008	0.0819	70	0.0000
Template Total	0.9132	96.8	2	0.4566
Template load	0.0021	0.2193	2	0.0010
Template processing	0.9111	96.5461	2	0.4556
Template load and register function	0.0001	0.0145	1	0.0001
states
state_id_array	0.0008	0.0802	1	0.0008
state_identifier_array	0.0009	0.0970	2	0.0005
Override
Cache load	0.0019	0.2032	23	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0010	0.1066	5	0.0002
Fetch class attribute name	0.0021	0.2225	9	0.0002
XML
Image XML parsing	0.0019	0.2038	5	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0025	9	0.0000
General
dbfile	0.0011	0.1195	28	0.0000
String conversion	0.0000	0.0009	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
6	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
3	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 17 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs