Earlier this year

• Nov 11, 2009

  issue 36 (ReverseMatch error when attempting to delete questions) commented on by Bmheight   -   This is still actually an issue in the non admin side of things. The literal fix, though improper fix is to remove "group_slug":group_slug from line 281 in django-survey/survey/views.py This is not a fix by any means, but more of a temporary representation of where the issue is at and to show where the issue occurs.

  This is still actually an issue in the non admin side of things. The literal fix, though improper fix is to remove "group_slug":group_slug from line 281 in django-survey/survey/views.py This is not a fix by any means, but more of a temporary representation of where the issue is at and to show where the issue occurs.
• Nov 11, 2009

  issue 45 (Multipage surveys) commented on by dschruth   -   Has anybody been working on this? Having this sort of multi page and/or session saving functionality would greatly help me in a project I need to complete within the next couple of months.

  Has anybody been working on this? Having this sort of multi page and/or session saving functionality would greatly help me in a project I need to complete within the next couple of months.
• Nov 03, 2009

  r116 (Incremental fixes to the project.) committed by salimfadhley   -   Incremental fixes to the project.

  Incremental fixes to the project.
• Oct 28, 2009

  issue 30 (A survey having been taken is tied only to the session.. and...) commented on by charpentier.johan   -   Hi, This issue insn't fixed for last revision in trunk (rev115) Here is patch with tests. Hope it can be usefull.

  Hi, This issue insn't fixed for last revision in trunk (rev115) Here is patch with tests. Hope it can be usefull.
• Oct 04, 2009

  r115 (Some bugfixes to optiongrid saving + ensure that session IDs...) committed by salimfadhley   -   Some bugfixes to optiongrid saving + ensure that session IDs are saved on checkbox fields.

  Some bugfixes to optiongrid saving + ensure that session IDs are saved on checkbox fields.
