Views 2

Overview

I'm rebuilding the site in Drupal, with the very awesome assistance of himerus (Jake Strawn). There's a very complicated View to build and we could really use some input on how to make this happen. We will be there on Tuesday night for the Boston meet up. I've also cross-posted this to my blog as well, so there may be other comments there: http://www.lisarex.com/2009/10/views-related-node/

There are two content types, Restaurant and Soup (a restaurant can have more than one soup).

Client requirement:
1. The site visitor will click their state/province.

Hi,

With views 2, I've got a request wich select a list of fields from nodes. Among these fields, I've got some node references. It outpour something like this :

• node 1 string field
  node 1 image field
  node 1 node reference field
• node 2 string field
  node 2 image field
  node 2 node reference field

Instead of having a node title link(or just a node title) representing the node reference in the view, could I outpout directly the teaser or the full representation of the node, wich would have bee overrided with a view. In the referenced node view, I could have another node reference with a view diplay, so I would have views in views, in views, in views ...

I would like to see exposed filter block in panels pages using Views2 get fixed for Drupal 6.

I am willing to chip in to make it happen. ($75). If there is a developer who could do this and possibly use chipin to gather more support.

Currently exposed filter block works if
1. no panels
2. no views as tabs in organic group

but I would like to have it work in those two areas

1. as tabs in an organic group
2. with panels

So in essence, they should redirect to the correct page.

1. exposed filter block in a view with path url node/%/foo and it is a tab

Create a view

Hello,
I'll start with the good ol' i'm new to drupal and creating custom modules spiel...
(btw, im using the most current versions of drupal and views)
What i need/have been trying to do is create a filter for a view that uses select dropdowns based on values that are collected from a cck text field.
(for example: a user adds a new node, there is a field called type and the user can enter whatever he wants. when the form is submitted, and he goes back to the list view, his entry in the type field now shows up in a select dropdown along with all of the other options that other users added. now he can filter the view with his own type entry.)

Hej,
Jag bråkar lite med taxonomy och views men har fastnat lite med argumenten.

Jag har aktiverat vyn taxonomy_term, som är en standardvy, för att ersätta taxonomi term-sidor.
Jag har en vokabulär, Märken, som är uppbyggd på detta sätt:

Märken
--Tillverkare 1
------Produkttyp 1
------Produkttyp 2
--Tillverkare 2
------Produkttyp 1

Varje produkttyp har noder kopplade till sig. Tillverkare har inga noder kopplade till sig direkt utan är bara "pappa" till produkttyp.

Hi there... I am flummoxed by a Multi Views Multi Pagers (one view embedded in the other) problem (Views 2, Drupal 6):

I am working on a magazine site. We have Issues, and Issues have Articles. I have created a view that lists Articles based on the related Issue (one at a time, with a pager). I have created another View that lists Issue's Covers (one at a time, with a pager), and used a .tpl file to embed the list_articles view.

Hello everyone. I am the author of the Facebook-style Statuses module, and I have recently completed writing the reorganized 2.x branch (now in CVS/dev). The API should be clearer now and there are a few cool new features. In the next week or so I'm going to add/update two of the three remaining features: Advanced Forum integration and AHAH-driven status submission.

However, the one thing that I don't have any idea how to do is Views 2 integration. I've gone through the documentation and tried working through it before without success. So I would really appreciate it if someone who was knowledgeable in this area could guide me along with my foray into Views--whether that means reviewing integration that I write that doesn't work or actually writing the integration for the module yourself. I consider this an essential feature of the 2.x branch since it means not just integration with Views but also with FriendList and Flag Friend, so I will do it completely by myself at some point if no one steps up to help, but it would save me untold time and pain if someone could offer a little guidance in this area. And of course you'd have my perpetual gratitude.

I just wrote up a sneak peek of Views 2 for the February Drupal Newsletter, which is to be published next week. I'd love some feedback from people in the know before going forward with it. I think the work being done is incredible. The wiki is at http://groups.drupal.org/node/8258 (you have to subscribe to the Drupal Newsletter group to see it).

I've begun work on Views 2.

Due to the fact that all of the systems that Views relies on have undergone massive overhaul, and the API changes I want to do, this had turned out to basically be a ground up rewrite. THis is probably good as it will let me really get rid of some problems that are leftover from how I started this whole thing out, but of course it's going to take some time.

Originally posted at my blog, these are my high level design goals for Views 2.

Views 2 will be the Drupal 6 port. Views 1 will not be ported to Drupal 6; this is so we can make wholesale changes to the API at the same time there are other changes, reducing the number of complex upgrades required.