Download & Extend

Text field tokens not exposed to pathauto

Project:Pathauto
Version:7.x-1.0-rc2
Component:Tokens
Category:bug report
Priority:normal
Assigned:Unassigned
Status:closed (works as designed)

Issue Summary

It seems that information in a field that is type "text" is not being exposed to pathauto when creating a url. I've got several content types on my site. Those that create a url from other field types (e.g. integer or term reference) are working fine (as are those using [node:title], etc.). It seems that just information relating to a text type isn't pulling through into the url.

Comments

#1

I had a similar problem here and found that embedding text fields worked fine after I changed my "Manage display" format settings for the field to not be <Hidden>. Also if I set the "Manage display" format to be "Trimmed:" I get a trimmed value embedded in the URL. I don't think the value picked up by pathauto should be affected by how I choose to display the field.

Not sure if this explains the original problem as well.

#2

I can confirm this, when I hide fields on the display they don't get used in the path patterns. I don't necessarily want to show all these fields to the public, but I do want them to be used in generating the path aliases.

#3

Status:active» closed (works as designed)

This is the way we could universally support the base-level tokens. You can go to admin/structure/types/manage/YOUR-CONTENT-TYPE/display and enable the 'Token' checkbox in the 'Custom display settings' fieldset to customize how the field tokens are rendered.

#4

Thanks, I don't think I saw this in docs. Makes sense.

#5

Many thanks.

#6

Status:closed (works as designed)» active

It's been over a year since this issue was first posted, so I'm not sure if something has changed. I found the "Tokens" checkbox in custom display settings, but I don't have more options under the Tokens area of Manage Display afterwards, and even after this when I go to change my custom content type URL patterns, I do not see replacement patterns for fields.

Am I doing something incorrectly? I have a List field type (with 6 pre-defined values that a user may select one of) that I would like to use as part of the replacement pattern for a custom content type.

Any help would be appreciated.

#7

Status:active» closed (works as designed)

Whoops, my bad! I just needed to look under Node after I activated the Token display for the content type! Hopefully anyone else that is stuck will learn from my mistake :)