Menu
▾
▴
phpesp-devel — Discussion of the development of phpESP
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
(103) |
Apr
(37) |
May
(45) |
Jun
(49) |
Jul
(55) |
Aug
(11) |
Sep
(47) |
Oct
(55) |
Nov
(47) |
Dec
(8) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(43) |
Feb
(85) |
Mar
(121) |
Apr
(37) |
May
(33) |
Jun
(33) |
Jul
(14) |
Aug
(34) |
Sep
(58) |
Oct
(68) |
Nov
(31) |
Dec
(9) |
| 2004 |
Jan
(13) |
Feb
(57) |
Mar
(37) |
Apr
(26) |
May
(57) |
Jun
(14) |
Jul
(8) |
Aug
(12) |
Sep
(32) |
Oct
(10) |
Nov
(7) |
Dec
(12) |
| 2005 |
Jan
(8) |
Feb
(25) |
Mar
(50) |
Apr
(20) |
May
(32) |
Jun
(20) |
Jul
(83) |
Aug
(25) |
Sep
(17) |
Oct
(14) |
Nov
(32) |
Dec
(27) |
| 2006 |
Jan
(24) |
Feb
(15) |
Mar
(46) |
Apr
(5) |
May
(6) |
Jun
(9) |
Jul
(12) |
Aug
(5) |
Sep
(7) |
Oct
(7) |
Nov
(4) |
Dec
(5) |
| 2007 |
Jan
(4) |
Feb
(1) |
Mar
(7) |
Apr
(3) |
May
(4) |
Jun
|
Jul
|
Aug
(2) |
Sep
(2) |
Oct
|
Nov
(22) |
Dec
(19) |
| 2008 |
Jan
(94) |
Feb
(19) |
Mar
(32) |
Apr
(46) |
May
(20) |
Jun
(10) |
Jul
(11) |
Aug
(20) |
Sep
(16) |
Oct
(12) |
Nov
(13) |
Dec
|
| 2009 |
Jan
|
Feb
(9) |
Mar
(37) |
Apr
(65) |
May
(15) |
Jun
|
Jul
(24) |
Aug
(1) |
Sep
(8) |
Oct
(4) |
Nov
(21) |
Dec
(5) |
| 2010 |
Jan
(35) |
Feb
(6) |
Mar
(8) |
Apr
|
May
(4) |
Jun
(3) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2009-07-24 09:25:25
|
Bugs item #2826093, was opened at 2009-07-23 18:59 Message generated for change (Comment added) made by liedekef You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2826093&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Admin Group: 2.1.2 >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: jordik (jordik) Assigned to: Franky Van Liedekerke (liedekef) Summary: changing status from test to active Initial Comment: if you change status from "test" to "active", the survey is marked "active" in the admin menues, but still is not accessible for the users i.e. still regared as not active if calling http://YOUR.SITE/public/survey.php?name=SURVEYNAME. If you change status from "edit" to "active", everything works alright. ---------------------------------------------------------------------- >Comment By: Franky Van Liedekerke (liedekef) Date: 2009-07-24 11:25 Message: ah ok, I believe it indeed was a problem in 2.1.1, but that's already old :-) So please upgrade to 2.1.3 and it will be fixed. Franky ---------------------------------------------------------------------- Comment By: jordik (jordik) Date: 2009-07-24 11:16 Message: I discovered in on my near-to-fresh-install of 2.1.1 and reproduced it in the demo install at http://phpesp.sourceforge.net/demo Didn't notice that there is already a new version, when I downloaded the version you get offered at http://sourceforge.net/projects/phpesp/ :-) I chose the wrong group in the tracker, though, I notice... *blush* ---------------------------------------------------------------------- Comment By: Franky Van Liedekerke (liedekef) Date: 2009-07-23 21:45 Message: I just tested this with 2.1.3 and can't reproduce this. Going from test to active works as expected. Franky ---------------------------------------------------------------------- Comment By: Franky Van Liedekerke (liedekef) Date: 2009-07-23 21:30 Message: Hmmm ... I remember this being a problem in the past. Are you sure this is version 2.1.2? Franky ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2826093&group_id=8956 |
|
From: SourceForge.net <no...@so...> - 2009-07-24 09:16:08
|
Bugs item #2826093, was opened at 2009-07-23 18:59 Message generated for change (Comment added) made by jordik You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2826093&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Admin Group: 2.1.2 Status: Open Resolution: None Priority: 5 Private: No Submitted By: jordik (jordik) Assigned to: Franky Van Liedekerke (liedekef) Summary: changing status from test to active Initial Comment: if you change status from "test" to "active", the survey is marked "active" in the admin menues, but still is not accessible for the users i.e. still regared as not active if calling http://YOUR.SITE/public/survey.php?name=SURVEYNAME. If you change status from "edit" to "active", everything works alright. ---------------------------------------------------------------------- >Comment By: jordik (jordik) Date: 2009-07-24 11:16 Message: I discovered in on my near-to-fresh-install of 2.1.1 and reproduced it in the demo install at http://phpesp.sourceforge.net/demo Didn't notice that there is already a new version, when I downloaded the version you get offered at http://sourceforge.net/projects/phpesp/ :-) I chose the wrong group in the tracker, though, I notice... *blush* ---------------------------------------------------------------------- Comment By: Franky Van Liedekerke (liedekef) Date: 2009-07-23 21:45 Message: I just tested this with 2.1.3 and can't reproduce this. Going from test to active works as expected. Franky ---------------------------------------------------------------------- Comment By: Franky Van Liedekerke (liedekef) Date: 2009-07-23 21:30 Message: Hmmm ... I remember this being a problem in the past. Are you sure this is version 2.1.2? Franky ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2826093&group_id=8956 |
|
From: SourceForge.net <no...@so...> - 2009-07-23 19:45:03
|
Bugs item #2826093, was opened at 2009-07-23 18:59 Message generated for change (Comment added) made by liedekef You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2826093&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Admin Group: 2.1.2 Status: Open Resolution: None Priority: 5 Private: No Submitted By: jordik (jordik) Assigned to: Franky Van Liedekerke (liedekef) Summary: changing status from test to active Initial Comment: if you change status from "test" to "active", the survey is marked "active" in the admin menues, but still is not accessible for the users i.e. still regared as not active if calling http://YOUR.SITE/public/survey.php?name=SURVEYNAME. If you change status from "edit" to "active", everything works alright. ---------------------------------------------------------------------- >Comment By: Franky Van Liedekerke (liedekef) Date: 2009-07-23 21:45 Message: I just tested this with 2.1.3 and can't reproduce this. Going from test to active works as expected. Franky ---------------------------------------------------------------------- Comment By: Franky Van Liedekerke (liedekef) Date: 2009-07-23 21:30 Message: Hmmm ... I remember this being a problem in the past. Are you sure this is version 2.1.2? Franky ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2826093&group_id=8956 |
|
From: SourceForge.net <no...@so...> - 2009-07-23 19:30:43
|
Bugs item #2826093, was opened at 2009-07-23 18:59 Message generated for change (Comment added) made by liedekef You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2826093&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Admin Group: 2.1.2 Status: Open Resolution: None Priority: 5 Private: No Submitted By: jordik (jordik) >Assigned to: Franky Van Liedekerke (liedekef) Summary: changing status from test to active Initial Comment: if you change status from "test" to "active", the survey is marked "active" in the admin menues, but still is not accessible for the users i.e. still regared as not active if calling http://YOUR.SITE/public/survey.php?name=SURVEYNAME. If you change status from "edit" to "active", everything works alright. ---------------------------------------------------------------------- >Comment By: Franky Van Liedekerke (liedekef) Date: 2009-07-23 21:30 Message: Hmmm ... I remember this being a problem in the past. Are you sure this is version 2.1.2? Franky ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2826093&group_id=8956 |
|
From: SourceForge.net <no...@so...> - 2009-07-23 16:59:04
|
Bugs item #2826093, was opened at 2009-07-23 18:59 Message generated for change (Tracker Item Submitted) made by jordik You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2826093&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Admin Group: 2.1.2 Status: Open Resolution: None Priority: 5 Private: No Submitted By: jordik (jordik) Assigned to: Nobody/Anonymous (nobody) Summary: changing status from test to active Initial Comment: if you change status from "test" to "active", the survey is marked "active" in the admin menues, but still is not accessible for the users i.e. still regared as not active if calling http://YOUR.SITE/public/survey.php?name=SURVEYNAME. If you change status from "edit" to "active", everything works alright. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2826093&group_id=8956 |
|
From: SourceForge.net <no...@so...> - 2009-05-29 18:59:34
|
Feature Requests item #2771716, was opened at 2009-04-17 21:08 Message generated for change (Comment added) made by bishopb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2771716&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: survey format Group: None Status: Closed Priority: 5 Private: No Submitted By: bishop (bishopb) Assigned to: bishop (bishopb) Summary: Allow possible answers to have associated "credit" Initial Comment: 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. ---------------------------------------------------------------------- >Comment By: bishop (bishopb) Date: 2009-05-29 14:59 Message: Thanks Franky! i'd like to note that the implementation differs from the requirements above, as follows: 1. The score is not cached in the response. 2. The respondent's score is not shown on the thank you page; however, the score is shown on each summary page, along with any feedback. 3. The score is not shown on the "Navigate Individual Respondent Submissions". 4. There is no concept of "total possible score". I decided not to implement these "admin" type features until further use cases present themselves. For example, instead of computing the total possible score as the sum of all credit, it may make sense to allow the admin to enter the total possible score on the survey definition page. Since there isn't any voting capability in SourceForge (AFAIK), anyone wishing to see particular functionality please comment in this ticket. ---------------------------------------------------------------------- Comment By: Franky Van Liedekerke (liedekef) Date: 2009-05-28 17:04 Message: nice work! Franky ---------------------------------------------------------------------- Comment By: bishop (bishopb) Date: 2009-05-28 14:55 Message: I have committed this to SVN. It will be publically available in the next release; anyone wanting a preview now should export the phpesp trunk. ---------------------------------------------------------------------- Comment By: bishop (bishopb) Date: 2009-05-28 10:45 Message: Revised design: only question types of radio buttons, check boxes, and dropdown box will be able to assign credit to possible answers. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2771716&group_id=8956 |
|
From: SourceForge.net <no...@so...> - 2009-05-28 21:04:13
|
Feature Requests item #2771716, was opened at 2009-04-18 03:08 Message generated for change (Comment added) made by liedekef You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2771716&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: survey format Group: None Status: Closed Priority: 5 Private: No Submitted By: bishop (bishopb) Assigned to: bishop (bishopb) Summary: Allow possible answers to have associated "credit" Initial Comment: 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. ---------------------------------------------------------------------- >Comment By: Franky Van Liedekerke (liedekef) Date: 2009-05-28 23:04 Message: nice work! Franky ---------------------------------------------------------------------- Comment By: bishop (bishopb) Date: 2009-05-28 20:55 Message: I have committed this to SVN. It will be publically available in the next release; anyone wanting a preview now should export the phpesp trunk. ---------------------------------------------------------------------- Comment By: bishop (bishopb) Date: 2009-05-28 16:45 Message: Revised design: only question types of radio buttons, check boxes, and dropdown box will be able to assign credit to possible answers. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2771716&group_id=8956 |
|
From: SourceForge.net <no...@so...> - 2009-05-28 18:56:09
|
Feature Requests item #2771716, was opened at 2009-04-17 21:08 Message generated for change (Settings changed) made by bishopb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2771716&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: survey format Group: None Status: Closed Priority: 5 Private: No Submitted By: bishop (bishopb) Assigned to: bishop (bishopb) Summary: Allow possible answers to have associated "credit" Initial Comment: 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. ---------------------------------------------------------------------- Comment By: bishop (bishopb) Date: 2009-05-28 14:55 Message: I have committed this to SVN. It will be publically available in the next release; anyone wanting a preview now should export the phpesp trunk. ---------------------------------------------------------------------- Comment By: bishop (bishopb) Date: 2009-05-28 10:45 Message: Revised design: only question types of radio buttons, check boxes, and dropdown box will be able to assign credit to possible answers. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2771716&group_id=8956 |
|
From: SourceForge.net <no...@so...> - 2009-05-28 18:55:55
|
Feature Requests item #2771716, was opened at 2009-04-17 21:08 Message generated for change (Comment added) made by bishopb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2771716&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: survey format Group: None >Status: Closed Priority: 5 Private: No Submitted By: bishop (bishopb) >Assigned to: bishop (bishopb) Summary: Allow possible answers to have associated "credit" Initial Comment: 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. ---------------------------------------------------------------------- >Comment By: bishop (bishopb) Date: 2009-05-28 14:55 Message: I have committed this to SVN. It will be publically available in the next release; anyone wanting a preview now should export the phpesp trunk. ---------------------------------------------------------------------- Comment By: bishop (bishopb) Date: 2009-05-28 10:45 Message: Revised design: only question types of radio buttons, check boxes, and dropdown box will be able to assign credit to possible answers. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2771716&group_id=8956 |
|
From: SourceForge.net <no...@so...> - 2009-05-28 14:45:47
|
Feature Requests item #2771716, was opened at 2009-04-17 21:08 Message generated for change (Comment added) made by bishopb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2771716&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: survey format Group: None Status: Open Priority: 5 Private: No Submitted By: bishop (bishopb) Assigned to: Nobody/Anonymous (nobody) Summary: Allow possible answers to have associated "credit" Initial Comment: 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. ---------------------------------------------------------------------- >Comment By: bishop (bishopb) Date: 2009-05-28 10:45 Message: Revised design: only question types of radio buttons, check boxes, and dropdown box will be able to assign credit to possible answers. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2771716&group_id=8956 |
|
From: SourceForge.net <no...@so...> - 2009-05-28 14:44:35
|
Feature Requests item #2771740, was opened at 2009-04-17 21:27 Message generated for change (Comment added) made by bishopb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2771740&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: survey format Group: None Status: Closed Priority: 5 Private: No Submitted By: bishop (bishopb) Assigned to: bishop (bishopb) Summary: Display feedback for possible answer Initial Comment: 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. ---------------------------------------------------------------------- >Comment By: bishop (bishopb) Date: 2009-05-28 10:44 Message: Clarification of implementation that's not mentioned in the design: feedback applies only to question types of: radio buttons, check boxes, and dropdown box. ---------------------------------------------------------------------- Comment By: bishop (bishopb) Date: 2009-05-27 21:46 Message: I have committed this to SVN. It will be publically available in the next release; anyone wanting a preview now should export the phpesp trunk. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2771740&group_id=8956 |
|
From: SourceForge.net <no...@so...> - 2009-05-28 01:46:39
|
Feature Requests item #2771740, was opened at 2009-04-17 21:27 Message generated for change (Comment added) made by bishopb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2771740&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: survey format Group: None >Status: Closed Priority: 5 Private: No Submitted By: bishop (bishopb) Assigned to: bishop (bishopb) Summary: Display feedback for possible answer Initial Comment: 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. ---------------------------------------------------------------------- >Comment By: bishop (bishopb) Date: 2009-05-27 21:46 Message: I have committed this to SVN. It will be publically available in the next release; anyone wanting a preview now should export the phpesp trunk. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2771740&group_id=8956 |
|
From: Bishop B. <ph...@id...> - 2009-05-08 11:32:40
|
Mat, I understand that you're a development house. However, to gain admin privileges you must demonstrate an interest and ability to work with the code, specifically by making modifications that are useful for the community. We consider that reasonable quality control. If you need the code in your own base, export out of SVN public and put into your own repository. Make changes there and post them to the list as patches. Once you've made a few solid changes, we can discuss elevating your privilege. Sincerely, bishop Quoting matin majtavi <ma...@gm...>: > hi i mean we are not about hosting, we developer and support and make things > happen but for us to help this project she needs to be part of trilex labs > as well, and the only way we would do it is for you to add us as a admin or > project manager with full privilege as well so we can know we are part of > this team as well > > Thanks > > Mat > > On Fri, May 8, 2009 at 5:55 AM, Bishop Bettini <ph...@id...> wrote: > >> Want to help out? Great! There's a list of 72 enhancement requests over >> at SourceForge: >> https://sourceforge.net/tracker/?atid=358956&group_id=8956&func=browse >> >> Pick some, make the patches against head, and send to the list! >> >> As for hosting, if it's not broken, why fix it? >> >> bishop >> >> >> Quoting Franky Van Liedekerke <lie...@te...>: >> >> Hi, >>> >>> I'm just continuing the project, sourcecode based ... I'm mailing this >>> to the developers list as well, so everybody who wants to react, >>> please do. >>> >>> Franky >>> >>> On Fri, May 8, 2009 at 11:36 AM, matin majtavi <ma...@gm...> wrote: >>> >>>> hi franky >>>> >>>> who controls phpESP then? anyone? Thanks for the fast reply. >>>> >>>> On Fri, May 8, 2009 at 5:24 AM, Franky Van Liedekerke < >>>> lie...@te...> >>>> wrote: >>>> >>>>> >>>>> On Thu, May 7, 2009 at 6:33 AM, Trilex Labs >>>>> <tri...@us...> wrote: >>>>> > >>>>> > Message body follows: >>>>> > >>>>> > My name is Mat, I am part of Group called Trilex Labs >>>>> > we do alot open source projects and help alot of open based >>>>> > projects too. Our team wanna help >>>>> > phpESP in hosting it plus developing it more and >>>>> > getting it closer to V3.0 plus in future the extend the >>>>> > project...Please let me know what you think so we can get >>>>> > started.. you can add to msn or live messnager >>>>> > ma...@tr... or if you have yahoo or something >>>>> > else I can add you to my list ... by the way my phone >>>>> > number is 416 427 1214 if you need to get in touch with me >>>>> > Thanks >>>>> >>>>> Hi Mat, >>>>> >>>>> thanks for the offer. For the moment we use sourceforge for our >>>>> project site. The real site needs changing (not under my control), but >>>>> I think it is best to keep the project on sourceforge. Of course you >>>>> can set up a demo at your site if you want (the one on sourceforge is >>>>> again not under my control). >>>>> And of course any contribution to the code is appreciated, as are >>>>> suggestions, etc ... >>>>> >>>>> Franky >>>>> >>>> >>>> >>>> >>>> -- >>>> Sincerley yours >>>> >>>> Mat >>>> >>>> >>>> >>> >>> ------------------------------------------------------------------------------ >>> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your >>> production scanning environment may not be a perfect world - but thanks to >>> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK >>> i700 >>> Series Scanner you'll get full speed at 300 dpi even with all image >>> processing features enabled. http://p.sf.net/sfu/kodak-com >>> _______________________________________________ >>> phpESP-devel mailing list >>> php...@li... >>> https://lists.sourceforge.net/lists/listinfo/phpesp-devel >>> >>> >> >> >> -- >> Bishop Bettini >> ideacode, Inc. >> (main) +1 919 341 5170 / (fax) +1 919 521 4100 >> >> Visit us on the web at: >> ideacode.com Professional software research and development >> reviewmysoftware.com Improve sales! Review your software before you >> release >> bytejar.com Solutions to those annoying development problems >> >> > > > -- > Sincerley yours > > Mat > -- Bishop Bettini ideacode, Inc. (main) +1 919 341 5170 / (fax) +1 919 521 4100 Visit us on the web at: ideacode.com Professional software research and development reviewmysoftware.com Improve sales! Review your software before you release bytejar.com Solutions to those annoying development problems |
|
From: Bishop B. <ph...@id...> - 2009-05-08 09:55:53
|
Want to help out? Great! There's a list of 72 enhancement requests over at SourceForge: https://sourceforge.net/tracker/?atid=358956&group_id=8956&func=browse Pick some, make the patches against head, and send to the list! As for hosting, if it's not broken, why fix it? bishop Quoting Franky Van Liedekerke <lie...@te...>: > Hi, > > I'm just continuing the project, sourcecode based ... I'm mailing this > to the developers list as well, so everybody who wants to react, > please do. > > Franky > > On Fri, May 8, 2009 at 11:36 AM, matin majtavi <ma...@gm...> wrote: >> hi franky >> >> who controls phpESP then? anyone? Thanks for the fast reply. >> >> On Fri, May 8, 2009 at 5:24 AM, Franky Van Liedekerke <lie...@te...> >> wrote: >>> >>> On Thu, May 7, 2009 at 6:33 AM, Trilex Labs >>> <tri...@us...> wrote: >>> > >>> > Message body follows: >>> > >>> > My name is Mat, I am part of Group called Trilex Labs >>> > we do alot open source projects and help alot of open based >>> > projects too. Our team wanna help >>> > phpESP in hosting it plus developing it more and >>> > getting it closer to V3.0 plus in future the extend the >>> > project...Please let me know what you think so we can get >>> > started.. you can add to msn or live messnager >>> > ma...@tr... or if you have yahoo or something >>> > else I can add you to my list ... by the way my phone >>> > number is 416 427 1214 if you need to get in touch with me >>> > Thanks >>> >>> Hi Mat, >>> >>> thanks for the offer. For the moment we use sourceforge for our >>> project site. The real site needs changing (not under my control), but >>> I think it is best to keep the project on sourceforge. Of course you >>> can set up a demo at your site if you want (the one on sourceforge is >>> again not under my control). >>> And of course any contribution to the code is appreciated, as are >>> suggestions, etc ... >>> >>> Franky >> >> >> >> -- >> Sincerley yours >> >> Mat >> >> > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > phpESP-devel mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpesp-devel > -- Bishop Bettini ideacode, Inc. (main) +1 919 341 5170 / (fax) +1 919 521 4100 Visit us on the web at: ideacode.com Professional software research and development reviewmysoftware.com Improve sales! Review your software before you release bytejar.com Solutions to those annoying development problems |
|
From: SourceForge.net <no...@so...> - 2009-05-08 09:48:41
|
Bugs item #1727902, was opened at 2007-05-29 16:38 Message generated for change (Settings changed) made by bishopb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=1727902&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Docs / FAQ Group: v1.8 Status: Closed Resolution: Accepted Priority: 5 Private: No Submitted By: Miguel (miguel2) Assigned to: Nobody/Anonymous (nobody) Summary: No Logon when mysql > 4.1 (hash lenght problem) Initial Comment: Today i could not login to phpESP even if i created a new user via phpmyadmin. I didnt login since a year. in the meantime the hoster upgraded to mysql 5. I investigated a bit and found that the lenght of the password hash created by the mysql function PASSWORD() has changed from 16bit to 41bit. (http://dev.mysql.com/doc/refman/5.0/en/password-hashing.html) You have to change the lenght of the password field in table designer to 41 ALTER TABLE `designer` CHANGE `password` `password` CHAR( 64 ) CHARACTER SET latin1 COLLATE latin1_swedish_ci NOT NULL ---------------------------------------------------------------------- Comment By: Franky Van Liedekerke (liedekef) Date: 2009-05-08 03:46 Message: Please don't do anonymous comments to a closed bug. Just upgrade to the latest version and this is fixed. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-05-07 23:50 Message: then how to solve it? ---------------------------------------------------------------------- Comment By: Franky Van Liedekerke (liedekef) Date: 2007-11-27 06:44 Message: Logged In: YES user_id=109671 Originator: NO Hi, I do consider this a phpesp issue as well, so I added these statements again to the next upgrade sql script, so everybody has the changes needed. Franky ---------------------------------------------------------------------- Comment By: Miguel (miguel2) Date: 2007-05-29 17:22 Message: Logged In: YES user_id=1346327 Originator: YES You are right. The sql statement in mysql_populate.sql is CREATE TABLE designer ( username CHAR(64) NOT NULL, password CHAR(64) NOT NULL, So the lenght is ok. Maybe you should put something in the faq like: I can't login anymore never mind which user I try. I always get the message "[ Incorrect User ID or Password, or your account has been disabled/expired. ]" ---------------------------------------------------------------------- Comment By: Matthew Gregg (greggmc) Date: 2007-05-29 16:54 Message: Logged In: YES user_id=14116 Originator: NO I guess this belongs in the documentation somewhere. Not really a bug with ESP. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=1727902&group_id=8956 |
|
From: Franky V. L. <lie...@te...> - 2009-05-08 09:42:33
|
Hi, I'm just continuing the project, sourcecode based ... I'm mailing this to the developers list as well, so everybody who wants to react, please do. Franky On Fri, May 8, 2009 at 11:36 AM, matin majtavi <ma...@gm...> wrote: > hi franky > > who controls phpESP then? anyone? Thanks for the fast reply. > > On Fri, May 8, 2009 at 5:24 AM, Franky Van Liedekerke <lie...@te...> > wrote: >> >> On Thu, May 7, 2009 at 6:33 AM, Trilex Labs >> <tri...@us...> wrote: >> > >> > Message body follows: >> > >> > My name is Mat, I am part of Group called Trilex Labs >> > we do alot open source projects and help alot of open based >> > projects too. Our team wanna help >> > phpESP in hosting it plus developing it more and >> > getting it closer to V3.0 plus in future the extend the >> > project...Please let me know what you think so we can get >> > started.. you can add to msn or live messnager >> > ma...@tr... or if you have yahoo or something >> > else I can add you to my list ... by the way my phone >> > number is 416 427 1214 if you need to get in touch with me >> > Thanks >> >> Hi Mat, >> >> thanks for the offer. For the moment we use sourceforge for our >> project site. The real site needs changing (not under my control), but >> I think it is best to keep the project on sourceforge. Of course you >> can set up a demo at your site if you want (the one on sourceforge is >> again not under my control). >> And of course any contribution to the code is appreciated, as are >> suggestions, etc ... >> >> Franky > > > > -- > Sincerley yours > > Mat > > |
|
From: SourceForge.net <no...@so...> - 2009-05-08 07:46:03
|
Bugs item #1727902, was opened at 2007-05-29 22:38 Message generated for change (Comment added) made by liedekef You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=1727902&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Docs / FAQ Group: v1.8 Status: Closed Resolution: Accepted Priority: 5 Private: No Submitted By: Miguel (miguel2) Assigned to: Nobody/Anonymous (nobody) Summary: No Logon when mysql > 4.1 (hash lenght problem) Initial Comment: Today i could not login to phpESP even if i created a new user via phpmyadmin. I didnt login since a year. in the meantime the hoster upgraded to mysql 5. I investigated a bit and found that the lenght of the password hash created by the mysql function PASSWORD() has changed from 16bit to 41bit. (http://dev.mysql.com/doc/refman/5.0/en/password-hashing.html) You have to change the lenght of the password field in table designer to 41 ALTER TABLE `designer` CHANGE `password` `password` CHAR( 64 ) CHARACTER SET latin1 COLLATE latin1_swedish_ci NOT NULL ---------------------------------------------------------------------- >Comment By: Franky Van Liedekerke (liedekef) Date: 2009-05-08 09:46 Message: Please don't do anonymous comments to a closed bug. Just upgrade to the latest version and this is fixed. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-05-08 05:50 Message: then how to solve it? ---------------------------------------------------------------------- Comment By: Franky Van Liedekerke (liedekef) Date: 2007-11-27 12:44 Message: Logged In: YES user_id=109671 Originator: NO Hi, I do consider this a phpesp issue as well, so I added these statements again to the next upgrade sql script, so everybody has the changes needed. Franky ---------------------------------------------------------------------- Comment By: Miguel (miguel2) Date: 2007-05-29 23:22 Message: Logged In: YES user_id=1346327 Originator: YES You are right. The sql statement in mysql_populate.sql is CREATE TABLE designer ( username CHAR(64) NOT NULL, password CHAR(64) NOT NULL, So the lenght is ok. Maybe you should put something in the faq like: I can't login anymore never mind which user I try. I always get the message "[ Incorrect User ID or Password, or your account has been disabled/expired. ]" ---------------------------------------------------------------------- Comment By: Matthew Gregg (greggmc) Date: 2007-05-29 22:54 Message: Logged In: YES user_id=14116 Originator: NO I guess this belongs in the documentation somewhere. Not really a bug with ESP. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=1727902&group_id=8956 |
|
From: SourceForge.net <no...@so...> - 2009-05-08 03:50:45
|
Bugs item #1727902, was opened at 2007-05-29 20:38 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=1727902&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Docs / FAQ Group: v1.8 Status: Closed Resolution: Accepted Priority: 5 Private: No Submitted By: Miguel (miguel2) Assigned to: Nobody/Anonymous (nobody) Summary: No Logon when mysql > 4.1 (hash lenght problem) Initial Comment: Today i could not login to phpESP even if i created a new user via phpmyadmin. I didnt login since a year. in the meantime the hoster upgraded to mysql 5. I investigated a bit and found that the lenght of the password hash created by the mysql function PASSWORD() has changed from 16bit to 41bit. (http://dev.mysql.com/doc/refman/5.0/en/password-hashing.html) You have to change the lenght of the password field in table designer to 41 ALTER TABLE `designer` CHANGE `password` `password` CHAR( 64 ) CHARACTER SET latin1 COLLATE latin1_swedish_ci NOT NULL ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-05-08 03:50 Message: then how to solve it? ---------------------------------------------------------------------- Comment By: Franky Van Liedekerke (liedekef) Date: 2007-11-27 11:44 Message: Logged In: YES user_id=109671 Originator: NO Hi, I do consider this a phpesp issue as well, so I added these statements again to the next upgrade sql script, so everybody has the changes needed. Franky ---------------------------------------------------------------------- Comment By: Miguel (miguel2) Date: 2007-05-29 21:22 Message: Logged In: YES user_id=1346327 Originator: YES You are right. The sql statement in mysql_populate.sql is CREATE TABLE designer ( username CHAR(64) NOT NULL, password CHAR(64) NOT NULL, So the lenght is ok. Maybe you should put something in the faq like: I can't login anymore never mind which user I try. I always get the message "[ Incorrect User ID or Password, or your account has been disabled/expired. ]" ---------------------------------------------------------------------- Comment By: Matthew Gregg (greggmc) Date: 2007-05-29 20:54 Message: Logged In: YES user_id=14116 Originator: NO I guess this belongs in the documentation somewhere. Not really a bug with ESP. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=1727902&group_id=8956 |
|
From: SourceForge.net <no...@so...> - 2009-05-05 08:31:02
|
Bugs item #2787019, was opened at 2009-05-05 00:04 Message generated for change (Settings changed) made by bishopb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2787019&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: User Group: 2.1.2 Status: Open Resolution: None Priority: 5 Private: No Submitted By: kswartz (kswartz) >Assigned to: bishop (bishopb) Summary: Survey in dashboard only allows one saved response at a time Initial Comment: When using the dashboard, if a survey allows multiple responses, the user can only have one ongoing (incomplete) copy of that survey at any given time. In other words, if a user wants to start a survey, save it, then start ANOTHER one, they cannot -- they have to finish the original survey first. (And they can't reset it, either, but that's a separate bug. :) ) Fixing this will probably require some changes to the way the dashboard is laid out. Right now, the only linkable text is the name of the survey. The logic is as follows: - If multiple submissions are allowed, and no survey has been submitted, clicking it starts a new survey. - If multiple submissions are allowed, and you have an ongoing survey, clicking it resumes the ongoing survey. - If multiple submissions are allowed, and a survey has been completed, clicking it starts a new one. So this results in two problems. First, if you have an ongoing survey, the UI does not provide any mechanism for starting a new one until the saved one is completed and submitted. Second, if you /do/ submit one or more surveys, and have another ongoing survey, the status will read either "Started, but Incomplete" or "Some Finished, some Incomplete". So if you have /multiple saved/ surveys, the UI has no means for you to choose /which one/ to resume. My suggestion would be a new column (specifically for surveys allowing multiple responses) listing how many submissions the user has made, and the dates each survey was started (or saved). For incomplete surveys, a link on that date -- rather than the survey name -- would allow the user to resume the survey. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2787019&group_id=8956 |
|
From: SourceForge.net <no...@so...> - 2009-05-05 04:05:08
|
Bugs item #2787019, was opened at 2009-05-04 21:04 Message generated for change (Tracker Item Submitted) made by kswartz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2787019&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: User Group: 2.1.2 Status: Open Resolution: None Priority: 5 Private: No Submitted By: kswartz (kswartz) Assigned to: Nobody/Anonymous (nobody) Summary: Survey in dashboard only allows one saved response at a time Initial Comment: When using the dashboard, if a survey allows multiple responses, the user can only have one ongoing (incomplete) copy of that survey at any given time. In other words, if a user wants to start a survey, save it, then start ANOTHER one, they cannot -- they have to finish the original survey first. (And they can't reset it, either, but that's a separate bug. :) ) Fixing this will probably require some changes to the way the dashboard is laid out. Right now, the only linkable text is the name of the survey. The logic is as follows: - If multiple submissions are allowed, and no survey has been submitted, clicking it starts a new survey. - If multiple submissions are allowed, and you have an ongoing survey, clicking it resumes the ongoing survey. - If multiple submissions are allowed, and a survey has been completed, clicking it starts a new one. So this results in two problems. First, if you have an ongoing survey, the UI does not provide any mechanism for starting a new one until the saved one is completed and submitted. Second, if you /do/ submit one or more surveys, and have another ongoing survey, the status will read either "Started, but Incomplete" or "Some Finished, some Incomplete". So if you have /multiple saved/ surveys, the UI has no means for you to choose /which one/ to resume. My suggestion would be a new column (specifically for surveys allowing multiple responses) listing how many submissions the user has made, and the dates each survey was started (or saved). For incomplete surveys, a link on that date -- rather than the survey name -- would allow the user to resume the survey. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108956&aid=2787019&group_id=8956 |
|
From: Franky V. L. <lie...@te...> - 2009-04-30 17:26:04
|
On Thu, 30 Apr 2009 11:08:58 -0400 Bishop Bettini <ph...@id...> wrote: > Quoting Keith Swartz <ph...@on...>: > > > I've been asked by my management to add a feature to our internal > > implementation of phpESP that would allow survey respondents to > > modify their responses at any time /after/ they have submitted > > their survey. > > This is outside my use case, so I've never really looked into it, > but I think phpesp was originally designed to not support this; the > original code seems to have been rooted in public surveys, to which > this doesn't apply. > > > > I've been looking over the code, and it seems like for private > > surveys, where /multiple responses/ are allowed, this is going to > > be quite a challenge. > > To say the least. How does the user decide b/w which previous > response he wants to resubmit... other than scrolling through them > and looking at them or maybe by date submitted? > > > > From only a cursory review, the authentication mechanism and > > the survey handler (and handler-prefix) would have to undergo some > > big changes, which would be hard to carry forward to new releases. > > Dashboard would have to change, if you're using that to list surveys. > > > > Before I start messing around with this, am I overlooking some easy > > or more obvious way to achieve this goal? > > What is the root goal? Or, rather, why allow people to change their > previous responses... instead of simply taking a new (duplicate) > survey? > > > bishop > This is totally beyond survey design, so by default also totally beyond phpesp. The thing is, a survey designer want to be able to guarantee that nobody messed with the answers, and you want the opposite ... Franky |
|
From: SourceForge.net <no...@so...> - 2009-04-30 15:15:39
|
Feature Requests item #2676835, was opened at 2009-03-09 19:46 Message generated for change (Comment added) made by bishopb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2676835&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: kswartz (kswartz) Assigned to: Nobody/Anonymous (nobody) Summary: Need ability for user to delete incomplete survey Initial Comment: 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. ---------------------------------------------------------------------- >Comment By: bishop (bishopb) Date: 2009-04-30 11:15 Message: kswartz> I'm kind of scratching my head here: under what conditions would that test kswartz> actually be valid? I'm not at all familiar with the whys in handler, but just guessing, maybe when the survey is in test mode? But, regardless, that whole conditional is voodoo. It starts out with "if empty request userid" then within it says "if not empty request userid"? Total black magic. ---------------------------------------------------------------------- Comment By: kswartz (kswartz) Date: 2009-04-30 00:43 Message: Okay, figured out why putting "&sec=1" in the query string doesn't work. It's because of this section in handler-prefix.php: if(empty($_REQUEST['userid'])) { // find remote user id (takes the first non-empty of the following) // 1. a GET variable named 'userid' // 2. the REMOTE_USER set by HTTP-Authentication // 3. the query string // 4. the remote ip address if (!empty($_REQUEST['userid'])) { $_REQUEST['userid'] = $_REQUEST['userid']; } elseif(!empty($_SERVER['REMOTE_USER'])) { $_REQUEST['userid'] = $_SERVER['REMOTE_USER']; ---> } elseif(!empty($_SERVER['QUERY_STRING'])) { $_REQUEST['userid'] = urldecode($_SERVER['QUERY_STRING']); } else { $_REQUEST['userid'] = $_SERVER['REMOTE_ADDR']; } } The line with "--->" in front is the condition that's triggering inappropriately. When the first two tests fail, the query_string "sec=1" is matched here, and it sets userid to that. I'm kind of scratching my head here: under what conditions would that test actually be valid? I'm finding that even if I modify that line as follows, though: } elseif(!empty($_SERVER['QUERY_STRING']) && (strpos($_SERVER['QUERY_STRING'],'=')===FALSE)) { it doesn't mess with the userid variable, but it still doesn't modify the value of sid. ---------------------------------------------------------------------- Comment By: kswartz (kswartz) Date: 2009-03-10 17:30 Message: This is the URL I was using to try and jump to page 1: http://localhost/techeval/public/survey.php?sec=1&name=ebstecheval However, it just reloads the page I saved on. When I do a view source, I see this: <input type="hidden" name="userid" value="sec=1" /> <input type="hidden" name="sid" value="3" /> <input type="hidden" name="rid" value="113" /> <input type="hidden" name="sec" value="3" /> Not sure if it's relevant, but this is a private survey, with navigation and save/resume enabled. Of course, overriding the URL on the browser bar is mixing GET parameters with POST parameters. If handler.php looks at the POST parameter over the GET one, then putting it in a URL won't work. I'll have to use a JavaScript handler to update the sec hidden field to something like 2, then pretend the user hit the Prev button. (I don't even know if that'll work, just a guess.) --- I totally agree about productizing any such solution. I would also want to harden it by comparing the owner of the current session and the owner of the survey, and only allow a delete (or reset) if they match. The per-survey control is something I can forego for my own purposes, although I would certainly agree with the need for that in the product. Regarding the resetting option, when you say: "Nonetheless, I don't think a survey_reset() would waste the response table rows: it would simply update them to the default values (eg null).", I see a problem with that if the questions are marked as required. It might technically work if you're only enforcing that constraint through the UI, but I'm visualizing a scenario in which the user manually tweaks the URL to jump to the last page and submit his survey -- now full of unanswered questions that require a value. (I'm also making an assumption here that a null value is not an acceptable answer when one is required. Functionally, I think that's appropriate.) ---------------------------------------------------------------------- Comment By: bishop (bishopb) Date: 2009-03-10 14:50 Message: I would think that sec=1 would do it, as that sets the section. Upon cursory review of the code (handler.php down to survey_render.php), that looks correct. Can you include your modified URL and a little more description of the "sets the hidden user id parameter to 'sec=1'" problem? Re: survey_reset() vs. survey_delete(). Your situation does sound like it could go both ways, so the easiest thing to do would be to link to a "delete" handler right on the survey. That handler (say delete.php) takes the response ID and blows away the survey (via survey_delete()), then links back (or throws a header) to the dashboard. That would be ad-hoc and could be kept out of the phpESP source tree for your own use. But, to implement this to production would require some more fortification. The delete handler, for example, would need to also corroborate the SID to prevent delete attacks. We would also want to add per-survey control over whether responses may be deleted by the respondent. Were there to be a survey_reset(), that would need to figure out the default values and set the entries to those defaults, opting to null if no defaults were defined. (I don't recall if we have a definition of "default values", so setting to null always would be appropriate.) Nonetheless, I don't think a survey_reset() would waste the response table rows: it would simply update them to the default values (eg null). (And then possibly increment a reset_counter in the statistics table.) ---------------------------------------------------------------------- Comment By: kswartz (kswartz) Date: 2009-03-10 13:59 Message: BTW, I've joined the developer's mailing list. If that is a more appropriate forum for discussions of this nature in the future, please let me know, and I'll do that. I logged a request mainly because I thought there was strong support for this to be a generic enhancement, and there might be a patch resulting from the discussion (possibly from me). ---------------------------------------------------------------------- Comment By: kswartz (kswartz) Date: 2009-03-10 13:58 Message: This is great. Thank you for the ideas! How do you link back to the first page of a survey? I tried adding "&sec=1" to the URL, but then it sets the hidden userid parameter to "sec=1". (That looks like a bug, by the way. :) ) Actually, my use case is really more of a deletion, than a reset, but either one would work. The survey we've implemented is used to request and gather information about using another software product in conjunction with our own. The use case I envision is that the respondent decides they don't want to use that product after doing the research. But the survey has to be filled out once for each product they want to use, so if the user finds something else he wants to use, he has to fill out a new survey, starting from scratch. In our case, nothing from the original survey would be preserved, except for about 3 questions (of roughly 100) with information identifying the requester. [If this were going to be a 100% custom solution for us, I might consider preserving that data. I've been trying not to make too many changes like that, however, as it'll make it harder for me to contribute other fixes I've made back to the project.] Now, in our case, there are no default values -- everything is blank to start out. In that case, the only difference between resetting and deleting the survey that I can see is that deleting it removes a row from the response table. Both options would still remove all the rows from the response_* child tables (again, that's specific to this case, where none of the questions have default values). Is that an accurate assessment? Thanks again. ---------------------------------------------------------------------- Comment By: bishop (bishopb) Date: 2009-03-10 08:13 Message: I'm with Franky, at least in addressing a valid navigation use case ("user wants to review or change submitted responses, starting from the beginning"). I'd also like to define the semantic differences of "resetting" a survey's responses and "deleting" a survey. The former keeps the survey, but initializes responses to default values. The latter removes any indication that the user every began the survey. It's entirely possible that "resetting" is allowed (and desired), but "deleting" is not. I can also see cases where you'd want to record the number of resets (for statistical analysis on the effectiveness of your surveys). Your description of the problem sounds more like resetting, than deleting. If that is the case, I would not reuse the admin survey_delete() code based on response ID. Instead, I'd write a new function (say survey_reset()) and expose it both in admin (keyed off of response ID) and in userland (as at least a link on the survey itself, possibly (though not recommended) with a link on the dashboard). ---------------------------------------------------------------------- Comment By: Franky Van Liedekerke (liedekef) Date: 2009-03-10 03:36 Message: How about just providing a link to the first page of the survey? You can do this at the bottom, top, anywhere within the current survey ... Franky ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2676835&group_id=8956 |
|
From: Bishop B. <ph...@id...> - 2009-04-30 15:09:17
|
Quoting Keith Swartz <ph...@on...>: > I've been asked by my management to add a feature to our internal > implementation of phpESP that would allow survey respondents to modify > their responses at any time /after/ they have submitted their survey. This is outside my use case, so I've never really looked into it, but I think phpesp was originally designed to not support this; the original code seems to have been rooted in public surveys, to which this doesn't apply. > I've been looking over the code, and it seems like for private surveys, > where /multiple responses/ are allowed, this is going to be quite a > challenge. To say the least. How does the user decide b/w which previous response he wants to resubmit... other than scrolling through them and looking at them or maybe by date submitted? > From only a cursory review, the authentication mechanism and > the survey handler (and handler-prefix) would have to undergo some big > changes, which would be hard to carry forward to new releases. Dashboard would have to change, if you're using that to list surveys. > Before I start messing around with this, am I overlooking some easy or > more obvious way to achieve this goal? What is the root goal? Or, rather, why allow people to change their previous responses... instead of simply taking a new (duplicate) survey? bishop -- Bishop Bettini ideacode, Inc. (main) +1 919 341 5170 / (fax) +1 919 521 4100 Visit us on the web at: ideacode.com Professional software research and development reviewmysoftware.com Improve sales! Review your software before you release bytejar.com Solutions to those annoying development problems |
|
From: Keith S. <ph...@on...> - 2009-04-30 06:11:31
|
Gentlemen, I've been asked by my management to add a feature to our internal implementation of phpESP that would allow survey respondents to modify their responses at any time /after/ they have submitted their survey. I've been looking over the code, and it seems like for private surveys, where /multiple responses/ are allowed, this is going to be quite a challenge. From only a cursory review, the authentication mechanism and the survey handler (and handler-prefix) would have to undergo some big changes, which would be hard to carry forward to new releases. Before I start messing around with this, am I overlooking some easy or more obvious way to achieve this goal? Thanks very much, Keith |
|
From: SourceForge.net <no...@so...> - 2009-04-30 04:43:32
|
Feature Requests item #2676835, was opened at 2009-03-09 16:46 Message generated for change (Comment added) made by kswartz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2676835&group_id=8956 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: kswartz (kswartz) Assigned to: Nobody/Anonymous (nobody) Summary: Need ability for user to delete incomplete survey Initial Comment: 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. ---------------------------------------------------------------------- >Comment By: kswartz (kswartz) Date: 2009-04-29 21:43 Message: Okay, figured out why putting "&sec=1" in the query string doesn't work. It's because of this section in handler-prefix.php: if(empty($_REQUEST['userid'])) { // find remote user id (takes the first non-empty of the following) // 1. a GET variable named 'userid' // 2. the REMOTE_USER set by HTTP-Authentication // 3. the query string // 4. the remote ip address if (!empty($_REQUEST['userid'])) { $_REQUEST['userid'] = $_REQUEST['userid']; } elseif(!empty($_SERVER['REMOTE_USER'])) { $_REQUEST['userid'] = $_SERVER['REMOTE_USER']; ---> } elseif(!empty($_SERVER['QUERY_STRING'])) { $_REQUEST['userid'] = urldecode($_SERVER['QUERY_STRING']); } else { $_REQUEST['userid'] = $_SERVER['REMOTE_ADDR']; } } The line with "--->" in front is the condition that's triggering inappropriately. When the first two tests fail, the query_string "sec=1" is matched here, and it sets userid to that. I'm kind of scratching my head here: under what conditions would that test actually be valid? I'm finding that even if I modify that line as follows, though: } elseif(!empty($_SERVER['QUERY_STRING']) && (strpos($_SERVER['QUERY_STRING'],'=')===FALSE)) { it doesn't mess with the userid variable, but it still doesn't modify the value of sid. ---------------------------------------------------------------------- Comment By: kswartz (kswartz) Date: 2009-03-10 14:30 Message: This is the URL I was using to try and jump to page 1: http://localhost/techeval/public/survey.php?sec=1&name=ebstecheval However, it just reloads the page I saved on. When I do a view source, I see this: <input type="hidden" name="userid" value="sec=1" /> <input type="hidden" name="sid" value="3" /> <input type="hidden" name="rid" value="113" /> <input type="hidden" name="sec" value="3" /> Not sure if it's relevant, but this is a private survey, with navigation and save/resume enabled. Of course, overriding the URL on the browser bar is mixing GET parameters with POST parameters. If handler.php looks at the POST parameter over the GET one, then putting it in a URL won't work. I'll have to use a JavaScript handler to update the sec hidden field to something like 2, then pretend the user hit the Prev button. (I don't even know if that'll work, just a guess.) --- I totally agree about productizing any such solution. I would also want to harden it by comparing the owner of the current session and the owner of the survey, and only allow a delete (or reset) if they match. The per-survey control is something I can forego for my own purposes, although I would certainly agree with the need for that in the product. Regarding the resetting option, when you say: "Nonetheless, I don't think a survey_reset() would waste the response table rows: it would simply update them to the default values (eg null).", I see a problem with that if the questions are marked as required. It might technically work if you're only enforcing that constraint through the UI, but I'm visualizing a scenario in which the user manually tweaks the URL to jump to the last page and submit his survey -- now full of unanswered questions that require a value. (I'm also making an assumption here that a null value is not an acceptable answer when one is required. Functionally, I think that's appropriate.) ---------------------------------------------------------------------- Comment By: bishop (bishopb) Date: 2009-03-10 11:50 Message: I would think that sec=1 would do it, as that sets the section. Upon cursory review of the code (handler.php down to survey_render.php), that looks correct. Can you include your modified URL and a little more description of the "sets the hidden user id parameter to 'sec=1'" problem? Re: survey_reset() vs. survey_delete(). Your situation does sound like it could go both ways, so the easiest thing to do would be to link to a "delete" handler right on the survey. That handler (say delete.php) takes the response ID and blows away the survey (via survey_delete()), then links back (or throws a header) to the dashboard. That would be ad-hoc and could be kept out of the phpESP source tree for your own use. But, to implement this to production would require some more fortification. The delete handler, for example, would need to also corroborate the SID to prevent delete attacks. We would also want to add per-survey control over whether responses may be deleted by the respondent. Were there to be a survey_reset(), that would need to figure out the default values and set the entries to those defaults, opting to null if no defaults were defined. (I don't recall if we have a definition of "default values", so setting to null always would be appropriate.) Nonetheless, I don't think a survey_reset() would waste the response table rows: it would simply update them to the default values (eg null). (And then possibly increment a reset_counter in the statistics table.) ---------------------------------------------------------------------- Comment By: kswartz (kswartz) Date: 2009-03-10 10:59 Message: BTW, I've joined the developer's mailing list. If that is a more appropriate forum for discussions of this nature in the future, please let me know, and I'll do that. I logged a request mainly because I thought there was strong support for this to be a generic enhancement, and there might be a patch resulting from the discussion (possibly from me). ---------------------------------------------------------------------- Comment By: kswartz (kswartz) Date: 2009-03-10 10:58 Message: This is great. Thank you for the ideas! How do you link back to the first page of a survey? I tried adding "&sec=1" to the URL, but then it sets the hidden userid parameter to "sec=1". (That looks like a bug, by the way. :) ) Actually, my use case is really more of a deletion, than a reset, but either one would work. The survey we've implemented is used to request and gather information about using another software product in conjunction with our own. The use case I envision is that the respondent decides they don't want to use that product after doing the research. But the survey has to be filled out once for each product they want to use, so if the user finds something else he wants to use, he has to fill out a new survey, starting from scratch. In our case, nothing from the original survey would be preserved, except for about 3 questions (of roughly 100) with information identifying the requester. [If this were going to be a 100% custom solution for us, I might consider preserving that data. I've been trying not to make too many changes like that, however, as it'll make it harder for me to contribute other fixes I've made back to the project.] Now, in our case, there are no default values -- everything is blank to start out. In that case, the only difference between resetting and deleting the survey that I can see is that deleting it removes a row from the response table. Both options would still remove all the rows from the response_* child tables (again, that's specific to this case, where none of the questions have default values). Is that an accurate assessment? Thanks again. ---------------------------------------------------------------------- Comment By: bishop (bishopb) Date: 2009-03-10 05:13 Message: I'm with Franky, at least in addressing a valid navigation use case ("user wants to review or change submitted responses, starting from the beginning"). I'd also like to define the semantic differences of "resetting" a survey's responses and "deleting" a survey. The former keeps the survey, but initializes responses to default values. The latter removes any indication that the user every began the survey. It's entirely possible that "resetting" is allowed (and desired), but "deleting" is not. I can also see cases where you'd want to record the number of resets (for statistical analysis on the effectiveness of your surveys). Your description of the problem sounds more like resetting, than deleting. If that is the case, I would not reuse the admin survey_delete() code based on response ID. Instead, I'd write a new function (say survey_reset()) and expose it both in admin (keyed off of response ID) and in userland (as at least a link on the survey itself, possibly (though not recommended) with a link on the dashboard). ---------------------------------------------------------------------- Comment By: Franky Van Liedekerke (liedekef) Date: 2009-03-10 00:36 Message: How about just providing a link to the first page of the survey? You can do this at the bottom, top, anywhere within the current survey ... Franky ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=358956&aid=2676835&group_id=8956 |
24 messages has been excluded from this view by a project administrator.
