Here's what I'm trying to do.
I'm using organic group's default view that shows unread messages in a user's groups. I want to create a link from the node-type column on that view to pages that list the most recent nodes of that content type. So a poll would link to a page listing all the most recent polls etc.
The problem I'm having is that the replacement pattern for the node:type outputs the human readable name for the node not the machine readable name. So my view for showing recent posts by type uses a node:type argument expecting the machine readable name and doesn't work with the human readable names.
Is this a bug? Or I'm I configuring something wrong? I'd like it so that the replacement pattern should be able to output both the machine readable name and human readable name for any given content type.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 528898-node_type-more-fieldset.patch | 555 bytes | dawehner |
| #6 | content type machine name.patch | 554 bytes | michaelfavia |
Comments
Comment #1
mandclu commentedI'm running into the same thing. There definitely should be a way to get the machine readable version.
Comment #2
mandclu commentedFor my purposes, I'd be happy if there was just a token I could use in the output rewrite field. Something like [type-raw] though I have no idea where I would go to create that. If someone could even suggest where to add code to support that, I'd be happy to attempt it myself, post the result here.
Comment #3
esmerel commentedThis issue is a year old, it's likely either resolved or no longer relevant.
Comment #4
michaelfavia commentedUnfortunately it is. Working on this.
Comment #5
michaelfavia commentedWow this IS possible now but i had to find it int he content type handler to find it in the field UI. :)
It is under MORE once you add the field to the view.
Comment #6
michaelfavia commented@UX people: Can i get a witness?
Attached patch moves it out of the MORE box into the main area like the other fields. It was undiscoverable in the MORE fieldset and is the only option for this field.
Comment #7
michaelfavia commentedForgot to update status sorry for the bugspam.
Comment #9
dawehnerJust uploading a test which can be applied by the testbot
Comment #10
tim.plunkettLast time I needed this checkbox, I had to find it by grepping the codebase.
I'm going to be bold and say this needs no formal usability review.
Comment #11
dawehnerAs this is a major part of the functionality of that specific handler, it totally makes sense to move them out.