Edit links does not display until after the node is saved.

I completely agree. I will get to work on this as soon as possible.

This feature will be gr8,
Beside this, on clicking edit a reference, Node Page open.
It will be gr8 if the path of editing that node open directly.

I'd find this useful.

Also I think it would be helpful if the create link was removed if an entity/node/user has been entered into the field. This would help prevent confusion on the users' part when using this in an unlimited setting (the fact that you need to click add another item then create in the new row. Also it would be helpful in preventing overwriting values that have already been entered in the field.

I don't know if you want this as a separate feature request as I see them being linked, but others may not.

I've addressed both the original request and the one by ejustice in #5 in another issue:

#1774466: References Dialog UI improvements - contextual create and edit links, hide input option

This uses ajax to replace the create link with an Edit link if the user has update permissions.

It doesn't yet check the widget settings to see if the Edit operation is enabled. This is an essential function but I've run out of time right now. Uploading anyway in case anyone wants to have a go.

Current issues with #7:

- Doesn't check Widget Settings for Edit operation
- Resets when "Add another item" is clicked
- Permission check not correct for all entity types. Only really tested with nodes but should work with entities.

It replaces the Create link so effectively deals with #5.

I'm working on a more robust solution.

Try this one.

Just a note on permission checking: the above uses entity_access() from the Entity API module. This, from my novice understanding of entities, should pass the request on to the appropriate access callback for that entity.

@ejustice #5, see: #1788596: Don't show Create link for fields which have a value

Thanks for the patch. It adds the edit link now, but edit or create aren't opened in a dialog anymore. I guess you introduced a javascript bug.
In my console I see this: "Uncaught TypeError: Cannot read property '2' of null "
Is this error coming from this part?
Drupal.ReferencesDialog.ajaxEdit(key, matches[2], matches[3]);
It's the only new part where you want to get property 2. Now looking why matches is null.

I tried some console.log().
- console.log($('#' + key).val());
Returns the values from the autocomplete entity reference field (eg. "title (34)").
- console.log(matches);
Returns "null".

I guess there's something wrong with the regex in this part:

var matches = $('#' + key).val().match(/^(?:\s*|(.*) )?\[\s*(.*)\s*:\s*(\d+)\s*\]$/);

Hmm...it works on node/edit for me but not node/add.

Won't be able to look at this for a little while but it does need fixing.

Using js is somehow not very stable, I've added an ajax callback to automatically refresh the widget, add link would be removed edit link would display then. I'll add this feature to references dialog after more testing.

http://drupal.org/sandbox/rogical/1880826 References Thumbnail

Pardon me for jumping into this issue, but shouldn't all of the logic managing the links be handled via JS? Collaborating on #1774466: References Dialog UI improvements - contextual create and edit links, hide input option would be the best solution as there are several related problems that should be fixed together.

Here is my js fix. I just change create link to edit link when popup closes.

Updated patch #17 to include base_path.

Thanks, #17 work's for me!

I have been working on a UI tweaks for this. It adds a little extra feature to update the edit link on each reference change.

#17 works for me, #21 doesn't work for me.

However, I would prefer to add this option:
While I found in autocomplete suitable node, so I don't need to use dialog in lightbox, after chosing the option in autocomplete, the link "Edit" could be added next to "+ Create"
So it could be possible to edit chosen option, or create new one.

Just like @igorik, #17 also works for me but #21 doesn't.

I also want to take #22 further, because there's an inconsistent user interface issue that's potentially confusing:

1) I think "Edit" from #17 should say "Edit Content Type" to match "Create Content Type".

2) I also think "Edit" that displays after node is saved should say "Edit Content Type".

3) I also think "Edit" ("Edit Content Type") from #17 should not replace "Create Content Type" but instead be added to it (to the left, just like how it's displayed after node is saved).

4) Per #22, "Edit" ("Edit Content Type") should be added to the left of "Create Content Type" when the Autocomplete option is used instead of "Create Content Type".

5) If I decide to reference another node on 4), update "Edit" ("Edit Content Type"). I believe this is what #21 is trying to do, but I created a separate issue for it because I believe it's a different although related bug that should be taken care of on its own page.