I'm documenting the install process, to make sure I'm doing everything correctly.

Am using Popups API version 6.x-1.3.

I deleted old popups_reference folder, uploaded popups_reference-6.x-2.0-alpha1 and ran update.php (tho it is not necessary to run update, apparently).

Then I ran the three patches against the new popup_references folder. Since there were no error messages, I assume the patches were applied correctly.

I am only assuming that 6.x-2.0-alpha1 is the correct version of Popups Add Reference to patch, because in the patch threads, 2 of the 3 patches are for that version. The third patch is for the 2.x-dev version.

I go to node edit form for content type that has node reference field (unlimited values, autocomplete widget). I see nothing, realize that this depends on Popups Add Reference being activated for my Node Reference field.

I go into 'manage fields' settings for the content type, click configure for the nodereference field. At the bottom of the configuration screen is a checkbox for adding a Popups Add Reference option.

Save settings for noderference field.

END OF INSTALLATION/CONFIGURATION

ATTEMPT AT USAGE

I go to the edit form for a node with this nodereference field.

I see the nodereference field/list, then for a split second a huge blue field takes over the screen and the page is redirected to white screen, never finishes loading a page, the status bar talks about "waiting for I.sharethis.com". Hit the back shortcut, see node edit form for moment before it redirects again.

I search my sites/ folder for any references to sharethis.com and find that it is part of the custom template for one of the node types available to my nodereference field (via the the View I setup to filter what nodes are available.) It's an in-content javascript tag (a client-side include) used to display creative commons license for site content. Put there by a themer/colleague who worked on the site previously.

<p><script type="text/javascript" src="http://w.sharethis.com/button/sharethis.js#tabs=web%2Cpost%2Cemail&amp;charset=utf-8&amp;style=default&amp;publisher=708fa3ce-b12c-4d3f-a124-aa4fe8846f72"></script></p>

So, without delving into the module's source, it appears that the "inline" actually displays the results from the node type's template? Ironically, Drupal's own Preview doesn't do this (which I had to disable because it was confusing to editors to hit 'Preview' and not see an actual themed view of the content) but Inline Reference seems to 'inline' a fully templated 'View' for each of the referenced nodes in the nodereference field.

So, I guess I need to create some kind of conditional in my node templates to check if the URL has arg(2) as 'edit', then present a dumbed-down view of the node (ie one without a javascript CSI)?

Or is there a better way to bypass having full-page node views appear in the form?

So that I could test the edit feature, I disabled my content templates (by renaming them) and I got the Drupal default node view. I was able to successfully edit the node and save it. Awesome.

One other question ... if I wanted to create a minimal edit form for my node references (say just the headline, body and an image upload field) could I do that via a form_alter hook? Is the form_id of the inlined edit form, different from the 'full-page' nde edit form. If it is, I can use form_alter to eliminate all but the most critical node fields.

I know it's early on this module, but I'm hopeful this can solve my client's request to be able to edit nodes from the referrer node. So far, lots of promise. Thanks for the great work so far!