• Sep 23, 2009

  issue 48 (Checkbox answers don't save with user.) commented on by schuyle...@gmail.com   -   could you send me a fixture for your survey data, perhaps? I've confirmed (again) that it is working for me with my patch.

  could you send me a fixture for your survey data, perhaps? I've confirmed (again) that it is working for me with my patch.
• Sep 22, 2009

  issue 48 (Checkbox answers don't save with user.) commented on by john.pena   -   I was able to replicate this issue. I patched with said patch, still experiencing the issue.

  I was able to replicate this issue. I patched with said patch, still experiencing the issue.
• Sep 20, 2009

  r114 (Incomplete X-to-Y grid support) committed by salimfadhley   -   Incomplete X-to-Y grid support

  Incomplete X-to-Y grid support
• Sep 14, 2009

  r113 (Make the post_survey_url optional) committed by salimfadhley   -   Make the post_survey_url optional

  Make the post_survey_url optional
• Sep 10, 2009

  r112 (Added the choice ordering feature.) committed by salimfadhley   -   Added the choice ordering feature.

  Added the choice ordering feature.
• Sep 09, 2009

  r111 (Bugfix to question ordering) committed by salimfadhley   -   Bugfix to question ordering

  Bugfix to question ordering
• Sep 09, 2009

  r110 (Ordering of questions now works.) committed by salimfadhley   -   Ordering of questions now works.

  Ordering of questions now works.
• Sep 08, 2009

  r109 (Interim checkin after tidyup - removed some ordering feature...) committed by salimfadhley   -   Interim checkin after tidyup - removed some ordering features from the Question class which were mucking up with MySQL

  Interim checkin after tidyup - removed some ordering features from the Question class which were mucking up with MySQL
• Sep 08, 2009

  r108 (Added some svn:ignores) committed by salimfadhley   -   Added some svn:ignores

  Added some svn:ignores
• Sep 08, 2009

  r107 (initial commit of my optiongroup work) committed by salimfadhley   -   initial commit of my optiongroup work

  initial commit of my optiongroup work
• Sep 08, 2009

  r106 (new branch for my optiongroup work) committed by salimfadhley   -   new branch for my optiongroup work

  new branch for my optiongroup work
• Sep 08, 2009

  r105 (Made in error ) committed by salimfadhley   -   Made in error

  Made in error
• Sep 08, 2009

  r104 (new branch for my optiongroup work ) committed by salimfadhley   -   new branch for my optiongroup work

  new branch for my optiongroup work
• Sep 07, 2009

  issue 37 (Docs for recipient type, recipient id) commented on by john.pena   -   All that needs to be done is adding 'blank=True' as a parameter to recipient ID and type in the Survey model

  All that needs to be done is adding 'blank=True' as a parameter to recipient ID and type in the Survey model
• Sep 07, 2009

  issue 37 (Docs for recipient type, recipient id) commented on by shac...@birdhouse.org   -   Since this is a re-usable app, I would recommend that the distribution leave Pinax-specific fields commented out in the source. People who need Pinax can uncomment them. For everyone else, leaving them in basically results in confusing/broken behavior.

  Since this is a re-usable app, I would recommend that the distribution leave Pinax-specific fields commented out in the source. People who need Pinax can uncomment them. For everyone else, leaving them in basically results in confusing/broken behavior.
• Sep 07, 2009

  issue 37 (Docs for recipient type, recipient id) commented on by john.pena   -   These fields are for integration with Pinax. No idea how to use them.

  These fields are for integration with Pinax. No idea how to use them.
• Aug 30, 2009

  issue 37 (Docs for recipient type, recipient id) commented on by john.pena   -   The example app doesn't offer any help. Try logging in to the admin page and changing one of the example surveys. Even if you hit save without changing anything, the admin site will raise an error saying you haven't filled in the recipient type/id even though they weren't filled in to begin with.

  The example app doesn't offer any help. Try logging in to the admin page and changing one of the example surveys. Even if you hit save without changing anything, the admin site will raise an error saying you haven't filled in the recipient type/id even though they weren't filled in to begin with.
• Aug 28, 2009

  issue 24 (syncdb raises exception) commented on by conradlee   -   This problem still exists. I followed the approach from mandric in the original post--that is, I changed the TextField to a CharField with a max_length of 500.

  This problem still exists. I followed the approach from mandric in the original post--that is, I changed the TextField to a CharField with a max_length of 500.
• Aug 10, 2009

  issue 48 (Checkbox answers don't save with user.) reported by schuyler1d   -   What steps will reproduce the problem? 1. Create a form with a checkbox 2. Have a user fill it out. 3. Note that (e.g. in admin) the Answer record has no user/user_id What is the expected output? What do you see instead? The Answer record should have a user_id What version of the product are you using? On what operating system? 0.0.2 and trunk Please provide any additional information below. The problem is that the extra save() code in BaseAnswerForm() became out of sync with ChoiceCheckbox()'s override. The patch fixes the issue and makes it slightly more likely that this will not happen in the future.

  What steps will reproduce the problem? 1. Create a form with a checkbox 2. Have a user fill it out. 3. Note that (e.g. in admin) the Answer record has no user/user_id What is the expected output? What do you see instead? The Answer record should have a user_id What version of the product are you using? On what operating system? 0.0.2 and trunk Please provide any additional information below. The problem is that the extra save() code in BaseAnswerForm() became out of sync with ChoiceCheckbox()'s override. The patch fixes the issue and makes it slightly more likely that this will not happen in the future.
• Jul 20, 2009

  issue 38 (Allow definition of 'next_page' in Survey model [patch attac...) commented on by mr.benward   -   Hi there, I applied your patch, but needed to make a small change line 48 from this: return HttpResponseRedirect(request.survey.next_page or request.REQUEST['next']) to this: return HttpResponseRedirect(survey.next_page or request.REQUEST['next']) Also at note to the developers, why do you inspect to see if request.REQUEST['next'].startswith('http:') ? could not the next url by relatively addressed? thanks for sharing your code. i will let you know how i go. thanks ben.

  Hi there, I applied your patch, but needed to make a small change line 48 from this: return HttpResponseRedirect(request.survey.next_page or request.REQUEST['next']) to this: return HttpResponseRedirect(survey.next_page or request.REQUEST['next']) Also at note to the developers, why do you inspect to see if request.REQUEST['next'].startswith('http:') ? could not the next url by relatively addressed? thanks for sharing your code. i will let you know how i go. thanks ben.
• Jul 20, 2009

  issue 38 (Allow definition of 'next_page' in Survey model [patch attac...) commented on by ministryofsoundau   -   Hi there, I applied your patch. but needed to change line 48 to this: return HttpResponseRedirect(survey.next_page or request.REQUEST['next'])

  Hi there, I applied your patch. but needed to change line 48 to this: return HttpResponseRedirect(survey.next_page or request.REQUEST['next'])
• Apr 29, 2009

  issue 37 (Docs for recipient type, recipient id) commented on by tdelam   -   I am trying to figure out what this is for as well, anyone?

  I am trying to figure out what this is for as well, anyone?
• Apr 11, 2009

  issue 47 (Add an interview table to help custom query reports.) changed by yann.malet   -  

  Status: Duplicate

  Status: Duplicate
• Apr 11, 2009

  issue 46 (Add an interview table to help custom query reports.) commented on by yann.malet   -   Issue 47 has been merged into this issue.

  Issue 47 has been merged into this issue.
• Apr 10, 2009

  issue 47 (Add an interview table to help custom query reports.) commented on by michael.larue   -   Delete this Google hiccup please.

  Delete this Google hiccup please.
• Apr 10, 2009

  issue 47 (Add an interview table to help custom query reports.) reported by michael.larue   -   Right now I'm trying to query the answer table for two answers to a survey, but it's requiring a massive amount ( O(n+1) ) of queries. Though I admit that I may be missing some Django query trickery that could solve in O(1). A simple interview table which contains submission_date, interview_uuid, user_id and session_key while adding an interview_id column to the answer table would reduce the query count in this case (and also reduce db memory footprint in general). Oh and the possible answers to query are far too numerous to create a survey for each possibility.

  Right now I'm trying to query the answer table for two answers to a survey, but it's requiring a massive amount ( O(n+1) ) of queries. Though I admit that I may be missing some Django query trickery that could solve in O(1). A simple interview table which contains submission_date, interview_uuid, user_id and session_key while adding an interview_id column to the answer table would reduce the query count in this case (and also reduce db memory footprint in general). Oh and the possible answers to query are far too numerous to create a survey for each possibility.
• Apr 10, 2009

  issue 46 (Add an interview table to help custom query reports.) reported by michael.larue   -   Right now I'm trying to query the answer table for two answers to a survey, but it's requiring a massive amount ( O(n+1) ) of queries. Though I admit that I may be missing some Django query trickery that could solve in O(1). A simple interview table which contains submission_date, interview_uuid, user_id and session_key while adding an interview_id column to the answer table would reduce the query count in this case (and also reduce db memory footprint in general). Oh and the possible answers to query are far too numerous to create a survey for each possibility.

  Right now I'm trying to query the answer table for two answers to a survey, but it's requiring a massive amount ( O(n+1) ) of queries. Though I admit that I may be missing some Django query trickery that could solve in O(1). A simple interview table which contains submission_date, interview_uuid, user_id and session_key while adding an interview_id column to the answer table would reduce the query count in this case (and also reduce db memory footprint in general). Oh and the possible answers to query are far too numerous to create a survey for each possibility.
• Mar 26, 2009

  issue 45 (Multipage surveys) commented on by freakclimbing   -   Well, glad you guys liked the idea! Given that multipage surveys and conditional flows, even if overlapping features, could be scomponed in 2 development steps, why not start with multipage? In another application I developed in PHP the data between pages where stored in the user session, and the data where serialized keeping the page they belonged to in the array (dictionary or list) key. Once the respondent had completed the questionnaire, the results where then saved in the DB. Not sure if the Django Form Wizard works with sessions or hidden fields. Daniel daniel

  Well, glad you guys liked the idea! Given that multipage surveys and conditional flows, even if overlapping features, could be scomponed in 2 development steps, why not start with multipage? In another application I developed in PHP the data between pages where stored in the user session, and the data where serialized keeping the page they belonged to in the array (dictionary or list) key. Once the respondent had completed the questionnaire, the results where then saved in the DB. Not sure if the Django Form Wizard works with sessions or hidden fields. Daniel daniel
• Mar 26, 2009

  issue 45 (Multipage surveys) commented on by yann.malet   -   I like the idea of being able to display a survey on multiple pages . Where I don't like the conditional flow. --yml

  I like the idea of being able to display a survey on multiple pages . Where I don't like the conditional flow. --yml
• Mar 25, 2009

  issue 45 (Multipage surveys) commented on by corn13read   -   I think that this would be a great addon. If this question is answered True then show blah page else show blah2 page. +1 from me.

  I think that this would be a great addon. If this question is answered True then show blah page else show blah2 page. +1 from me.
• Mar 23, 2009

  issue 45 (Multipage surveys) reported by freakclimbing   -   Hey guys, thanks for the great job! I just wanted to suggest an enhancement: what about adding the ability to build multipage surveys?: This would require, among the other things to - add a "page" field in the Question model - display just the questions related to a specific page - use the django-form wizard maybe? Jus an idea! Thanks again daniel

  Hey guys, thanks for the great job! I just wanted to suggest an enhancement: what about adding the ability to build multipage surveys?: This would require, among the other things to - add a "page" field in the Question model - display just the questions related to a specific page - use the django-form wizard maybe? Jus an idea! Thanks again daniel
• Mar 18, 2009

  issue 44 (Survey locking) reported by shac...@birdhouse.org   -   Because data integrity can be seriously messed up if you edit, add, or delete some types of questions after going live, most survey systems include a locking mechanism that prevents most types of editing after a survey has been published (see LimeSurvey for example). What version of the product are you using? On what operating system? r103

  Because data integrity can be seriously messed up if you edit, add, or delete some types of questions after going live, most survey systems include a locking mechanism that prevents most types of editing after a survey has been published (see LimeSurvey for example). What version of the product are you using? On what operating system? r103
• Mar 18, 2009

  issue 43 (Submissions count off by one) commented on by shac...@birdhouse.org   -   Nevermind - I had a leftover row in the table from previous experiment, sorry. Delete ticket.

  Nevermind - I had a leftover row in the table from previous experiment, sorry. Delete ticket.
• Mar 18, 2009

  issue 41 (Related field question type) commented on by shac...@birdhouse.org   -   The attached patch creates a new question type: UserPicklist. It's useful when teachers need to evaluate students, or for employers to evaluate employees, etc. Entries in the list are displayed as Lastname, Firstname. By default this question type will create a select box showing all registered users in the system. However, that's not always appropriate - you may have 5,000 registered users but only want to show users who match some criteria (like students from a particular school year or employees who have completed a workshop). So this question type adds a new Custom Query field in the add/edit question view. Enter a dictionary of the picklist criteria, e.g.: {'is_staff':True,'last_name__startswith':'A',} The dictionary will be stored in the db, then applied to the picklist when it's rendered. If you apply this to an existing system you'll need a new field on the question table: ALTER TABLE `survey_question` ADD COLUMN `custom_query` VARCHAR(255) CHARACTER SET latin1 COLLATE latin1_swedish_ci NULL DEFAULT NULL AFTER `choice_num_min`;

  The attached patch creates a new question type: UserPicklist. It's useful when teachers need to evaluate students, or for employers to evaluate employees, etc. Entries in the list are displayed as Lastname, Firstname. By default this question type will create a select box showing all registered users in the system. However, that's not always appropriate - you may have 5,000 registered users but only want to show users who match some criteria (like students from a particular school year or employees who have completed a workshop). So this question type adds a new Custom Query field in the add/edit question view. Enter a dictionary of the picklist criteria, e.g.: {'is_staff':True,'last_name__startswith':'A',} The dictionary will be stored in the db, then applied to the picklist when it's rendered. If you apply this to an existing system you'll need a new field on the question table: ALTER TABLE `survey_question` ADD COLUMN `custom_query` VARCHAR(255) CHARACTER SET latin1 COLLATE latin1_swedish_ci NULL DEFAULT NULL AFTER `choice_num_min`;
• Mar 18, 2009

  issue 43 (Submissions count off by one) reported by shac...@birdhouse.org   -   After submitting a fresh survey for the first time, the Info field says "2 Submissions." What version of the product are you using? On what operating system? r103

  After submitting a fresh survey for the first time, the Info field says "2 Submissions." What version of the product are you using? On what operating system? r103
• Mar 18, 2009

  issue 8 (transferring the ownership of a survey) commented on by shac...@birdhouse.org   -   I would add to this that in some uses cases, more than one person needs the ability to view and edit surveys. For example I (the webmaster) set up the survey, but our entire staff need to be able to see the results. Currently only the survey creator can edit questions and view results - we'd like to see this ability attached to a Group or a system permission such as is_staff().

  I would add to this that in some uses cases, more than one person needs the ability to view and edit surveys. For example I (the webmaster) set up the survey, but our entire staff need to be able to see the results. Currently only the survey creator can edit questions and view results - we'd like to see this ability attached to a Group or a system permission such as is_staff().
• Mar 12, 2009

  issue 42 (Non-staff can ) reported by shac...@birdhouse.org   -   While there is a @login_required decorator on survey_add, it allows *any* logged in user to create new surveys, rather than just users with is_staff or higher. Might be better to use has_perms for this so we can control which users or groups can create surveys from the django admin. What version of the product are you using? r103

  While there is a @login_required decorator on survey_add, it allows *any* logged in user to create new surveys, rather than just users with is_staff or higher. Might be better to use has_perms for this so we can control which users or groups can create surveys from the django admin. What version of the product are you using? r103
• Mar 12, 2009

  issue 40 (Answering survey with checkbox choices generates 500) commented on by shac...@birdhouse.org   -   This issue seems to be fixed in r103 - ticket should be closed. Thanks a ton!

  This issue seems to be fixed in r103 - ticket should be closed. Thanks a ton!
• Mar 12, 2009

  issue 36 (ReverseMatch error when attempting to delete questions) commented on by shac...@birdhouse.org   -   Thanks for all the bug fixes! On this one - I can now access and delete a question via the admin, but not from the edit quiz interface. I still get NoReverseMatch at /survey/question/delete/test-survey-1/3/ Reverse for 'survey-edit' with arguments '()' and keyword arguments '{'survey_slug': u'test-survey-1', 'group_slug': None}' not found. Testing with MySQL 5, Django SVN-9904, fresh tables.

  Thanks for all the bug fixes! On this one - I can now access and delete a question via the admin, but not from the edit quiz interface. I still get NoReverseMatch at /survey/question/delete/test-survey-1/3/ Reverse for 'survey-edit' with arguments '()' and keyword arguments '{'survey_slug': u'test-survey-1', 'group_slug': None}' not found. Testing with MySQL 5, Django SVN-9904, fresh tables.
• Mar 11, 2009

  r103 (Added the ability for surveys to be 'retaken'. This is done ...) committed by doug.napoleone   -   Added the ability for surveys to be 'retaken'. This is done by supplying the optional argument 'allow_edit_existing_answers' to the survey_detail view. This should be considered experimental support. ALERT!!! CRITICAL!!!! READ THIS!!!! Clients: the answer text for image answers has been updated to only be the choice text label and not the image html. This was causing problems for some clients when they changed where images were served from causing answers to magicly no longer exist. This change will mean that existing surveys with images will have thier previous data invalidated!!!!!!!

  Added the ability for surveys to be 'retaken'. This is done by supplying the optional argument 'allow_edit_existing_answers' to the survey_detail view. This should be considered experimental support. ALERT!!! CRITICAL!!!! READ THIS!!!! Clients: the answer text for image answers has been updated to only be the choice text label and not the image html. This was causing problems for some clients when they changed where images were served from causing answers to magicly no longer exist. This change will mean that existing surveys with images will have thier previous data invalidated!!!!!!!
• Mar 11, 2009

  issue 41 (Related field question type) Labels changed by yann.malet   -  

  Labels: Type-Enhancement −Type-Defect

  Labels: Type-Enhancement −Type-Defect
• Mar 11, 2009

  issue 39 (Wrong confirmation msg when deleting a question) Status changed by yann.malet   -   closed in r102

  Status: Fixed

  closed in r102

  Status: Fixed
• Mar 11, 2009

  r102 (Improve the confirmaition message when deleting a question o...) committed by yann.malet   -   Improve the confirmaition message when deleting a question or a choice

  Improve the confirmaition message when deleting a question or a choice
• Mar 11, 2009

  issue 35 (KeyError when editing questions via admin) Status changed by yann.malet   -   fixed in r101

  Status: Fixed

  fixed in r101

  Status: Fixed
• Mar 11, 2009

  issue 36 (ReverseMatch error when attempting to delete questions) Status changed by yann.malet   -   closed in r101 I can now delete a question

  Status: Fixed

  closed in r101 I can now delete a question

  Status: Fixed