If I go to the taxonomy page "term1" it shows all the associated nodes based on the time created. So a lot of times, I see blog entry on top, photo entry on the second, forum entry on third and so on. It's a mess right now.
Is there a way to rearrange the content in taxonomy pages so that I at least separate the nodes based on their types and make them look more organized?
I'm trying to create a default view that is available on the Views admin page when the module is enabled using hok_views_default_views() based on this handbook page. Here's the code I'm using:
I have branched off of Panels and incorporated OAT components.
With the current configuration in the zip file 'changes_rolled_oats_version.tar.gz' you create a panel layout and save it, and there is a great deal of on-page interactivity.
Then, you can create a layout page for a piece of content.
If you are not using the rolled oats content, then you will be presented with page containing only blocks and styles to drop onto the layouts.
This can be reached through /admin/build/panels/add. At the top of the page, there is a button, "content selector".
Clicking on this opens an OAT window. There are then two tabs for lists in the window. (Implented with OAT blockbar, and a change I made.)
One list is a list of blocks. The other list is a list of styles. You may drag list entries to a panel. After saving, the list entries wil be available for editing,
by dragging around to different positions, or to the scratch pad, which is trashed on saving. For viewing, the panels should show block content.
If you want to configure a block, then click on the plus sign to the left of the list entry. There is a link that opens a new window to the block configuration pages.
i'm using views & cck (+email_field) to manage a members list (less then 200 members). now i'm looking for a views-way to output a mailto-link within every email address from specific roles - like this:
An organization I am working for uses Plaxo.com for their contacts. Plaxo has open sync and address book api that could be adapted to work with drupal. It is based on REST. I think this would be really cool thing to do and would love to get involved in that, but I do not know enough of PHP or Drupal Module development to do this on my own. Anybody interested ? What is the best way to get started ?