Recent changes to feature-requests

Apply css in embedded survey

Anonymous — Tue, 20 Jul 2010 20:06:16 -0000

phpESP allows you to modify appearance via css which can be selected at setup on the general tab. The styles defined are rendered when the survey is displayed via the URL given on Finish - i.e. via public/survey.php. However, when the survey is displayed via public/handler.php (and survey_render.inc) there does not seem to be any reference to the chosen style sheet, nor are the designs rendered. My request is that the css indicated at setup should be used for rendering the survey whether it be directly by URL or by embedding in a custom php.

Replace ereg_* functions (because they are deprecated)

Katalonian — Mon, 12 Jul 2010 07:24:51 -0000

I get an error in test.php :

phpESP Settings

* Loading phpESP.ini.php ...

Deprecated: Function ereg() is deprecated in D:\xampp\htdocs\adiu\phpESP\admin\include\lib\espauth.inc on line 13

Deprecated: Function ereg() is deprecated in D:\xampp\htdocs\adiu\phpESP\admin\include\lib\espauth.inc on line 16

Deprecated: Assigning the return value of new by reference is deprecated in D:\xampp\htdocs\adiu\phpESP\admin\include\lib\adodb\adodb-xmlschema03.inc.php on line 404

Deprecated: Assigning the return value of new by reference is deprecated in D:\xampp\htdocs\adiu\phpESP\admin\include\lib\adodb\adodb-xmlschema03.inc.php on line 416

And get error lines in header of manage.php (but all working)

Deprecated: Function ereg() is deprecated in D:\xampp\htdocs\adiu\phpESP\admin\include\lib\espauth.inc on line 13

Deprecated: Function ereg() is deprecated in D:\xampp\htdocs\adiu\phpESP\admin\include\lib\espauth.inc on line 16

Deprecated: Assigning the return value of new by reference is deprecated in D:\xampp\htdocs\adiu\phpESP\admin\include\lib\adodb\adodb-xmlschema03.inc.php on line 404

Deprecated: Assigning the return value of new by reference is deprecated in D:\xampp\htdocs\adiu\phpESP\admin\include\lib\adodb\adodb-xmlschema03.inc.php on line 416

Deprecated: Function ereg_replace() is deprecated in D:\xampp\htdocs\adiu\phpESP\admin\include\funcs.inc on line 35

Deprecated: Function ereg() is deprecated in D:\xampp\htdocs\adiu\phpESP\admin\include\funcs.inc on line 36

Deprecated: Function ereg_replace() is deprecated in D:\xampp\htdocs\adiu\phpESP\admin\include\funcs.inc on line 35

Deprecated: Function ereg() is deprecated in D:\xampp\htdocs\adiu\phpESP\admin\include\funcs.inc on line 36

Timed Survey

Anonymous — Mon, 15 Mar 2010 03:28:49 -0000

Can we have a timed survey for our users.
I need my user to fill survey in a specific time and they should be able to see the down timer on top of screen. It is somewhat like a test scenario, where respondent has to answer questions in a specific time.

duplicate survey name

Gurdeep Singh — Sun, 17 Jan 2010 20:32:15 -0000

multiple surveys cannot be created with a single name. > Now if multiple users access the tool then it is hard to create a new survey everytime with a unique name. It is an important usability aspect and it require solution.

Possible solution: If survey ID is appended to the newly created survey name automatically than it will give you a unique survey name itself.
or username can also be appended to keep the survey name unique.

Add Tool Tips

Anonymous — Fri, 20 Nov 2009 06:33:00 -0000

I think a great feature to add to each question as an option would be "Tool Tips" a pop up balloon giving you the capability
to type in support for an individual question. In my case I would have used it to put in a different language for each question...
Rather than having to make two separate surveys of one in each language, it would have been much easier to have
English as the primary survey and the tool tips to be in a secondary language.

-- Just a though

http://www.opensourcecms.com/

Anonymous — Wed, 23 Sep 2009 03:44:51 -0000

