eZusrvey: how to have one question per page

Next topic

Author	Message
Gaetano Giunta	Tuesday 26 August 2008 10:03:34 am What would be the best way to achieve a survey presentation where the questions are given one per page - and the final result calculated only after the last question is answered? Hits-friendly webmasters would love to have that, but it looks like the current code is not structured for such a case... Ideas: - add a kind of question_id unordered param to the urls - store previous questions in either session or cookies, or - add hidden input fields for all previous questions to every page where a single question is displayed Principal Consultant International Business Member of the Community Project Board
Gaetano Giunta	Tuesday 26 August 2008 2:54:38 pm Related to the above request, it would be nice to have a fetch function to get the results of a survey taken from a given user id (for speed it would need an extra index on ezsurveyresult.survey_id + user_id). Plus some hooks to allow a "result calculation and display"... This way it can be used as a general-purpose "test" extension and not only for surveys Principal Consultant International Business Member of the Community Project Board

Author

Message

Tuesday 26 August 2008 10:03:34 am

What would be the best way to achieve a survey presentation where the questions are given one per page - and the final result calculated only after the last question is answered?

Hits-friendly webmasters would love to have that, but it looks like the current code is not structured for such a case...

Ideas:
- add a kind of question_id unordered param to the urls
- store previous questions in either session or cookies, or
- add hidden input fields for all previous questions to every page where a single question is displayed

Principal Consultant International Business
Member of the Community Project Board

Gaetano Giunta

Tuesday 26 August 2008 2:54:38 pm

Related to the above request, it would be nice to have a fetch function to get the results of a survey taken from a given user id (for speed it would need an extra index on ezsurveyresult.survey_id + user_id).
Plus some hooks to allow a "result calculation and display"...
This way it can be used as a general-purpose "test" extension and not only for surveys

Principal Consultant International Business
Member of the Community Project Board

eZ debug

Timing:	Jan 30 2025 19:50:48
Script start
Timing:	Jan 30 2025 19:50:48
Module start 'layout'
Timing:	Jan 30 2025 19:50:48
Module start 'content'
Timing:	Jan 30 2025 19:50:48
Module end 'content'
Timing:	Jan 30 2025 19:50:48
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.0058	588.2656	151.2266
Module start 'layout'	0.0058	0.0037	739.4922	220.7188
Module start 'content'	0.0095	0.0147	960.2109	997.8359
Module end 'content'	0.0242	0.0026	1,958.0469	29.9922
Script end	0.0267		1,988.0391

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0037	13.9572	14	0.0003
Check MTime	0.0018	6.6025	14	0.0001
Mysql Total
Database connection	0.0010	3.6106	1	0.0010
Mysqli_queries	0.0018	6.8304	3	0.0006
Looping result	0.0000	0.0409	1	0.0000
Template Total	0.0013	4.8	1	0.0013
Template load	0.0010	3.8830	1	0.0010
Template processing	0.0003	0.9454	1	0.0003
Override
Cache load	0.0008	2.8076	1	0.0008
General
dbfile	0.0018	6.6497	8	0.0002
String conversion	0.0000	0.0223	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