Javascript errors with prepopulated_fields in admin

[ElliottM]

When I set the prepopulated_fields property in my ModelAdmin, I get the following Javascript error (as reported by firebug):

None is not defined
onkeyup() (line 149)
if (!e._changed) { e.value = URL...ntById("id_description").value, None); }
http://127.0.0.1/admin/network/path/add/

My model:

class Path(models.Model):
	circuit_id=	models.CharField(max_length=16, db_index=True, unique=True)
	
	description=models.CharField(max_length=64)
	comments=	models.TextField(blank=True)
	speed=		models.CharField(max_length=8, blank=True)
	
	in_use=		models.BooleanField(db_index=True)

The ModelAdmin for that model:

class PathAdmin(admin.ModelAdmin):
	list_display=('circuit_id','description','comments','speed','in_use')
	list_filter=('in_use',)
	search_fields=('circuit_id',)
	prepopulated_fields= {'comments':('description',)}

The error results in the comments field not being prepopulated.
This happens both on my Mac 10.5 running Firefox 2.0.0.11 and my Kubuntu Hardy computer running Firefox 3.0

[Brian Rosner]

I am beginning to wonder why you are using a TextField for the field to prepopulate. What is the behavior you want with that? It appears the Javascript is working right the textarea element. I also wonder if this something that should be allowed or not. I tend to lean to preventing the behavior in validation of the ModelAdmin.

[Brian Rosner]

Correction, not working right with the textarea element ;)

[ElliottM]

I was just trying it out with a pre-existing model to see how it worked. I didn't even intend to use it like that, just wanted to see it in action.

[Matthias Kestenholz]

It probably does not make much sense to support this, but here is a patch which just uses the default SlugField length.

[Malcolm Tredinnick]

This isn't ready for checkin yet, since the patch no longer applies. There's been some refactoring in that template since the patch was created and the relevant code has been moved elsewhere. The idea's good and it can go in, but can somebody regenerate the patch against the new home of that fragment of code (and then bump it back to "ready for checkin")?

[Malcolm Tredinnick]

(In [8505]) Fixed #7903 -- Allow admin's prepopulated_from to work with TextFields. Patch
from mk and Alex Gaynor.

[Jacob]

Milestone 1.0 deleted