Hello. If there's a way to do this, I'm totally clueless to it, so this is may be a Feature Request rather than a support request.

We have a content type that requires both a Title field and a Feature Title field. This is due to the fact that we have a requirement to have a different title on the News section of the home page than the actual title of the content. This News section is a view with just the Feature Title text field listed and I need those to link to those news items. Text fields do not have the check-box which gives the option to link back to the content so I am forced to try and use "Rewrite Results".

I cannot, for the life of me, figure out how to get the Feature Title text field to link to the content itself. I notice that under Configure field > Rewrite results > Output this field as link you can define a link, but the list of replacement patterns is very slim. When I try to put [path], it renders as %5Bpath%5D.

It says "if you need a field not listed here, rearrange your fields". What the heck does that mean? I've moved this field up and down in the list and it doesn't give me any new replacement options.

Comments

loopy1492’s picture

Issue summary: View changes

Clarified.

loopy1492’s picture

Status: Active » Closed (works as designed)

Oh. You have to add the content path as a field in the view. Got it. At least it's here for posterity.

loopy1492’s picture

Status: Closed (works as designed) » Needs review

double post

loopy1492’s picture

Category: support » feature

Please see my comment here:

http://drupal.org/node/1466274#comment-5710716

This is a really clunky process and should probably be cleaned up.

tim.plunkett’s picture

Version: 7.x-3.3 » 7.x-3.x-dev
Status: Needs review » Active

"Needs review" is for issues with a patch. However, I do think this is a good idea.

dawehner’s picture

Status: Active » Needs review
StatusFileSize
new6.37 KB

Here is a small path with this feature as addition and a test.

Status: Needs review » Needs work

The last submitted patch, 1475230-node-path-no-base.patch, failed testing.

dawehner’s picture

Status: Needs work » Needs review

#5: 1475230-node-path-no-base.patch queued for re-testing.

Status: Needs review » Needs work

The last submitted patch, 1475230-node-path-no-base.patch, failed testing.

tim.plunkett’s picture

Status: Needs work » Needs review
StatusFileSize
new7.71 KB

Adding some debug messages to see what's going on. Locally it passes fine, but I don't have a prefix or anything to mess up the base path.

Status: Needs review » Needs work

The last submitted patch, views-1475230-9.patch, failed testing.

tim.plunkett’s picture

Status: Needs work » Needs review
StatusFileSize
new6.57 KB

Whoops, forgot to pull first.

Status: Needs review » Needs work

The last submitted patch, views-1475230-11.patch, failed testing.

tim.plunkett’s picture

The latest failure shows that clean URLs aren't being used in the test, how do we turn that on?

tim.plunkett’s picture

Issue summary: View changes

clarified