#django

04:44 < FunkyBob> unless you're trying for a ManyTomany relation

04:45 < mribeirodantas> yes, I am.

funkybob runs a tight ship

Hi everyone

could someone point me to a good richtexteditor for django that is updated and well documented?

I tried django-cfkeditor, django-redactor and django-tinymce and I have many problems to use them

hey all, im having my urls capture and pass the wrong parameter to my view...heres my code https://dpaste.de/N6Tz

any ideas what is wrong?

deltaskelta: well, the one on line 3 starts with a$... so it can't possibly work

$ means "end of string"

line 7 has no $, so will match anything after its match ,too

it should start with a ^, too

can you suggest me a good wysiwyg editor for the textfield?

nope... they're all crappy IME

redactor looked ok... but never erally tried it

FunkyBob: I tried redactor and works in the admin, but in my view I got some weird js errors and the doc doesn’t explain anything

FunkyBob, my apologies, I typed that out without double checking, it is right in my real code, let me paste in the real stuff in a minute

deltaskelta: good idea

keyengi: yeah, well.. would need details about "some weird JS errors" and exactly what you did...

yes FunkyBob let me switch branch and I’ll be back with detailed errors

FunkyBob, here is the actual code... https://dpaste.de/YDkM

FunkyBob, I solved it. I am changing my urls structure slightly and another url in my old structure was matching that ;)

FunkyBob: installed redactor and works in the admin. In my view I got a ReferenceError: jQuery is not defined because I load the jquery at the bottom

well, then...

seems obvious, eh?

yes, let me move the jquery at the top

or fire off the thing that needs it after jquery is loaded

if I load the jQuery at the top

I get the error on this line: jQuery("#id_description").redactor(jQuery.extend({}, …

the error is jQuery(...).redactor is not a function

and... that line is...?

is the javascript in the input field that refactor provide in the widget if you use RefactorField in the model

so this is the code generated by the widget

I'm not sure how you expect anyone to debug this when you provide almost no details

what I don’t understand is why in the admin works, but not in my page. I know that admin use the {{ form.media }}

yes, you’re right FunkyBob

try to imagine for a second the near infinite number of ways your page could be written... and you're expecting us to guess?

yes FunkyBob I’ll try to figure out few things before boring you, then I’ll provide more details

just dpaste the template, for a start

so we can _see_ how you have things arranged

it's not boring... it's frustrating... trying to help someone who gives no details

hi

hello!

With wsgi aside from HTTP_HOST I wonder what other headers are non standard?

request headers sorry.

I'm not sure why the wsgi spec didn't include a seperate dict for request headers, instead of lumping them all in the one dict :/

why is Debug = True not working anymore?

audioburn: define "not working".

no errors are being displayed

audioburn: So what is displayed instead?

Server Error 500

jtiai ^

audioburn: Either you're modifying incorrect settings file or you may override that setting in your setting file(s).

perhaps your IP is not in the whitelist?

ALLOWED_HOSTS = ['127.0.0.1']

yes it is

jtiai, both of those are untrue

I vaguely remember once having to add 'localhost' to ALLOWED_HOSTS because for some reason 127.0.0.1 wasn'

wasn't enough

I'm not sure why upload_to for ImageField is changing the name of my file: http://stackoverflow.com/questions/28205560/upl...

(but maybe I got confused and misunderstood or am now misremembering)

mgedmin: That is required when DEBUG is False...

mgedmin, I have another ALLOWED_HOSTS further down actually, set to *

audioburn: When this server error 500 happens? When running with django dev server?

anyway, the whitelist I had in mind is INTERNAL_IPS, not ALLOWED_HOSTS

jtiai, both dev and production

jtiai, but I'm worried about dev right now

so i can fix production

both are acting like debug is still set to False

mgedmin, oh

oh wait, that's for the django debug toolbar

I'm not sure if regular error pages need this

audioburn: well that's easy to test. in top url config put print settings.DEBUG

alright

audioburn: Also cleaning up .pyc files sometimes helps if you for some reason have stale .pyc file(s) hanging around.