django-survey - Google Code

Earlier this year 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 Mar 11, 2009 r101 (closes #36 -- Remove the answers in inlines from the questio...) committed by yann.malet - closes #36 -- Remove the answers in inlines from the question closes #36 -- Remove the answers in inlines from the question Mar 11, 2009 issue 33 (No submission_count) Status changed by yann.malet - patched in r100 Status: Fixed patched in r100 Status: Fixed Mar 11, 2009 r100 (closes #33 -- apply patch proposed by rwpoulton) committed by yann.malet - closes #33 -- apply patch proposed by rwpoulton closes #33 -- apply patch proposed by rwpoulton Mar 11, 2009 issue 34 (Survey title longer than slug length limit errors on save) Status changed by yann.malet - Status: Fixed Status: Fixed Mar 11, 2009 issue 34 (Survey title longer than slug length limit errors on save) commented on by yann.malet - closed in r98 by setting an explicit max_lenght to 255 closed in r98 by setting an explicit max_lenght to 255 Mar 11, 2009 r99 (Add setup.py to enable a pip based installation.) committed by yann.malet - Add setup.py to enable a pip based installation. Add setup.py to enable a pip based installation. Mar 11, 2009 r98 (closes #34 -- The max_length is now explicitely set to 255, ...) committed by yann.malet - closes #34 -- The max_length is now explicitely set to 255, like the title closes #34 -- The max_length is now explicitely set to 255, like the title Mar 11, 2009 issue 26 (Add a "unique" choice) commented on by yann.malet - The patch does not apply cleanly on django-survey. The patch does not apply cleanly on django-survey. Mar 11, 2009 r97 (remove some old selenium tests) committed by yann.malet - remove some old selenium tests remove some old selenium tests Mar 11, 2009 issue 41 (Related field question type) reported by shac...@birdhouse.org - For one survey we need to conduct, we need the user to be able to select from a list of other registered users in the system (managers selecting employees). Because we have more than 5000 registered users, we would also need a way to limit the list of users on that picklist some kind of queryset syntax. A question type that could pull rows from other models in the system would be a realy nice enhancement. What version of the product are you using? On what operating system? 96 For one survey we need to conduct, we need the user to be able to select from a list of other registered users in the system (managers selecting employees). Because we have more than 5000 registered users, we would also need a way to limit the list of users on that picklist some kind of queryset syntax. A question type that could pull rows from other models in the system would be a realy nice enhancement. What version of the product are you using? On what operating system? 96 Mar 11, 2009 issue 40 (Answering survey with checkbox choices generates 500) reported by shac...@birdhouse.org - If you add a Checkbox List question to a survey, django-survey crashes when the survey is submitted by a user: IntegrityError at /survey/detail/2009-newsroom-training-survey/ (1062, "Duplicate entry '4-baeb0b83bf52d26e9daef123dfb1d157' for key 2") This happens even if the user has chosen only one of the choices. What version of the product are you using? On what operating system? 96 w/MySQL 5 If you add a Checkbox List question to a survey, django-survey crashes when the survey is submitted by a user: IntegrityError at /survey/detail/2009-newsroom-training-survey/ (1062, "Duplicate entry '4-baeb0b83bf52d26e9daef123dfb1d157' for key 2") This happens even if the user has chosen only one of the choices. What version of the product are you using? On what operating system? 96 w/MySQL 5 Mar 11, 2009 issue 39 (Wrong confirmation msg when deleting a question) reported by shac...@birdhouse.org - When you attempt to delete a question, the confirmation prompt says "Are you sure you want to delete this survey" rather than "Are you sure you want to delete this question?" Clicking OK actually deletes the question, not the survey, but it scares the hell out of your manager :) What version of the product are you using? On what operating system? 96 When you attempt to delete a question, the confirmation prompt says "Are you sure you want to delete this survey" rather than "Are you sure you want to delete this question?" Clicking OK actually deletes the question, not the survey, but it scares the hell out of your manager :) What version of the product are you using? On what operating system? 96 Mar 03, 2009 issue 33 (No submission_count) commented on by rwpoulton - submission_count is incorrect, the code should be referring to the interview_count property. In templates/survey/editable_survey_list.html and templates/survey/survey_list.html, change all references to submission_count to interview_count. The attached diff will do that for you (against svn r96). submission_count is incorrect, the code should be referring to the interview_count property. In templates/survey/editable_survey_list.html and templates/survey/survey_list.html, change all references to submission_count to interview_count. The attached diff will do that for you (against svn r96). Mar 03, 2009 issue 38 (Allow definition of 'next_page' in Survey model [patch attac...) reported by rwpoulton - There is currently the ability to add '?next=' to a URL when linking a user to a survey. However I would like to be able to redirect a user to a page unrelated to the survey when they submit their answers, without having to manually set the ?next GET param each time I send a user to the survey. I will be sending the survey link to my users via e-mail, and I want it to be as neat & tidy as possible. This patch adds a new option on the Survey model to add this functionality. By defining the next_page on a Survey, the redirect will be done automatically. If next_page is left blank, then the existing redirection functionality is kept in place (eg it uses ?next, or shows the answers, depending on the users permissions). This is a very small change but provides quite useful functionality for my particular use. I haven't discussed this on the list, but it fixes a pain I've had for a while. Hopefully others find it useful, and it'd be nice to see it put into trunk. NOTE: You will need to complete a small schema change to make this work: UPDATE survey_survey ADD "next_page" varchar(200); There is currently the ability to add '?next=' to a URL when linking a user to a survey. However I would like to be able to redirect a user to a page unrelated to the survey when they submit their answers, without having to manually set the ?next GET param each time I send a user to the survey. I will be sending the survey link to my users via e-mail, and I want it to be as neat & tidy as possible. This patch adds a new option on the Survey model to add this functionality. By defining the next_page on a Survey, the redirect will be done automatically. If next_page is left blank, then the existing redirection functionality is kept in place (eg it uses ?next, or shows the answers, depending on the users permissions). This is a very small change but provides quite useful functionality for my particular use. I haven't discussed this on the list, but it fixes a pain I've had for a while. Hopefully others find it useful, and it'd be nice to see it put into trunk. NOTE: You will need to complete a small schema change to make this work: UPDATE survey_survey ADD "next_page" varchar(200); Feb 27, 2009 issue 37 (Docs for recipient type, recipient id) reported by shac...@birdhouse.org - Because recipient type and recipient ID are required fields but are not auto-entered when creating a survey via /survey/add , it's not possible to edit+save a survey via the admin (because one doesn't know what to enter in these fields). Can we get some documentation on the purpose of these fields, how to use them etc.? Thanks. Because recipient type and recipient ID are required fields but are not auto-entered when creating a survey via /survey/add , it's not possible to edit+save a survey via the admin (because one doesn't know what to enter in these fields). Can we get some documentation on the purpose of these fields, how to use them etc.? Thanks. Feb 27, 2009 issue 36 (ReverseMatch error when attempting to delete questions) reported by shac...@birdhouse.org - Clicking Delete for any question results in: NoReverseMatch at /survey/question/delete/2009-newsroom-training-survey/6/ Reverse for 'survey-edit' with arguments '()' and keyword arguments '{'survey_slug': u'2009-newsroom-training-survey', 'group_slug': None}' not found. Since it's also not possible to click any question in the admin without crashing Django, deleting questions is difficult. Clicking Delete for any question results in: NoReverseMatch at /survey/question/delete/2009-newsroom-training-survey/6/ Reverse for 'survey-edit' with arguments '()' and keyword arguments '{'survey_slug': u'2009-newsroom-training-survey', 'group_slug': None}' not found. Since it's also not possible to click any question in the admin without crashing Django, deleting questions is difficult. Feb 27, 2009 issue 35 (KeyError when editing questions via admin) reported by shac...@birdhouse.org - Click any question in the admin to edit it directly and you get: KeyError at /admin/survey/question/2/ 'question' No problem editing questions through the survey interface, but this should probably be fixed. Click any question in the admin to edit it directly and you get: KeyError at /admin/survey/question/2/ 'question' No problem editing questions through the survey interface, but this should probably be fixed. Feb 27, 2009 issue 34 (Survey title longer than slug length limit errors on save) reported by shac...@birdhouse.org - Attempt to create a survey with a very long length such as "Knight Digital Media Center at UC Berkeley 2009 Newsroom Training Survey" and end user gets a 500 error. Solution is to create survey title with shorter slug from the admin, but that's not an end-user oriented solution. Attempt to create a survey with a very long length such as "Knight Digital Media Center at UC Berkeley 2009 Newsroom Training Survey" and end user gets a 500 error. Solution is to create survey title with shorter slug from the admin, but that's not an end-user oriented solution. Feb 27, 2009 issue 33 (No submission_count) reported by shac...@birdhouse.org - After creating a survey and submitting several test submissions by various users, the Info column on /survey/visible and /survey/editable says "No submissions" and no link is provided to view results. However, I can go manually to /survey/answers/slug and see the compiled results. In other words, survey.submission_count is turning up empty. This is true both with the provided example site and my implemented version. Any ideas why? Using Django 1.1 alpha. Great pluggable app by the way! Thanks. After creating a survey and submitting several test submissions by various users, the Info column on /survey/visible and /survey/editable says "No submissions" and no link is provided to view results. However, I can go manually to /survey/answers/slug and see the compiled results. In other words, survey.submission_count is turning up empty. This is true both with the provided example site and my implemented version. Any ideas why? Using Django 1.1 alpha. Great pluggable app by the way! Thanks. Older Dec 26, 2008 issue 24 (syncdb raises exception) commented on by Mark0978 - Still a problem with MySQL that should be fixed in the DJango cod, but hasn't been. Problem has been around since Jun 2008 Comment out the unique_together(...) call, syncdb, then turn it back on..... Can't find any docs on unique_together, but if you could specify a keylength, maybe this could be fixed here..... Still a problem with MySQL that should be fixed in the DJango cod, but hasn't been. Problem has been around since Jun 2008 Comment out the unique_together(...) call, syncdb, then turn it back on..... Can't find any docs on unique_together, but if you could specify a keylength, maybe this could be fixed here..... Oct 30, 2008 issue 28 (Does not work with Python2.4 because uuid.py can not be impo...) commented on by yann.malet - I have added a note in http://code.google.com/p/django-survey/wiki/GettingStarted You can also easy_install it in your Python 2.4 or use virtualenv. --yml I have added a note in http://code.google.com/p/django-survey/wiki/GettingStarted You can also easy_install it in your Python 2.4 or use virtualenv. --yml Oct 30, 2008 GettingStarted (How to get it, and what to do when you've got it.) Wiki page edited by yann.malet Oct 29, 2008 issue 28 (Does not work with Python2.4 because uuid.py can not be impo...) commented on by MountainPaul - I can definitely see why you would not make this change to the source (it is sort of a kluge), after all the install or (Django) would have to copy the uuid.py file from Python 2.5 into utils directory. Plus how if it changes how does one ensure it gets updated. Would adding the path to /usr/lib/python2.5 and running python2.4 cause some conflicts/problems with /usr/lib/python2.4 ? For example a user could use another Django (or other python app) that would try to use a 2.5 module that would not be compatible with 2.4(and does not exist in 2.4). It seems an import error would be easier to track down than some incompatibility. In my case I decide to rebuild wsgi to use python 2.5, so the problem is now moot for me. FYI, I stole the original solution from another django app (sorry, I forgot which one). I would suggest that somewhere in the docs or the wiki that perhaps 2.5 should be mentioned as a requirement. I don't think it is necessary to support all the way down to 2.3 (which Django does). I can definitely see why you would not make this change to the source (it is sort of a kluge), after all the install or (Django) would have to copy the uuid.py file from Python 2.5 into utils directory. Plus how if it changes how does one ensure it gets updated. Would adding the path to /usr/lib/python2.5 and running python2.4 cause some conflicts/problems with /usr/lib/python2.4 ? For example a user could use another Django (or other python app) that would try to use a 2.5 module that would not be compatible with 2.4(and does not exist in 2.4). It seems an import error would be easier to track down than some incompatibility. In my case I decide to rebuild wsgi to use python 2.5, so the problem is now moot for me. FYI, I stole the original solution from another django app (sorry, I forgot which one). I would suggest that somewhere in the docs or the wiki that perhaps 2.5 should be mentioned as a requirement. I don't think it is necessary to support all the way down to 2.3 (which Django does). Oct 29, 2008 issue 30 (A survey having been taken is tied only to the session.. and...) changed by yann.malet - The modification that you propose there sounds very reasonable to me. It would be nice if next time that you submit a patch that bring new capability you could add some tests. Thank you for your recent contributions. --yml Status: Fixed Owner: yann.malet Labels: Type-Enhancement −Type-Defect The modification that you propose there sounds very reasonable to me. It would be nice if next time that you submit a patch that bring new capability you could add some tests. Thank you for your recent contributions. --yml Status: Fixed Owner: yann.malet Labels: Type-Enhancement −Type-Defect Oct 29, 2008 issue 27 (Allow permissions for who can edit a survey to include group...) changed by yann.malet - Status: WontFix Owner: yann.malet Status: WontFix Owner: yann.malet Oct 29, 2008 issue 28 (Does not work with Python2.4 because uuid.py can not be impo...) changed by yann.malet - Hello, I would prefer to avoid checking in external code in that repository. If you want to use python 2.4 I would advise you to have uuid in your PYTHONPATH. Like this you will be able to use django-survey without patching it. --yml Status: WontFix Owner: yann.malet Hello, I would prefer to avoid checking in external code in that repository. If you want to use python 2.4 I would advise you to have uuid in your PYTHONPATH. Like this you will be able to use django-survey without patching it. --yml Status: WontFix Owner: yann.malet

issue 38 (Allow definition of 'next_page' in Survey model [patch attac...) reported by rwpoulton - There is currently the ability to add '?next=' to a URL when linking a user to a survey. However I would like to be able to redirect a user to a page unrelated to the survey when they submit their answers, without having to manually set the ?next GET param each time I send a user to the survey. I will be sending the survey link to my users via e-mail, and I want it to be as neat & tidy as possible. This patch adds a new option on the Survey model to add this functionality. By defining the next_page on a Survey, the redirect will be done automatically. If next_page is left blank, then the existing redirection functionality is kept in place (eg it uses ?next, or shows the answers, depending on the users permissions). This is a very small change but provides quite useful functionality for my particular use. I haven't discussed this on the list, but it fixes a pain I've had for a while. Hopefully others find it useful, and it'd be nice to see it put into trunk. NOTE: You will need to complete a small schema change to make this work: UPDATE survey_survey ADD "next_page" varchar(200);

There is currently the ability to add '?next=' to a URL when linking a user to a survey. However I would like to be able to redirect a user to a page unrelated to the survey when they submit their answers, without having to manually set the ?next GET param each time I send a user to the survey. I will be sending the survey link to my users via e-mail, and I want it to be as neat & tidy as possible. This patch adds a new option on the Survey model to add this functionality. By defining the next_page on a Survey, the redirect will be done automatically. If next_page is left blank, then the existing redirection functionality is kept in place (eg it uses ?next, or shows the answers, depending on the users permissions). This is a very small change but provides quite useful functionality for my particular use. I haven't discussed this on the list, but it fixes a pain I've had for a while. Hopefully others find it useful, and it'd be nice to see it put into trunk. NOTE: You will need to complete a small schema change to make this work: UPDATE survey_survey ADD "next_page" varchar(200);

Earlier this year

Older