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.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | views-545738_node_type_display.patch | 1.52 KB | dawehner |
| #3 | views-545738_node_type_display.patch | 1.38 KB | dawehner |
Comments
Comment #1
srobert72 commentedCould it be possible to have choice between human value and machine value ?
Comment #2
merlinofchaos commentedA checkbox or radio button could probably be added to the filter to switch which value is displayed.
Comment #3
dawehnerHere it is
Comment #4
merlinofchaos commented1) 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.
Comment #5
dawehnerupdated patch. Thx for the feedback
Comment #6
dagmarMmm, I think this is redundant, or at least, not recommended by the Drupal API
What do you think about?
Comment #7
dawehnerMh ... The value itself will not be translated..... Is this really wanted?
Comment #8
dagmarWe 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.
Comment #9
dawehnerOk this makes sense.
Comment #10
dawehnerBut it should be @type or @typename.
Comment #11
merlinofchaos commentedThe human readable name for a node type has to go through t() -- there are examples of doing it in core.
Comment #12
dawehnerSo, but should we wrap this within an extra t function?
Comment #13
dawehnerThis is already in views 2.11
Beside a switch for human readable it's a switch to enable machine name.