Delete information collection

Previous topic

General

Next topic

Author	Message
Jens Kultima	Saturday 05 April 2008 3:46:53 am Dear all, <b>How do I, in a template, delete an information collection?</b> I could use the Admin-interface, but I have created a custom view for my collected information. Now I would like a "delete this" button. I don't understand how they have implemented the function in the admin-interface. Could anyone help? Thank you in advance! Regards, Jens
Xavier Gouley	Saturday 05 April 2008 10:58:40 am Hi, You have to follow this template, in the admin interface: design/admin/templates/infocollector/view.tpl This one does what you want, in the admin interface : see the form tag, and input tags : <form name="objects" method="post" action={concat( '/infocollector/collectionlist/', $collection.contentobject_id )\|ezurl}> <input class="button" type="submit" name="RemoveCollectionsButton" value="{'Remove'\|i18n( 'design/admin/infocollector/view' )}" title="{'Remove collection.'\|i18n( 'design/admin/infocollector/view' )}" /> <input type="hidden" name="CollectionIDArray[]" value="{$collection.id}" /> You just have to paste them in your template, and I think, add in appropriate roles (for users that can remove info collection in the front office), the infocollector module. When you click to this button, the next page that will be automatically loaded is the design/admin/templates/infocollector/confirmremoval.tpl : just look in this admin template, as for the first step, to retrieve form and input tags. This template shows a "confirm form". Copy this template in your front office design folder (to the same destination folder, and same name), and adapt it graphically (adapt HTML code, but not form and input tags). When you confirm in this second page, the collection is removed, but you will be redirected to: design/admin/templates/infocollector/collectionlist/{$objectID} page automatically, which generally does not exist in a front office. This page use the infocollector/collectionlist.tpl, so you can copy it (like previously), and make a redirection in this page, where you want, for example. I think this should work. If not, use the kernel/infocollector/collectionlist.php as a good model to make yourself a new module in an extension. Gook luck ! Xavier Gouley http://www.gxapplications.com/eng_blog/GX-Admin-s-Blog/

Author

Message

Jens Kultima

Saturday 05 April 2008 3:46:53 am

Dear all,

<b>How do I, in a template, delete an information collection?</b>

I could use the Admin-interface, but I have created a custom view for my collected information. Now I would like a "delete this" button.

I don't understand how they have implemented the function in the admin-interface.

Could anyone help?

Thank you in advance!
Regards,
Jens

Xavier Gouley

Saturday 05 April 2008 10:58:40 am

Hi,

You have to follow this template, in the admin interface: design/admin/templates/infocollector/view.tpl

This one does what you want, in the admin interface :
see the form tag, and input tags :

<form name="objects" method="post" action={concat( '/infocollector/collectionlist/', $collection.contentobject_id )|ezurl}>
<input class="button" type="submit" name="RemoveCollectionsButton" value="{'Remove'|i18n( 'design/admin/infocollector/view' )}" title="{'Remove collection.'|i18n( 'design/admin/infocollector/view' )}" />
<input type="hidden" name="CollectionIDArray[]" value="{$collection.id}" />

You just have to paste them in your template, and I think, add in appropriate roles (for users that can remove info collection in the front office), the infocollector module.

When you click to this button, the next page that will be automatically loaded is the design/admin/templates/infocollector/confirmremoval.tpl : just look in this admin template, as for the first step, to retrieve form and input tags. This template shows a "confirm form". Copy this template in your front office design folder (to the same destination folder, and same name), and adapt it graphically (adapt HTML code, but not form and input tags).
When you confirm in this second page, the collection is removed, but you will be redirected to: design/admin/templates/infocollector/collectionlist/{$objectID} page automatically, which generally does not exist in a front office. This page use the infocollector/collectionlist.tpl, so you can copy it (like previously), and make a redirection in this page, where you want, for example.

I think this should work. If not, use the kernel/infocollector/collectionlist.php as a good model to make yourself a new module in an extension.

Gook luck !

Xavier Gouley
http://www.gxapplications.com/eng_blog/GX-Admin-s-Blog/

eZ debug

Timing:	Jan 18 2025 18:31:47
Script start
Timing:	Jan 18 2025 18:31:47
Module start 'layout'
Timing:	Jan 18 2025 18:31:47
Module start 'content'
Timing:	Jan 18 2025 18:31:47
Module end 'content'
Timing:	Jan 18 2025 18:31:47
Script end

Main resources:

Total runtime	0.6477 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0057	587.9063	152.6250
Module start 'layout'	0.0057	0.0031	740.5313	39.4453
Module start 'content'	0.0089	0.6375	779.9766	529.5313
Module end 'content'	0.6463	0.0013	1,309.5078	12.1641
Script end	0.6476		1,321.6719

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.5172	16	0.0002
Check MTime	0.0013	0.2032	16	0.0001
Mysql Total
Database connection	0.0009	0.1354	1	0.0009
Mysqli_queries	0.6025	93.0349	54	0.0112
Looping result	0.0004	0.0662	52	0.0000
Template Total	0.6174	95.3	2	0.3087
Template load	0.0020	0.3153	2	0.0010
Template processing	0.6153	95.0060	2	0.3077
Template load and register function	0.0001	0.0193	1	0.0001
states
state_id_array	0.0009	0.1356	1	0.0009
state_identifier_array	0.0010	0.1550	2	0.0005
Override
Cache load	0.0017	0.2564	23	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0004	0.0647	2	0.0002
Fetch class attribute name	0.0008	0.1272	3	0.0003
XML
Image XML parsing	0.0027	0.4098	2	0.0013
class_abstraction
Instantiating content class attribute	0.0000	0.0010	3	0.0000
General
dbfile	0.0027	0.4135	16	0.0002
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
2	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/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 15 Number of unique templates used: 7

Time used to render debug report: 0.0001 secs