Node:Type link replacement patterns
srobert72 - August 11, 2009 - 07:50
| Project: | Views |
| Version: | 6.x-2.x-dev |
| Component: | node data |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
| Issue tags: | Node:Type, Replacement patterns |
Description
Hi all,
Thx for your wonderfull job.
For Node:Type I selected "Output this field as a link" and wrote link path as : references/[type]
The problem is that [type] write Node:Type only with human readable name and not machine name.
For example link appears
.../references/Hotel
instead of
.../references/hotel
So my other Views2 page ".../references/" can't use argument Node:Type correctly.
Is there a way to do it as I would want ?
Thx a lot.
#1
Could it be possible to have choice between human value and machine value ?
#2
A checkbox or radio button could probably be added to the filter to switch which value is displayed.
#3
Here it is
#4
1) The description of the field needs a . at the end. Also story and Story should be in quotes.
2) The machine readable name should not be translated, so t() should only be on the human readable version.
#5
updated patch. Thx for the feedback
#6
Mmm, I think this is redundant, or at least, not recommended by the Drupal API
+ return $this->render_link(t(check_plain($value->{$display})), $values);What do you think about?
+ return $this->render_link(t('@display', array('@display' => $value->{$display})), $values);#7
Mh ... The value itself will not be translated..... Is this really wanted?
#8
We don't know if a certain language doesn't need to include something else to content type name.
This string will not be present in the language settings page.
#9
Ok this makes sense.
#10
But it should be @type or @typename.
#11
The human readable name for a node type has to go through t() -- there are examples of doing it in core.
#12
So, but should we wrap this within an extra t function?