I'm hoping to receive some help from the community with this RedHen site I'm putting together. If there is a better place or forum for general discussion please let me know.
Currently the client I am building this for does not like the layout of the RedHen Organizations and Contacts page. Since I am using Views for the other content pages on the site I decided to put together a view for the Orgs and Contacts. I just realized however that I cannot link any of the redhen fields in the view back to their original piece of content. So I added Org ID to the view and ended up using a rewrite for the Org Name field to output as a link to redhen/org/[org_id]
Is there a better way that I can be designing these pages and blocks though? I feel like I am already on the path to making something wonky and would rather figure out how to do it right. Any help would be greatly appreciated. Thanks!
Matt
Comments
That is how I do it.
that is what I do. Curious to see if there a better way.
That's correct
Most of the Views display handlers for RedHen are either provided "for free" by the module suite's reliance on Entity API, or they have been contributed by other developers as patches. Making sure that the module has Views support was really important to our development team. However, we generally write EntityFieldQueries to manage these listings, as they rely less on Features exports.
If you'd like to summit a patch for this, that would rock! It'd be really helpful to the rest of the community. We'll do our best to prioritize this request as well.
May have to do with "Relation" module
If you are using the relation & redhen_relation modules to build the connections between Contacts and Orgs (which is the recommended methodology), you might want to look specifically at the relation/views issues. We built redhen_relation on top of relation for good reason: relation is a popular and mature module!
This looks like a good starting point: https://www.drupal.org/node/1276380