Extra logic for a feedback form

Next topic

Author	Message
Ronan Limon Duparcmeur	Friday 02 April 2010 9:16:36 am After hitting my head against the wall and blowing off much steam on Twitter, I've finally been able to add some logic to what should have been a simple feedback form. For the record, here is my problem and how I solved it. One of our eZP-powered website features a simple feedback form. The catch ? Instead of sending an email, the submitted data has to be used to fill our CRM. This involves consuming a webservice, and thus some backend code. Since triggers aren't available on feedback forms (or, if they are, I just couldn't figure it out), we had to find another way. A custom module+action was out of question, so instead, we choose to add the extra logic in the feedback email template. So, basically, what we do is activate the sending of feedback emails (even though we don't want them), and in the overridden template for this email, we call a custom template operator. This operator, in turn, handles the call to the CRM's webservice. This is an ugly solution to a problem that shouldn't even exist in the first place. It may not be the best solution, but hey, at least the problem is solved for now.

Author

Message

Friday 02 April 2010 9:16:36 am

After hitting my head against the wall and blowing off much steam on Twitter, I've finally been able to add some logic to what should have been a simple feedback form. For the record, here is my problem and how I solved it.

One of our eZP-powered website features a simple feedback form. The catch ? Instead of sending an email, the submitted data has to be used to fill our CRM. This involves consuming a webservice, and thus some backend code.

Since triggers aren't available on feedback forms (or, if they are, I just couldn't figure it out), we had to find another way. A custom module+action was out of question, so instead, we choose to add the extra logic in the feedback email template.

So, basically, what we do is activate the sending of feedback emails (even though we don't want them), and in the overridden template for this email, we call a custom template operator. This operator, in turn, handles the call to the CRM's webservice.

This is an ugly solution to a problem that shouldn't even exist in the first place. It may not be the best solution, but hey, at least the problem is solved for now.

eZ debug

Timing:	Jan 18 2025 10:29:25
Script start
Timing:	Jan 18 2025 10:29:25
Module start 'layout'
Timing:	Jan 18 2025 10:29:25
Module start 'content'
Timing:	Jan 18 2025 10:29:26
Module end 'content'
Timing:	Jan 18 2025 10:29:26
Script end

Main resources:

Total runtime	0.9480 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.0052	587.9141	152.6250
Module start 'layout'	0.0052	0.0025	740.5391	39.4453
Module start 'content'	0.0077	0.9390	779.9844	401.1719
Module end 'content'	0.9467	0.0013	1,181.1563	8.1641
Script end	0.9480		1,189.3203

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0031	0.3264	16	0.0002
Check MTime	0.0012	0.1317	16	0.0001
Mysql Total
Database connection	0.0009	0.0942	1	0.0009
Mysqli_queries	0.9122	96.2255	46	0.0198
Looping result	0.0004	0.0448	44	0.0000
Template Total	0.9194	97.0	2	0.4597
Template load	0.0022	0.2278	2	0.0011
Template processing	0.9172	96.7565	2	0.4586
Template load and register function	0.0003	0.0286	1	0.0003
states
state_id_array	0.0007	0.0768	1	0.0007
state_identifier_array	0.0008	0.0851	2	0.0004
Override
Cache load	0.0018	0.1859	9	0.0002
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0622	1	0.0006
Fetch class attribute name	0.0015	0.1538	1	0.0015
XML
Image XML parsing	0.0001	0.0153	1	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0009	1	0.0000
General
dbfile	0.0006	0.0629	10	0.0001
String conversion	0.0000	0.0007	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
2	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/strong.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/strong.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 6 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs