Views Developers

I know that I will most likely be wrong about this, but with the advancement of CCK, Views, OG and Panels, is the forum module really necessary anymore? My idea being is that with all these "practically core" modules, isn't it feasible to create a forum with just these modules?

I can create a content type called "forum post" manually, set the taxonomy for the forums (granted containers would be an issue) and use views to custom tailor the data shown to the users. I can already create 8/10th's of the forum functionality with just that scenario. Unless I am missing something.

Hi,
How can I set up a view with one (latest) blog entry per user, sorted by node submission type. Can't seem to figure out how to set up the whole "one node per user" thing...
Thanks!

Any chance of rolling a new release for Drupal 5? I know everyone's excited about Views 2, but the last release (1.6) was last July, and I've run into some bugs that do have patches sitting out there... I've got a client that's uncomfortable going into production with Views 1.6 + CVS + uncommitted patches...

Thanks.

I am working on "fields in core" this week and recently found myself pondering the problem of very inefficient CCK-related Views queries. Here's a brief summary of the situation:

I'm building a link directory. Links are location based. I want to to create link listing grouped by Country and Cities. I'm not able to find out how I can do this.
Pls help me.

Hi,

I have tested views 2 version with drupal 6. What feature I like is new interface and type of views like views for nodes or comment or user. Now I have a question in my mind how I can create comment views in views 1.6.

Sharique

This is a quick list of help pages I've identified and their current state.

So, it may be premature to ask this and this may not be the right place, but here is some sql generated from a view I built using the latest dev build of views 2 (as of Friday). Two questions ...

1) shouldn't the joins use term_node's vid instead of nid (More Info)
2) shouldn't the joins on term_node use INNER JOIN instead of LEFT JOIN

Thought it'd be a good idea to start a discussion specificially on how this might work.

This is a very rough outline from my first post on this subject Drupal.org the redesign - high level.

Hi,

I'm not sure if this is the right place to propose an idea for modifying/improving the views module (or, to be more specific, the views_rss module). If not, feel free to delete this post and please accept my apologies.

I did a little experiment recently to see how we could get e-Commerce Transactions into views in D5. The reason I did this was because I'd like to de-couple store crud routines from store admin ui code so that someone could write an alternative admin interface for ecommerce. The current admin interface is clumsy and always begging to be hacked.

For those not familiar with ecommerce, transactions are represented by a few tables, I was just interested in the main one ec_transaction for this experiment.

(Note: yes, usernode does something like this for users.)

This wiki page summarizes the remaining Views 2 development tasks. This is a wiki so that interested developers can help implement some of these features. I can provide help implementing this stuff on IRC; find me in #drupal-views. (Note: Not a support channel. Development. I will quickly ban inappropriate support requesters).

People are reporting that they get a whitescreen when editing the wiki. I have therefore opened up comments to let people claim/unclaim tasks by adding a comment.

First off, if this has already been discussed/decided or if, as a non-views-developer, just a web-dev using drupal, I'm not allowed to post here, please say so and I'll move along never to return to this group.

Right, onto something which in the current drupal5 views module, I've found a little frustrating.
It's related to the Header, Empty text and Footer text input areas.

I have to lock down the Views area to knowledgeable site admin's only, as users I define as editors have a nasty habit of breaking my carefully constructed views logic.

It looks like there's going to be an explosion in the number of people doing Drop tasks soon (see http://lists.drupal.org/archives/development/2008-03/msg00105.html for more), so it'd be good to get some Views 2 ones up.

Hi There
I have been trying to filter view with the cck date field, and can't make it to work , i am missing something...

I have an defined event content type with a start date & end date
I have created an events view that i wish to filter as a start date with the logic :

1. if no argument has been sent to the view than start_date >= now
2. if a date parameter has been sent then start_date >= arg[0]

if have 3 filters , first 2 are published and term id , and another filter "start_date" "greater or equal to" and set the value to "now"

in the arguments i have set the code

I have gone through and deleted a bunch of support requests. I realized that the front page of this group was almost entirely support requests and that was giving the wrong impression of the group, and simply inviting more.

This is a working group; it's a group for people who are working on Views or on Views-based modules. It's absolutely not a place to ask how to do some random task with Views on your site. Those posts are distracting.

Six months ago, Dries linked to this DabbleDB demo from his blog. He hailed it as a vision for what CCK and Views could ultimately be. The demo is positively breathtaking in the flexibility of fields to morph and change. Further, the usability of the UI is outstanding. Everyone in these group really ought to watch the demo, and discuss what small changes we can make to get closer to this.

Some starting points:

• Can we design a flow whereby node_import module could suggest and then create the needed CCK fields to hold the incoming data?
• Can we add a metric ton of flexibility to CCK whereby we can take a field and move it into a new content type (i.e. the demo moves Person into a 1st class object) and move fields (and data) between content types (in the demo, the Company field moves over the new Person 'content type').
• Could we get a View created automatically for each content type that has the right exposed filters automatically? And then a UI which progressively shows those exposed filters in the 'query by example' method in the demo?
• The demo has a notion of saving ad hoc queries. Our equivalent is Views Saved Searches. Should this be a core feature of Views, or otherwise better integrated?

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).

Natural sorting, also known as natural order, is about putting the string "Chapter 10" after the string "Chapter 2".

Or about putting "I like it with 3.5 spoons of sugar" after "she'll have 2 spoons".

We humans prefer it this way.

I just added an Attendees tab to all event nodes on this groups.drupal.org site. This lists all users who have signed up for an event. Signup happens by clicking on a one of the node links that reads 'i am not attending'. I'd love someone to create two graphics which will sit at the bottom of event node views which encourage users to attend or unattend an event. The current link is a little too subtle.