Usability: Creating a release of a project, default to current project

[mig5]

After navigating to a project and then clicking to add a new release (on path node/add/fserver-release), it would be neat if the field_fserver_project field defaulted to the current project (i.e the project one was on when clicking "add new release" and the one defined by the URL ).

A couple of times I didn't check this field and took a moment to realise why my release had been applied to a different project: namely, the alpabetically-first project on my feature server, because it was the default choice in the combobox field.

I don't really know if this is possible to change with CCK (weighting a field based on some argument / condition such as what referer or something) - it'd just be a neat usability thing to know the Release you're making is by default going to apply to the project you were viewing when you clicked 'Add new release'.

Cheers :)

[yhahn]

y, agreed. we can add a loose dependency on http://drupal.org/project/prepopulate

[mig5]

I found an elegant solution from a suggestion by dmitrig to use 'nodereference_url'. Set the widget type for the Project nodereference field on Release node type, to be Reference from url.

Now, we don't currently reference the project's node in the URL when clicking on 'Add new release' on a project. So the nodereference_url wasn't picking up anything to automatically set that field. I modified fserver_link to add the node's nid with $object->nid likeso:

'href' => 'node/add/fserver-release/'. $object->nid,

Of course I guess this won't solve when someone goes to 'Create content > Release', only from a Project page.. but if they are going the long way about it already, they're already committed to manually choosing the Project (and I set, in the nodereference_url widget options, to automatically fallback to using the Select widget if no match is found).

Lemme know if you want a patch to test it out, but it's a pretty trivial change.

[mig5]

Actually, as dmitrig has just shown me, one can create the 'Add new release' link directly in the nodereference_url widget on Release, which puts the link on the Project node. This means you could remove fserver_link() altogether in the module.

[mig5]

Attached is a patch worked on by dmitrig and myself that introduces nodereference_url support as above, including making the widget set a field 'Add new release' to the project nodes, so that the url reflects the nid and thus the Project widget field, when adding a new Release, is an uneditable set Project field.

I also remove fserver_link() to remove the existing 'Add new release' link.

http://pastie.textmate.org/private/ywzc2lybmhrbbwlwn8cfbq

[JoshOldenburg]

See my pull request at #8. I added this.