Optional "read more" link to node while using row style fields

yesss! ... and it should also solve the problem of making "readmore" translatable. Using Node:Link with custom text is a problem for i18n sites because t('readmore') does not work here

Or a more generic solution, by replacing the ellipsis with a custom text/token input field?

This seems to be the most generic implementation and conceptual looks fine for me.

Yes, this is a seriously missing feature

Edit: Thought I had an idea of a solution but sods law...

Hi, still very interested in a solution for this please?
greetings, Martijn

I would loooove a solution too...

Here is a small patch which allows to use tokens both for the more link text and the more link path

Nice work! This is a well needed feature. I think it should be possible to use the node: path field as a token, right now all I could get woring was the nid field as a usable token/path.
It would also be nice, if the read more link would reference automaticly to its content, if possible.

Two changes to the patch.

* Add a help description
* Take sure that relative links like /foo/bar works as well. Basically everything which is runned through url().

Now the replacement patterns are shown above it.

Works for me! You should adjust the help message to "above" at the end when the eplacementpatterns are shown above and not below.

+ '#description' => t('The path which is used for the more link. You may enter data from this view as per the "Replacement patterns" above.'),

Just a small update

Looks fine :)

Thanks for all the testing.

Would be definitive a worth feature for 6.x-3.x as well.

What is the replacement token for the node's link path? Such token is not listed in the options.
Without setting it, the 'read more'-URL is set to the root of the website.

You can add a "Node: Path" field, exclude it from display and then use the "[path]" as the path of the "More..." link.

Could someone that knows how extend this patch allow it to accept HTML entities like » in the read more text. I'd do it myself but I'm not quite up to speed enough yet.

Much appreciated
Chris

There is no direct solution, but using 7.x-3.x Views I used ntg's #15 suggestion: add new field "node path", exclude it from display, then set [path] as the path for the "read more" body field.

Having played with this a little more without wanting to disrespect or dismiss the work that has gone into this for D6 (which I'm using) I've come the conclusion that actually the best solution is simply to use a custom markup field.....why? because:

1. First and for most what I really wanted was that the "read more" text became part of the paragraph when its trimmed in the same way the "..." does however that's not the case which means it always appears on a new line and NOT at the end of the trimmed paragraph and on that basis I can already do this with a custom markup field
2. The current patches do not let you include thing like » in your text which a custom markup field does
3. In any case you need to define a field for the path and hide it.

Hope that helps someone but even so thanks to the folks that have put the time into building this and I'm sure it helped you.

C

Using views 7.x-3.3

Confirming that #15 solution works.

Problem: read more links using [title] pattern did not link to the any page. Using [path] pattern (after adding the Content:Path field, and then exclude from display) did the trick. Read more link now links to the content.

Of Course #15 is working. You can use any token as path. If you are using a token wich not leads you to the destination you wish to, it's not working. It would be nice if it would automaticly reference to the content, but this is an other issue. Right now it's working perfectly well and it's ready to be ported.

#15 doesn't work if one happens to be working in a language that has special characters that [path] messes up for some reason and the path alias is broken. I use [nid] instead, linked to original content and rewritten to be "read more…" or what ever is needed. Quite complicated and not very intuitive for the purpose.

The Drupal 6 branch is no longer supported, please check with the D6LTS project if you need further support. For more information as to why this issue was closed, please see issue #3030347: Plan to clean process issue queue