Field: Path to node

I think this would have to be a prerender_list handler

I had the same need in a project I'm working on. Attached is a patch to add Node:Path as a display field. I didn't need filters or sort functionality so I didn't add those.

I would be good to include a relative/absolute option -- I'll see if I have time to add that later. In the meantime, any help testing would be appreciated.

Mh this executes the function quite often. You could perhaps use pre_render method to load all path aliases at once.

dereine, I'm not sure I understand. render() is called once per node:path field per record. Using pre_render to load all path aliases at once will make the same number of calls to drupal_get_path_alias. Wouldn't adding a pre_render() method add an additional function call to the total? Or is there some way to use pre_render to replace render()?

Thanks.

Why not just use the "Node: Link" field?

Node:Link gives you the whole <a> tag with no ability to edit it (eg: add a title attribute). The use case I ran into was creating having the Node:Title link to the node with a custom field in the in the title attribute.

Then you might want to consider a patch to "Node: link" that makes that possible, it seems to make more sense than another field type.

I considered that. I thought Node:Path would be more flexible in terms of using the "Rewrite the output of this field" in other fields. Perhaps not, though.

Also, to do this in Node:Link, I'd have to add the alt text field plus enable both that and the "Text to display" field for replacement patterns. And, to put it bluntly, I've got no idea how to do that...

I can look into it if you feel strongly that this belongs in Node:Link or that adding another node field creates additional confusion.

I am interested in this functionality too.

Wouldn't it be possible to write a drupal_lookup_path_multiple?

The more i think about it, i'm ok with this patch. Even for normal links to nodes, this function will be stored and cached internally

Maybe it could be better to use url() instead or concatenating base_path() directly.

I think ao2 is right. Besides it also makes it really easy to add an absolute/relative option, which I did with the attached patch.

The patch above works beautifully, kudos and thanks.

I'm using it with Views Gallery to link the image in the gallery teaser to the gallery node itself.

For me absolute should be configurable. There are use cases for both.

For me absolute should be configurable. There are use cases for both.

Agreed. The patch in #13 adds a checkbox for absolute paths.

Yeah the patch looks fine.

Works perfectly, I hope this gets added soon so when I update I wont have to patch again.

Ok, this is +1.

However, the new handler seems to be missing an option_definition() to define the new 'absolute' setting, which will break in 3.x. This is necessary.

Update, but still needs work.

Non-Absolute urls should be "node/123" instead of "/node/123".b

Ok. Its fine. You can use absolute then. Added a description to document this

COmmitted to both branches of 6.x; doesn't apply to 7.x but this is probably an easy fix.

And commited.