Comments on: Overriding a Widget in the Django Admin Site

By: kamran

kamran — Thu, 27 Jan 2011 09:47:47 +0000

Thanks it is very helpful

By: David Peers

David Peers — Sat, 15 May 2010 19:25:32 +0000

This blog helped me somewhat in narrowing down some issues with the latest release, Why do they always seem to leave out vital documentation when they upgrade? It may be trivial to them but not for us! I’m sure i’m not alone.

By: Dwight Hansen

Dwight Hansen — Sat, 06 Mar 2010 19:34:12 +0000

Thanks for this post. I am new at python and this is a big help.

By: Ben Tappin

Ben Tappin — Thu, 05 Nov 2009 10:47:32 +0000

Thank you! Just what I needed.

Unfortunately this overwrites the existing attrs for the widget. I’m sure there’s a workaround but I don’t need it right now :-).

By: podarki

podarki — Sun, 23 Aug 2009 10:09:24 +0000

??????, ?? ??? ??????, ????? ?????? ? ?????? ?????, ??? ??? ????????????.

By: rick

rick — Wed, 10 Jun 2009 00:49:24 +0000

oh thanks :)

By: varikin

varikin — Sun, 07 Jun 2009 17:20:20 +0000

Rick, you mean my very next post, http://www.fictitiousnonsense.com/archives/33?

By: rick

rick — Sat, 06 Jun 2009 02:29:37 +0000

Thanks, varikin.

Like Ed, I’m having the problem of the preview not working.

I found this:

http://expressionengine.com/forums/viewthread/82013/P18/#425444

But I’m having a hard time how to translate that into Django.

I noticed your post says “I have some server side hooks to process the save and preview, but I will get to that in another post.”

So any idea when we might see that second post? :)

By: Ed

Ed — Thu, 04 Jun 2009 01:56:21 +0000

Great tutorial thank you!

I have one problem: the preview window (when I hit the checkmark in the markitup bar) just renders exactly what is written in the input, not parsing it to HTML. Any ideas? I’m using textile instead of markdown, but that shouldn’t matter.

By: Jesús Gómez

Jesús Gómez — Fri, 29 May 2009 15:09:32 +0000

Hello. Very useful. I wanted to point that i had a little issue with this method, and is that i couldn't set the raw_html field as an optional field in the admin, and i had to override formfield_for_dbfield as explained in the post you followed instead of defining the post arg in the PostAdmin. I wold like to rescue the form way so: any idea why this happend?