Posted by scottrigby on July 1, 2009 at 8:24pm
Jump to:
| Project: | link node |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
This would be killer
| Project: | link node |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
This would be killer
Comments
#1
So, how would this work ? Given there may be a lot of nodes on a site, and they may or many not all be in categories... maybe some sort of autocomplete text box for the title ? Or a search box ?
#2
@Tom: good question. Personally I'd be happy with an autocomplete that recognizes node titles and/or nids - maybe with select options like "My node title [nid:1]" (then the autocomplete could list options that contain anything the user types, including the nid).
But that's just me. It may be more widely useful if this were configurable to include only certain node-types - similar to how nodereference displays checkboxes for each content type that should be selectable. Nodereference optionally allows a View to determine the list of selectable nodes, which could be a nice model for Link node too? However, unlike the Nodereference fields, Link node would be providing a single button to the Wysiwyg API (multiple configurable buttons might be way outside the scope of this feature request?).
I don't want to over-complicate the idea, but here's an issue that might be worth looking at for current discussion about how the WYSIWYG buttons could work with the BUEditor #429684: Add editor: BUEditor. The Linodef module also integrates with BUEditor - making a great combo. The issue with Linodef buttons is that - while awesome - what i've experienced so far is they insert html
<a>links to the node. The great thing about Link Node is the that the [node:NNN] tags keep the node's path alias - just as it would if we used l() - and even better, keeps the node's current title.So... i'm of two minds. On one hand, it would be great to add a Link Node button to the Wysiwyg API (similar to how img_assist does this) with some basic functionality (configurable list of nodes, similar to how noderefence fields allow the field to be limited by content type(s) or by a view) --- On the other hand, it might be worth thinking about integrating with BUEditor (and potentially other editors) using Lindef's Buttons API. Maybe the first one could be a good lead-in to the 2nd? Or is this all crazy wishful thinking?
#3
any interest in this still? I'll be writing this mini module at some point in the near future to grab a list of nodes just in the current context provided by Spaces / OG
#4
I'd go with the former option. I use the G2 plugin to embed images from my Gallery install, for instance, and it seems the easiest approach. But then I'm not writing it :-)
#5
if I was using images that would work well but I need to allow people to potentially reference other material in their outline in the page they are currently creating. Right now they have to understand creating a direct path as well as how to get the node nid incase the link would change.
#6
Found this project which does a very similar thing with the CKEditor / Wysiwyg module
http://drupal.org/project/ckeditor_link
#7
@btopro - nice :)