This is a great application. You should submit this product to OpenSourceCMS.com (http://www.opensourcecms.com/). They will host working demo versions of the latest release so people can try the product. The will also provide alink to your site for the download. Right now there is only one product on there that has 'survey' functionality and it isn't a dedicated survey product.

Display feedback for possible answer

bishop — Sat, 18 Apr 2009 01:27:44 -0000

In some circumstances (usually when "grading" a survey as an examination), the survey designer wants to provide feedback about the particular answer chosen. For example, consider this survey:

Title: "Are you ready to move to France?".
Question 1: "How much French do you speak?"
Possible Answers:
None
A few words
Conversational
Fluent

If the respondent selects "None", the survey designer wants to present some text impressing the importance of knowing French, perhaps with hyperlinks to resources on-line. But if the respondent selects "Conversational", the survey designer wants to tell them that they can move to France, but they need to improve their skill to take a professional position.

Or this survey:
Title: "All About the Moon"
Question 1: "The moon is made of..."
Possible Answers:
Rock
Cheese

If the respondent chooses rock, the feedback could be "That's right!". But if the respondent chooses cheese, the feedback could be "That's wrong!".

So, the scope of this ticket is to add feedback text to each possible answer, like (assuming SFID 2771716 completed):

LABEL CREDIT FEEDBACK
1. [_____________________] [____] [________________________________]
2. [_____________________] [____] [________________________________]
3. [_____________________] [____] [________________________________]
4. [_____________________] [____] [________________________________]
5. [_____________________] [____] [________________________________]
6. [_____________________] [____] [________________________________]
7. [_____________________] [____] [________________________________]
8. [_____________________] [____] [________________________________]
9. [_____________________] [____] [________________________________]
10. [_____________________] [____] [________________________________]

Note: The feedback may be either a text input or a text area; text area is preferred but space limitations on the UI may dictate a text input.

Feedback is shown at the next section break or end of survey, which ever comes first. So, if a survey has two sections with 10 questions in each section, then any feedback for the first 10 questions is shown between the 1st & 2nd section, and feedback for the last 10 questions is shown at the end of the survey.

Feedback is shown as follows:

This is the question that was asked?

Your Choice: The respondent chose this.
Feedback: This is the feedback entered for this possible answer.

If question numbering is engaged, the question number should appear in front of the question text.

If no feedback is entered for the respondent's selected choice, no feedback is shown. That is, the question, the choice and the feedback section are all omitted; this ensures visual backwards compatibility.

Allow possible answers to have associated "credit"

bishop — Sat, 18 Apr 2009 01:08:57 -0000

The core of phpESP functionality is "ask question, record answer." This
functionality applies to surveys ("tell me your opinion") and to
examinations ("tell me what you know").

However, examinations get graded, which means each possible answer contributes
numerically to an overall score. For example, say you have a 20 question exam
with a 100 point scale. Each question is worth 5 points. Some questions may
have a strictly right answer (credit=5), while the rest are strictly wrong
(credit=0). Other questions may have strictly right, partially right
(credit=4, 3, 2, or 1), and strictly wrong answers. The survey designer makes
these decisions when creating their examination.

The scope of this feature request is to add a "credit" value for each possible
answer in a question supporting possible answers (Yes/No, Radio, Checkbox,
Rate, etc.) This would be added as an additional column in the answer matrix
on the question definition of the survey creator. For every answer entry box,
there would be an entry box into which a number may be entered. This is the
response "credit". For example:

LABEL CREDIT
1. [_____________________] [____]
2. [_____________________] [____]
3. [_____________________] [____]
4. [_____________________] [____]
5. [_____________________] [____]
6. [_____________________] [____]
7. [_____________________] [____]
8. [_____________________] [____]
9. [_____________________] [____]
10. [_____________________] [____]

The "possible score" is the sum of the all maximum possible response credits.
For example, 20 questions, each with a maximum credit of 5, yields a "possible
score" of 100. Since the "possible score" is constant, it should be computed
and stored in the survey definition.

For a completed survey, the "score" is the sum of all specific response's credit.
For example, 20 questions, each with a maximum credit of 5, all strictly
right/strictly wrong questions, missing one would yield a "score" of 95.
Since this is constant once the response is marked as complete, store this in the
response definition.

Allow the admin to enter any numeric value, including negative and floating
point numbers. (Because we cannot predict exotic uses, we should be
maximally flexible.) Deny any value that is not numeric. Any question
without credits, or any question that does not make use of possible
answers, contributes nothing (that is, 0) to the score and possible score.

Show the score on the "thank you" page after completing a survey, as
"Score: N out of M (P%)". For example, "Score 95 out of 100 (95%)".

Also show the score on the "Navigate Individual Respondent Submissions" page,
at the top of the page, in the same format as for the thank you page.

Need ability for user to delete incomplete survey

kswartz — Mon, 09 Mar 2009 23:46:13 -0000

I've been making numerous enhancements to phpESP on my own (many of which I'm about to work on giving back), but I'm a bit stumped on how to move forward on this one, and would like some advice (in the absence of an actual fix).

We have a lengthy survey that may be filled out multiple times by our users. The survey has about 100 questions, and may be done over a period of a few days, while the respondent does some research.

We've found that occasionally, a user will want to scrap the survey completely, but still enter a new one. However, any time they sign in and try to start the survey, it always uses their saved one, and starts them where they left off.

We want to introduce the option to DELETE a saved-but-incomplete survey from the dashboard page. I'm up for working on this code myself, but need some advice. Is there a good way to securely reuse the code that does this in the admin pages? Unlike the admin pages, a user doesn't have to be a superuser to delete his OWN survey.

Right now, the workaround we have is to resume the saved survey, and hit the "Previous Page" button all the way back to page 1. Unfortunately, at 20 pages, that's a bit painful.

I am visualizing an additional column on the dashboard page, called "Action". It can show a link to delete a saved survey, OR a link to view (or edit, depending on whether the survey would support it) any previously submitted copies of the survey. That's a separate enhancement request; I just wanted to mention how I saw this one fitting into a bigger picture.

Cannot create conditions on questions with multiple answers

kswartz — Fri, 06 Mar 2009 21:40:17 -0000

Most conditions are based on radio buttons, but it's reasonable to expect that you may want to display questions according to selected checkboxes on a question that allows more than one answer.

For instance, if a question asks:

"What kind of vehicle(s) do you own?
[ ] Motorcycle
[ ] Car
[ ] SUV
[ ] Minivan
"

You may want to ask additional questions in a future section if they have a motorcycle, and other additional questions if they have a car.

The workaround is to split this up into separate questions and use Yes/No radio buttons. For example:

"Do you drive a motorcycle? () Yes () No
Do you drive a car? () Yes () No
...
"

This isn't necessarily a bad idea -- it may make reporting easier. But if you have a "checklist" of, say, ten items, this could make the survey considerably long by turning one question into ten.

The fix as I see it is to add a new conditional operation called "contains". For instance, you would say "Show question 42 is question 21 CONTAINS Motorcycle". The code fix is pretty easy:

1) if the response is an array, convert it to a comma-separated scalar (e.g.: "Motorcycle,Car,SUV"
2) perform your SQL query with LIKE '%$RESPONSE_VALUE%' in the where clause.