This may be related to http://drupal.org/node/1475230 but I'm not sure - my use case is simpler.
It looks like both "Link to node" and "read more" from a trimmed post seem to both be broken in 3.3 - I've used this many times in D6.
Adding a "read more" link if output is trimmed and not entering anything in the destination field results in an output of "/". And Using "Link to node" and suppressing display to provide the [view_node] token (which I then put into the link destination for "read more") results in an output of /view, not the node.
I've tried everything I can think of and perhaps I'm missing something. But the behavior certainly seems to be different. Pretty important feature - any ideas here? Thanks much!
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | Screen Shot 2012-05-09 at 5.10.00 PM.png | 10.2 KB | callen87123 |
| #2 | press_releases_view.txt | 42.23 KB | bcobin |
| #1 | example.view_.txt | 3.08 KB | dawehner |
Comments
Comment #1
dawehnerCould you please export of your view? Maybe it's configured wrong.
You know views maintainers suck at using views in a way which is broken. Here is a view which works fine for me.
Comment #2
bcobin commentedThanks for asking! Attaching the view as requested.
Just checked it again and the problem is bizarre, but should be very simple to check. In the Home Page Block subview, I just want to add a "read more" link, which is an option in the Content: Summary field. (I have a link field - the first field - that's excluded from display as part of my trying to work around the problem. Ignore it.)
If the "read more" option is checked, the output for all items is /view, as described, instead of a link to the node. This is definitely wrong and should be simple to check. In this case, I'm just ditching the "read more" functionality, but I don't want to.
Thanks again for asking about this... I don't know what it could be other than a bug, unless it has something to do with the OpenPublic distro.
I remain hopeful!
Comment #3
esmerel commentedComment #4
bcobin commentedSee similar (or really the exact the same issue) here: http://drupal.org/node/1155236
I'd say this qualifies as a major problem insofar as if you don't want to use the title to link to the node (and in my case, I don't), there's no "proper" way to link to the content. Yikes!
Update: Actually, I spoke too soon - sort of. Using
node/[nid]as the replacement pattern works OK. The system translates the path properly, meaning it's an acceptable workaround for the bug. Link to content should still be fixed, though...Comment #5
dawehnerGive people a feature and they will ask for more ... :)
You know there is a proper way to configure a link. What you call workaround is from my perspective the official and suggested way to do it. I'm not really sure why a link should work automatically as an url.
Comment #6
bcobin commentedThanks for the response - I would never want to seem ungrateful! But the "provide a simple link to the node" definitely doesn't work as advertised and doesn't behave the same as it did in D6, at the very least. I've now gotten my head completely 'round D7 and can't imagine going back, but this was one of the "gotcha" issues I ran into while I was making the transition.
The good news is that this basic functionality can be done; I honestly don't see how the "provide a simple link" could be of any use as it now stands. At least this is now memorialized and will hopefully be of some help to others who run into the same issue.
Thanks for all the work you're doing - I can now go merrily linking away! ;-)
Comment #7
callen87123 commentedI have this exact same problem and have used the "read more" simple link function thousands of times before.
Spent past two weeks bamboozled!?!?!
At first I thought it was the token module and updated that to latest dev version to no avail.
Then started thinking that maybe it's the views and/or link.
I did do the workaround and "rewriting the output of content:nid to "read more" and displaying that field inline as shown here.
This workaround works for the moment but definitely need the old "read more" rewrite functionality like it used to be.
Comment #8
bredi commenteduh. yeah. I have been stumped on this too. didn't it used to be [node]? now I"m getting confused.
I tried [path] and it works on some views but not others. tried [nid] but doesn't work. Like others have said, link to content should be a simple check box. without even having to "rewrite" outputs. if rewrite fields/outputs is the way, then token replacements need to be supplied. This is such a simple need.
"Link this field to the original piece of content"
"Enable to override this field's links."
This verbiage is misleading also. If I want to "Link this field to the original piece of content". then yes. link it to the original content.
But this enables the rewrites. so you think you are done. but your not. because the rewrites are blank. by default it should populate the [node], [path], [nid] or what ever is the proper way.
It is embarrassing to not be able to link to something without searching and trying workarounds.
is this a bug? if so, its been this way in D7 for a while. is it views 3? Path Auto?
if not. what is the correct way to link to a node? OMG, Am I really asking this?
In my case its simply the title field to its node. Really. yes. I'm embarrassed to post such a question.
thanks!
Comment #9
rennevat commentedYou can also add "Content:path" as a field, exclude it from display, then use [path] as the "More link path" to get the aliased path to the content.
Comment #11
one_orange_cat commentedUsing Content:Path works nicely for this, but just a note in case anyone else falls over the same quirk I did - you've got to be sure to tick 'Use absolute link (begins with "http://")' under Rewrite Results for Content: Path, otherwise it will not render the path correctly when you then tick "Output this field as a link" and enter [path] as the Link Path in your chosen field.