This release is a pre-release and may not be stable for production use.
django-voice
django-voice integrates user feedback with your Django project. Originally built for Verb (http://verbapp.com).
IMPORTANT: Upgrading to 0.4 from older versions
If you upgrade django-voice to 0.4 from older versions, you will take an error about database changing:
DatabaseError at /feedback/ no such column: djangovoice_feedback.email
You have two ways for fixing the problem.
If you want to use South..
Fake the first migration and run the second migration:
python manage.py migrate --fake djangovoice 0001 python manage.py migrate djangovoice
If you don’t want to use South..
Open your SQL shell and add email column to djangovoice_feedback:
python manage.py dbshell sqlite> ALTER TABLE "djangovoice_feedback" ADD COLUMN "email" varchar(75) NULL; sqlite> ALTER TABLE "djangovoice_feedback" ADD COLUMN "slug" varchar(10) NULL;
That’s it..
Installation and Dependencies
To satisfy dependencies listed in REQUIREMENTS you can simply run this command:
pip install -r requirements.txt
‘pip’ will automatically download and install dependencies required for django-voice. Next step is activating helper applications to run.
Activate django’s comment system. (https://docs.djangoproject.com/en/dev/ref/contrib/comments/)
Add django-gravatar (optional) and qhonuskan-votes to your INSTALLED_APPS in settings file.
Add comments and django-voice to your url configration.
Create at least one Type and Status either through the admin or fixtures.
After these steps, your INSTALLED_APPS in settings.py must be seen like this:
INSTALLED_APPS = (
...
'django.contrib.comments',
'qhonuskan_votes',
'gravatar', # it's optional dependency
'djangovoice'
)
and urls.py like this:
urlpatterns = patterns(
...
url(r'^comments/', include('django.contrib.comments.urls')),
url(r'^feedback/', include('djangovoice.urls')))
Remember to create and save at least one Type and Status model instance.
That’s all you need to run django-voice.
Settings
VOICE_ALLOW_ANONYMOUS_USER_SUBMIT (default: False) Allow anonymous user to submit feedback. Asks for email and marks the feedback as private to hide the email and prevent spam. VOICE_BRAND_VIEW (default: 'djangovoice_home') The view associated with clicking the brand logo in the top left of the bootstrap navbar.
Metadata
Release files for django-voice 0.5alpha
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django-voice-0.5alpha.tar.gz | 119.3 kB | Without provenance | Details for django-voice-0.5alpha.tar.gz |
Release files / django-voice-0.5alpha.tar.gz
| Download URL | django-voice-0.5alpha.tar.gz |
|---|---|
| Size | 119.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9afa3af841be16af42b566398b2b61803df84fdfcecf4d5885f7f3734de1f047
|
|
BLAKE2b-256 checksum How to use checksums |
7fcaccaf3d0b71ad6997a12335b53b20c310766f908037e68c0d263705eb1d24
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-voice 0.5alpha
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.