When using autocomplete field, object created with "Add Another" is not editable.

[juliecampbell]

I have two models, ProductSpecs and Product. Product has a foreign key relationship to ProductSpecs, and on the admin page for Product, ProductSpecs is the field using autocomplete.

Here are the actions I take in the admin backend:

1. Create a new Product. (This is not reproducible when editing an existing Product.)
2. Click "Add Another" for ProductSpecs. The popup for ProductSpecs appears as expected.
3. Fill out the fields for ProductSpecs. Click save in the popup. The popup closes as expected and the ProductSpecs field is filled out with the correct ProductSpecs object.

If after this point I click save on the Product, everything is created and works as expected.

The problem is if I have not yet clicked save on the new product, but instead click to edit the newly created ProductSpecs object, the popup contains a 404. The error message given in my local environment is "Product Specs object with primary key u'null' does not exist.". This is also reproducible with a different foreign key relationship elsewhere in my project (which is the only other place I am using autocomplete fields).

If I let the ProductSpecs field on the Products admin page be the default Django foreign key select dropdown, this error does not happen.

As this is the first time I have used this plugin, it is entirely possible that I haven't set something up right. I have not dug deeply into the plugin functionality yet and have only used the basic install and tutorial information. Does it sound like I am missing something, or does this sound like a bug?

[jpic]

I think this is fixed by #499, could you try ?

Thanks !

[jpic]

Fixed in master.

[juliecampbell]

I see what you did there. You made it so that the newly created foreign key object is not editable at all until you save everything for the first time. It does prevent the user from seeing the 404, but also is different from how base Django works. It would be nice if the foreign key object was editable once it was not empty (I stumbled on this issue by clicking too quickly and wanting to double-check what I had just done), but if it's not possible...

[jpic]

Well there's a fix for the bug that was released, but it could be improved.

A PR would be nice here: https://github.com/yourlabs/jquery-autocomplete-light/blob/master/src/django_admin.js

Too bad Django doesn't listen on the select widget change events but I assume that's for compatibility with other kinds of (weird?) user-defined widgets.