Giter VIP home page Giter VIP logo

django-survey's People

django-survey's Issues

Support newforms-admin

We should support the newforms-admin and we do not need to wait for it to
be merged. peschler has requested this feature and has offered to work on it.
With that in mind I am creating a newforms-admin branch, this enhancement
request, and assigning it to peschler.

I would not try to go overboard with the admin fanciness like I did with
the old admin. Yann has already done a lot of work to create proper forms
for building surveys, and I see the admin as just that, and superuser admin.

Original issue reported on code.google.com by [email protected] on 8 May 2008 at 7:58

Multipage surveys

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

Original issue reported on code.google.com by [email protected] on 23 Mar 2009 at 9:39

syncdb raises exception

What steps will reproduce the problem?
./manage.py syncdb

What is the expected output? What do you see instead?

_mysql_exceptions.OperationalError: (1170, "BLOB/TEXT column 'text' used in
key specification without a key length")

What version of the product are you using? On what operating system?

Trunk on OSX with MySQL5

Please provide any additional information below.

Looking at ./manage.py sqlall survey I longtext `text` field might be the
culprit:

CREATE TABLE `survey_question` (
    `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
    `survey_id` integer NOT NULL,
    `qtype` varchar(2) NOT NULL,
    `required` bool NOT NULL,
    `text` longtext NOT NULL,
    `order` integer NULL,
    `image` varchar(100) NULL,
    `choice_num_min` integer NULL,
    `choice_num_max` integer NULL,
    `qstyle` longtext NULL,
    `_order` integer NULL,
    UNIQUE (`survey_id`, `text`)
)

Trying to UNIQUE a longtext field ... the attached patch seems to have
fixed it but only by using a varchar. patch also includes a typo fix.


Original issue reported on code.google.com by [email protected] on 2 Oct 2008 at 11:26

Attachments:

Set up the internationalization infrastructure

This issue will be used to track the progress of the internationalization
(i18n). The following tasks need to be performed :
  * Mark all the strings with this templatetag in all the templates {%
trans "Translate this string" %}
  * Mark all the strings with _() in the python files
  * Create the message files as place holder for the a couple of language :
spannish, german, french

I plan to use django-rosetta as part of the infrastructure, this will lower
the barrier  in collecting the translation string from hypothetic contributor.



Original issue reported on code.google.com by [email protected] on 27 May 2008 at 7:06

Non-staff can

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

Original issue reported on code.google.com by [email protected] on 12 Mar 2009 at 6:35

Some views were accepting a template argument but never actually using it

Some views had a template_name argument with a default value that was not the 
correct default for 
a view, and in the render clause the template_name passed it was not being used 
at all.

Also the 'survey_update()' view looked like it was just a copy and paste of the 
'survey_add()' view, 
which was passing in the wrong 'title' variable to the context. What is more it 
is handy if the context 
had the survey object if we actually have it.

Attached is a patch that fixes (well, I am assuming these were mistakes) this.
This is against subversion revision 92.


Original issue reported on code.google.com by [email protected] on 28 Oct 2008 at 4:24

Attachments:

label for="id_answer" isn't quite right

Something isn't quite right, but I can't figure out where it is failing.


        <div>
<label for="id_answer">Company Name :</label>
 <span class="helptext">(this question is optional)</span> 
<input name="1_1-answer" id="id_1_1-answer" type="text">
        </div>

comes from

<label for="id_{{ bound_field.name }}">{{ bound_field.label }}
...
{{ bound_field }} 

"The id attribute values are generated by prepending id_ to the form field
names." 
http://www.djangoproject.com/documentation/forms/#configuring-html-label-tags

but in django?  (I have not svn up'ed yet - still running on something from
before the nfAdmin merge)

Original issue reported on code.google.com by [email protected] on 23 Jul 2008 at 6:58

minor 2.4 issues

I was getting a syntax error because there is one line of 2.5 specific code
... here's the patch for python 2.4 compatibility, not sure if that's a target.

Index: forms.py
===================================================================
--- forms.py    (revision 36)
+++ forms.py    (working copy)
@@ -172,7 +172,10 @@
     session_key = request.session.session_key.lower()
     login_user = request.user
     random_uuid = uuid.uuid4().hex
-    post = request.POST if request.POST else None # bug in newforms
+    if request.POST: # bug in newforms
+        post = request.POST 
+    else:
+        post = None 
     return [QTYPE_FORM[q.qtype](q, login_user, random_uuid, session_key,
prefix=sp+str(q.id), data=post)
             for q in survey.questions.all().order_by("order") ]

Original issue reported on code.google.com by [email protected] on 29 May 2008 at 12:02

Add an interview table to help custom query reports.

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.

Original issue reported on code.google.com by [email protected] on 10 Apr 2009 at 6:05

Image management for Question and Choice

The models.py for Question and Choice enable an administrator to add an image. 
As of now there is several problem associated with this feature : 
 * the settings.py do not provide with a reasonable default
 * It is impossible to delete a file in admin interface. This issue might
be solved by newforms-admin
 * The files are not displayed in survey_detail (need to modify the template)
 * It is impossible to add an image to a question using question_add and
question_update
 * It is impossible to add an image to a choice using choice_add and
choice_update

I will use this ticket to track the progress I am making in this area.


Original issue reported on code.google.com by [email protected] on 26 May 2008 at 3:38

Adding multiple type choices in a question

At the moment i can make a question with one kind of response (Select One 
Choice, Text Input, Radio List, etc).
Is possible to make this kind of question?

1. Question? 
- Answer1
- Answer2
- Answer3
- other __________________ (write something)

In this case there is a Radio List in wich the fourth element may be a Text 
Input.

Is possible to do this?


What version of the product are you using? On what operating system?
django 1.1.1, Apache 2.2, Linux

Thank you very much.


Original issue reported on code.google.com by [email protected] on 13 Jul 2010 at 2:26

Add a "unique" choice

I'm using django-survey as a quick data-entry tool, and wanted some way of
removing a choice once one of the users has answered with it (e.g. only
allow ONE answer for each choice in a given question).

To do this, I added a "UniqueChoiceField" - diff attached.

Probably not worth adding to django-survey on the whole, but I've put it
here in case anyone finds it useful

Original issue reported on code.google.com by [email protected] on 19 Oct 2008 at 2:24

Attachments:

Related field question type

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

Original issue reported on code.google.com by [email protected] on 12 Mar 2009 at 12:42

Wrong confirmation msg when deleting a question

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


Original issue reported on code.google.com by [email protected] on 11 Mar 2009 at 11:43

Submissions count off by one

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



Original issue reported on code.google.com by [email protected] on 18 Mar 2009 at 11:30

Default example site does not contain core site html

The examples site should behave like a fully functional website.
That is, you should have a main page at the root with instructions and
links to the google project.

this used to be the case at one point, but no longer is.
marking this as an enhancement as the core stuff does work.

Original issue reported on code.google.com by [email protected] on 17 Jun 2008 at 9:24

Edit a survey in a single page

Write the view and the template to create/update a survey. As of now I
imagine a single page where you could :
  * create /update / delete question and Choice
  * Set the order of the questions and choice (Move up, move down)

This will be done using ajax call to get and display the forms. Then this
form will be submitted to the server. 



Original issue reported on code.google.com by [email protected] on 2 May 2008 at 2:50

<div None>

        <div {{ bound_field.form.question.qstyle|safe}}>

If no qstyle is set, you get <div None> which is... 

fix:
        <div {{ bound_field.form.question.qstyle|default_if_none:""|safe}}>


Original issue reported on code.google.com by [email protected] on 22 Jul 2008 at 8:19

transferring the ownership of a survey

This enhancement should enable the creator of a survey to transfer the
ownership of a survey to another user. I see two folds in this feature :
  * one is to be able to keep in memory the intention. The user X wants to
transfer the "Survey 1" to the user Y. In addition we need to keep track of
the date and the validity period of this offer.
  * the second is to actually notify user Y that user X want to transfer
the "Survey 1". From there user Y could accept or deny the offer.

I am under the impression that the second part could be fulfill by Pinax or
one of its components. 
--yml


Original issue reported on code.google.com by [email protected] on 27 May 2008 at 7:35

Allow definition of 'next_page' in Survey model [patch attached]

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);

Original issue reported on code.google.com by [email protected] on 3 Mar 2009 at 8:33

Attachments:

Don't use "local" imports

Not sure if local is the right word.  Looking at:

http://code.google.com/p/django-survey/source/browse/trunk/survey/views.py?r=18

Pretty sure the best convention here to use the package name like 

from survey.models import Survey, ...

rather than:  

from models import Survey, ...

Original issue reported on code.google.com by [email protected] on 28 May 2008 at 5:01

Raw HTML escape for ChoiceImage

What steps will reproduce the problem?
1. Add a question with the type Radio Image List
2. point your Browser to survey_detail

What is the expected output?
* See the image
What do you see instead?
* I see an escaped html string


What version of the product are you using? 
svn trunk
Please provide any additional information below.
the patch is included

I hope that help.
--yml

I would like to know what is the most appropriate channel to exchange with
the core developers of that project. Is there a mailing list somewhere ?
I have been working on something similar in the past months :
https://launchpad.net/django-survey/
Thank you

Original issue reported on code.google.com by [email protected] on 28 Mar 2008 at 1:26

Attachments:

extra () in ((this question is optional))

There are () being used in 2 places, which results in an extra set:

forms.py                                                                  


        if not question.required:
            answer.help_text = unicode(_('(this question is optional)'))

templates/newforms/field.html
{% if bound_field.help_text %} <span class="helptext">({{
bound_field.help_text }})</span> {% endif %}


 <span class="helptext">((this question is optional))</span> 

Original issue reported on code.google.com by [email protected] on 22 Jul 2008 at 5:48

Checkbox List with no image fails when taking survey.. (error in ChoiceCheckbox form in forms.py)

What steps will reproduce the problem?
1. Create a survey with a  Checkbox List, and no specified image
2. Take the survey.

What is the expected output? What do you see instead?

A survey with a choice checkbox list.
Instead it fails with an exception of ValueError because the image has no file 
associated with it.

What version of the product are you using? On what operating system?

subversion revision 92.

Please provide any additional information below.

By patching the form from:

"if opt.image.url:" to "if opt.image and opt.image.url:" fixes this (on line 
129 of forms.py)


Original issue reported on code.google.com by [email protected] on 28 Oct 2008 at 3:36

example survey site broken

The example survey site is broken.
The examples database is not synced with the current models, and all of the
default main site views are missing.

Original issue reported on code.google.com by [email protected] on 13 Jun 2008 at 12:13

extra /

        <div>{% if view_submissions %}<a href='{% url answers-detail
survey_slug=survey.slug,key=answer.session_key %}/'>

makes this:

http://pycon08a:8000/survey/answers/b/a32a80142c0e7d9ab3b3a2b954036941//

The extra / at the end does not match the pattern it should:

    url(r'^answers/(?P<survey_slug>[-\w]+)/(?P<key>[a-fA-F0-9]{10,40})/$',
        answers_detail,  name='answers-detail'),

+        <div>{% if view_submissions %}<a href='{% url answers-detail
survey_slug=survey.slug,key=answer.session_key %}'>

Ran 3 tests in 1.096s
OK

and now I don't get a 404 :)



Original issue reported on code.google.com by [email protected] on 18 Jul 2008 at 5:22

KeyError when editing questions via admin

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.

Original issue reported on code.google.com by [email protected] on 28 Feb 2009 at 12:10

Add question type "checkbox list"

This is not an issue but rather an enhancement. The goal of this patch is
to enable the an additional question type : "check box list"

The most important part of the patch has been proposed by Doug on the
mailing list. I have added a couple of modification to make it works.

The biggest impact is that I had to comments the following line in models.py : 
  * # unique_together = (('question', 'session_key'),)
It is part of the class Answer. 

--yml

Original issue reported on code.google.com by [email protected] on 3 Apr 2008 at 12:05

Attachments:

Checkbox answers don't save with user.

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.

Original issue reported on code.google.com by [email protected] on 10 Aug 2009 at 5:56

Attachments:

No submission_count

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.

Original issue reported on code.google.com by [email protected] on 27 Feb 2009 at 11:08

make Survey:Question M:M

I need to make 6 surveys, and the first 12 questions of each are all the
same.  it would be nice if I could define the question once, and assign it
to multiple surveys.  

This let me add the data:

    survey = models.ManyToManyField(Survey, related_name='questions',

            new_question = question_form.save(commit=False)
            new_question.save()
            new_question.survey.add( survey )

above hack doesn't let me take the survey: 
http://dhcp11:8002/survey/visible/

I am guessing there is something checking for at least on question, and
that needs to be fixed.  

I think answers will have to be a child of the intersect table, no clue how
to do that in django.  maybe just add a FK to survey?

I didn't want to burn up too much time on this - maybe there is a better
implementation, like let one survey contain sub-surveys.  (kinda liking
this idea better.)



Original issue reported on code.google.com by [email protected] on 17 Jul 2008 at 1:08

Allow permissions for who can edit a survey to include groups, not just users.

Right now you have surveys editable by the owner and a list of users. It would 
be really 
convenient if you could permit them to a group as well. I make surveys and have 
a group of 
users that I want to permit to edit them.

Of course, this would be really nice if we had row level permissions instead to 
handle this.

Basically the change I am after would add a new field to the model like:

editable_by_group = models.ForeignKey(Group)

and then in the 'editable_survey_list()' view, an additional Q clause:

'queryset': Survey.objects.filter(Q(created_by=login_user) |
                                            Q(editable_by=login_user | Q(editable_by_group__in = 
login_user.groups.all())),



Original issue reported on code.google.com by [email protected] on 24 Oct 2008 at 9:42

runtests errors

What steps will reproduce the problem?
1. svn checkout http://django-survey.googlecode.com/svn/trunk/
django-survey-read-only

2. cd django-survey-read-only/tests/
3. . runtests.sh 


What is the expected output? 
no error.
What do you see instead?
error.

What version of the product are you using? On what operating system?
Checked out revision 76.

Please provide any additional information below.

Checked out revision 76.
juser@pycon08a:~/temp$ cd django-survey-read-only/tests/
juser@pycon08a:~/temp/django-survey-read-only/tests$ . runtests.sh 
Restored 'examples.db'
At revision 76.
E
======================================================================
ERROR: test_new (__main__.NewTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "survey_selenium.py", line 8, in setUp
    self.selenium.start()
  File "/home/juser/temp/django-survey-read-only/tests/selenium.py", line
166, in start
    result = self.get_string("getNewBrowserSession",
[self.browserStartCommand, self.browserURL])
  File "/home/juser/temp/django-survey-read-only/tests/selenium.py", line
195, in get_string
    result = self.do_command(verb, args)
  File "/home/juser/temp/django-survey-read-only/tests/selenium.py", line
191, in do_command
    raise Exception, data
Exception

----------------------------------------------------------------------
Ran 1 test in 0.379s

FAILED (errors=1)
[1]-  Terminated              python manage.py runserver > /dev/null 2>
/dev/null
Restored 'examples.db'
At revision 76.
[2]+  Exit 143                java -jar ~/lib/java/selenium-server.jar >
/dev/null 2> /dev/null  (wd: ~/temp/django-survey-read-only/tests)
(wd now: ~/temp/django-survey-read-only/examples)
juser@pycon08a:~/temp/django-survey-read-only/tests$ 


Original issue reported on code.google.com by [email protected] on 18 Jul 2008 at 12:28

TypeError: 'core' is not a valid argument for <class 'django.db.models.fields.files.ImageField'

What steps will reproduce the problem?
1. python manage.py syncdb
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?
Django version 1.0-alpha_2-SVN-8339, Python 2.5.1, Windows, Postgres

Please provide any additional information below.
Traceback (most recent call last):
  File "manage.py", line 11, in <module>
    execute_manager(settings)
  File "C:\Python25\lib\site-packages\django\core\management\__init__.py",
line 334, in execute_manager
    utility.execute()
  File "C:\Python25\lib\site-packages\django\core\management\__init__.py",
line 295, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "C:\Python25\lib\site-packages\django\core\management\base.py", line
77, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "C:\Python25\lib\site-packages\django\core\management\base.py", line
95, in execute
    self.validate()
  File "C:\Python25\lib\site-packages\django\core\management\base.py", line
122, in validate
    num_errors = get_validation_errors(s, app)
  File
"C:\Python25\lib\site-packages\django\core\management\validation.py", line
28, in get_validation_errors
    for (app_name, error) in get_app_errors().items():
  File "C:\Python25\lib\site-packages\django\db\models\loading.py", line
128, in get_app_errors
    self._populate()
  File "C:\Python25\lib\site-packages\django\db\models\loading.py", line
57, in _populate
    self.load_app(app_name, True)
  File "C:\Python25\lib\site-packages\django\db\models\loading.py", line
72, in load_app
    mod = __import__(app_name, {}, {}, ['models'])
  File "C:\Projects\pyapps\dot\gem\models.py", line 820, in <module>
    model_signals = SignalRegister()
  File "C:\Projects\pyapps\dot\gem\signals.py", line 88, in __init__
    g =
Game.objects.values('team_profile_module').order_by('team_profile_module').disti
nct()
  File "C:\Python25\lib\site-packages\django\db\models\manager.py", line
114, in values
    return self.get_query_set().values(*args, **kwargs)
  File "C:\Python25\lib\site-packages\django\db\models\query.py", line 431,
in values
    return self._clone(klass=ValuesQuerySet, setup=True, _fields=fields)
  File "C:\Python25\lib\site-packages\django\db\models\query.py", line 596,
in _clone
    c._setup_query()
  File "C:\Python25\lib\site-packages\django\db\models\query.py", line 660,
in _setup_query
    self.query.add_fields(field_names, False)
  File "C:\Python25\lib\site-packages\django\db\models\sql\query.py", line
1425, in add_fields
    True)
  File "C:\Python25\lib\site-packages\django\db\models\sql\query.py", line
1204, in setup_joins
    field, model, direct, m2m = opts.get_field_by_name(name)
  File "C:\Python25\lib\site-packages\django\db\models\options.py", line
274, in get_field_by_name
    cache = self.init_name_map()
  File "C:\Python25\lib\site-packages\django\db\models\options.py", line
300, in init_name_map
    for f, model in self.get_all_related_m2m_objects_with_model():
  File "C:\Python25\lib\site-packages\django\db\models\options.py", line
377, in get_all_related_m2m_objects_with_model
    cache = self._fill_related_many_to_many_cache()
  File "C:\Python25\lib\site-packages\django\db\models\options.py", line
391, in _fill_related_many_to_many_cache
    for klass in get_models():
  File "C:\Python25\lib\site-packages\django\db\models\loading.py", line
136, in get_models
    self._populate()
  File "C:\Python25\lib\site-packages\django\db\models\loading.py", line
57, in _populate
    self.load_app(app_name, True)
  File "C:\Python25\lib\site-packages\django\db\models\loading.py", line
72, in load_app
    mod = __import__(app_name, {}, {}, ['models'])
  File "C:\Python25\lib\site-packages\survey\models.py", line 159, in <module>
    class Question(models.Model):
  File "C:\Python25\lib\site-packages\survey\models.py", line 172, in Question
    null=True, blank= True, core=False)
  File "C:\Python25\lib\site-packages\django\db\models\fields\files.py",
line 283, in __init__
    FileField.__init__(self, verbose_name, name, **kwargs)
  File "C:\Python25\lib\site-packages\django\db\models\fields\files.py",
line 131, in __init__
    raise TypeError("'%s' is not a valid argument for %s." % (arg,
self.__class__))
TypeError: 'core' is not a valid argument for <class
'django.db.models.fields.files.ImageField'>.

Original issue reported on code.google.com by [email protected] on 22 Aug 2008 at 1:55

Attachments:

ReverseMatch error when attempting to delete questions

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.

Original issue reported on code.google.com by [email protected] on 28 Feb 2009 at 12:14

Docs for recipient type, recipient id

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.


Original issue reported on code.google.com by [email protected] on 28 Feb 2009 at 12:29

'AdminSite' object has no attribute 'root' when example is run.

What steps will reproduce the problem?
1. download the latest version
2. manage.py runserver
3. try to hit /admin url - you will get an errro

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?
django 1.3.1

Please provide any additional information below.

urls.py mentions:
(r'^admin/(.*)', admin.site.root),
but admin.site.root does not appear to exist ?

>>> from django.contrib import admin
>>> print admin.site.root
Traceback (most recent call last):
  File "<console>", line 1, in <module>
AttributeError: 'AdminSite' object has no attribute 'root'

i get same message on the browser:
AttributeError at /
'AdminSite' object has no attribute 'root'Request Method: GET 
Request URL: http://127.0.0.1:8000/ 
Django Version: 1.3.1 
Exception Type: AttributeError 
Exception Value: 'AdminSite' object has no attribute 'root' 
Exception Location: C:\temp\git_repo\examples\urls.py in <module>, line 11 
Python Executable: C:\Python27\python.exe 
Python Version: 2.7.2 

Original issue reported on code.google.com by [email protected] on 10 May 2012 at 8:03

a number of survey url patterns using '\d' instead of '\d+' ... more then 10 questions or 10 choices and bad stuff..

What steps will reproduce the problem?

Create more then 10 questions, or more then 10 choices.

What is the expected output? What do you see instead?

You instead get a 500 error because likely the 'reverse()' pattern for the 
question or choice no 
longer matches.

What version of the product are you using? On what operating system?

Subversion version 92.

Please provide any additional information below.

The problem is the several url patterns that use "\d" instead of "\d+" to find 
a question or choice 
id, for example:

url(r'^choice/add/(?P<question_id>\d)/$', choice_add,   name='choice-add'),

Please find attached a patch that fixes this.




Original issue reported on code.google.com by [email protected] on 28 Oct 2008 at 11:01

Attachments:

A survey having been taken is tied only to the session.. and is easy to work around (and can be confusing.)

The issue is that we need surveys that can only be taken once by any one 
authenticated user.
However, the session key is used to determine if a user has taken the survey or 
not.

If a user logs out and then logs back in, they will no longer be considered to 
have taken the 
survey. I can see where using the session id works somewhat for anonymous users 
and this way 
you only have to worry about one mechanism for seeing if a survey has been 
taken.

However, this method seems exceptionally fragile. In our case, we want our 
users to take some 
surveys only once. Once they have taken them, we do not want them to be able to 
see the survey 
again. The curious thing is this is not because we can not trust them to try to 
jack the survey 
results, but they are trained to take a survey when they see it.

As it is now, they log out.. they come back later, or on a different machine, 
they see the survey 
again. They are a little bit confused, but since they can see the survey they 
figure that they must 
take it again, and do so.

I wager this is likely to be met with resistance, but I think for authenticated 
users you should use 
the user as the determining factor of whether they have taken a survey already.

The way I worked around it for our case was to add a 'has_answers_from_user' 
method to the 
survey model, and if the user is authenticated then check 
'has_answers_from_user' after checking 
'has_answers_from()' in 'survey_detail' in views.py at line 85.

This is based on subversion revision 92.



Original issue reported on code.google.com by [email protected] on 28 Oct 2008 at 3:52

Survey locking

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





Original issue reported on code.google.com by [email protected] on 19 Mar 2009 at 12:54

Answering survey with checkbox choices generates 500

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




Original issue reported on code.google.com by [email protected] on 12 Mar 2009 at 12:30

self.open missing()


http://code.google.com/p/django-survey/source/browse/trunk/survey/models.py#101

    def status(self):

-        if self.open: return _('open')
+        if self.open(): return _('open')

Ran 3 tests in 1.072s
OK
need more?

Original issue reported on code.google.com by [email protected] on 18 Jul 2008 at 5:12

dont force start/end

Seems odd that Survey.opens and .closes are required.

I know it is easy enough to stuff bogus date/times into the fields....


Original issue reported on code.google.com by [email protected] on 17 Jul 2008 at 12:55

Add an interview table to help custom query reports.

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.

Original issue reported on code.google.com by [email protected] on 10 Apr 2009 at 6:01

Survey title longer than slug length limit errors on save

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.

Original issue reported on code.google.com by [email protected] on 27 Feb 2009 at 11:47

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.