#django

i dunno though, this is just general troubleshooting the problem, i may be way off base, i dont use bower for anything, but, I would try looking there, as the whitenoise site doesn’t seem to have a lot in respects to fixing something like this

so, question for you from earlier

avri: what do you mean by this: it works with django's staticfile app when DEBUG is set

does whitenoise work fine with debug set to true, but, not when its set to false?

or, were you just saying that your staticfile app works

If i unset DEBUG, django's staticfiles won't be served - I need to handle them myself using a web-server

WhiteNoise is supposed to do that

everything works fine with django's staticfiles app, during DEBUG.

it uses django-compressor and calls sassc to compile the .scss files in runtime

joshbright: m( I had the login route in 2 different paths and I worked at the wrong one …

sash_: so did you get it working then?

yes :D

Just subclass the form, change the error messages, done

avri: yeah, i’m not too sure what could be the issue =(

sash_: ah yeah that sounds about right, glad to hear its working!

thanks anyway :)

so I got it to work when commenting out COMPRESS_STORAGE

I had it set to be equal to STATICFILES_STORAGE

which was set to 'whitenoise.storage.CompressedManifestStaticFilesStorage'

for some reason it does not like that :/

hey

traceback: http://dpaste.com/29ZKB6E

throughouts: did you run makemigrations/migrate?

yes

but didn’t work had some errors

then give us those errors

they are the same as shown in traceback

admin.py https://dpaste.de/pPYb

models.py : https://dpaste.de/nJhY

please share the traceback for makemigrations/migrate anyway

for makemigrations don’t have any errors

that's an entirely different traceback...

ya i just forgot that i had template error on index

index = main page

did you at some point add unique=True to the slug field and run makemigrations?

ya

this happend to me 3 times i added unique and problem started

that likely means you have multiple questions with the same slug, and the migration fails to add the unique constraint

if you run `manage.py dbshell`, and in that shell run `.tables`, what do you see?

can you show the polls/migrations/0004_question_slug.py file?

i deleted questions and worked

yeah that should work

but now i have this problem : http://dpaste.com/3628BZ7

next time, if you don't want to lose data, you should follow these steps to add a unique field: https://docs.djangoproject.com/en/2.0/howto/wri...

why there is this key error : http://dpaste.com/1SSYGQ3

files : https://dpaste.de/nrWr

does the form have a field called slugurl?

no, it doesn't, because you didn't put it in the fieldset

okay

and it needs to check it because: prepopulated_fields = {"slugurl": ("question_text",)}

prepopulated fields happens in the browser

hmm there was a problem

is it very bad to do this kind of mistake or they are comman

which one?

like forgot to add slug in fliedsets

for people who rely in admin a lot, probably

is there a better way !

invest less time/effort in admin...

spend more time on writing your app

/buffer #ansible

is there a way to do like “ this was first question “ then user changed it to “ this is second question “

this is what admin panel shows http://prntscr.com/i7eg6e