views

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

Last week I started the challenge to upgrade <a href="http://testedgroup.com" target=_blank">my custom zen sub-theme from zen 5.x-0.7 to zen 5.x-1.0 which has taken a couple more hours effort than I had originally expected. The outcome so far however was worth the effort. Thanks JohnAlbin and contributors.

With the excellent documentation, I have decided to start and modify my frontpage from the traditional river of news to display NODE-X that wraps around BLOCK-X displayed on the right hand side of the content. Now I have hit a barrier and I need your input...

From the wiki:

Most of this will be dependent on Views core going into D7 core.

Preface:

I've read a lot of requests for using multiple taxonomy term names as view arguments. I found a code, but it didnt work for me.
Views default argument handling using termid rather then name works beautifully, using forms like: "mydomain.com/viewpage/termid1,termid3,termid2" or "mydomain.com/viewpage/termid1+termid2+termid3", but I found the support for term names lacking.

Concept:

Hi there,

I am stuck on a seemingly no-brainer problem here. Yet I can't find a solution already half a day. In short I cannot get a view to show it's pager inside a Panel.

I have a view, which has the "Use pager" checked and "Items to display" set to 12. I have used the same settings under the Views Panels configuration (http://mysite/admin/panels/views). My "view type" is set to Page.
When the view is displayed alone, it shows its pager and I can browse through the pages if there are more than 12 nodes in the view.

Hi,

Please how is it possible to create 2 views on one page which would sort in the following way : -

1. Enhanced Listing : a Teaser List
2. Basic Listing : a Table View

A fabulous example can be seen at:

http://www.productionhub.com/directory/listings.asp?section_id=7&cat_id=264

I've tried Views Fusion and Views Union to no avail.

So much would love to make this work and immensely appreciate any reply.

Lilian

Here is the situation:

I have a node type called Destination. I have created a view called Destination Pictures, which shows all pictures from a given destination.
Using the following code I have added this view as a new tab under the main Destination node type:

<?php
function dest_pics_menu($may_cache) {

$items = array();

if (arg(0) == 'node' && is_numeric(arg(1))) {
$node = node_load(arg(1));
if ($node->nid && $node->type=="destination") {
$items[]= array(
'path' => 'node/'. arg(1) .'/dest_pics',

I've been wrestling a bit with how to create default views without exposing potentially sensitive data. What are others thinking about this issue?

The Views module includes support for "default" views implemented through a hook, hook_views_default_views(). A quick search through the contributions repository shows close to 60 modules implementing this hook.

Hi Views Developers,

I admit that I joined this group just to post this bounty, but I would really appreciate your help.

I'm trying to create a view that outputs nodes like this - http://www.lawteacher.net/contractlawcases.php

I'm currently building a similar case law library. I've created a Case Law content type and given it a taxonomy with terms like Contract Law, Criminal Law etc.

I'm going to bring up an old discussion now. I don't think there's been much discussion in forums (but if so, maybe someone can dig up some posts). But there has been much over the past couple of years in IRC.

This has to do with integrating RPG with the Drupal node system. The current RPG module is its own entity, entirely unattached to nodes. This is a reversal of earlier versions of the module. Originally, I'd planned to fully integrate it with CCK and Views, and if you look at the first few dozen commits, you'll see that RPG objects were actually node types, and the attributes were fields.

Eventually, I ran into several problems. Some issues were merely difficult, while others seemed nearly insurmountable. Thus, I rewrote the engine, making RPG objects an entirely separate entity in the database.

Now I'm writing graphical support for RPG, and am finding myself duplicating code, and questioning (yet again) my original decision to detach RPG from nodes. Here are some Pro's and Con's of using node types & fields for RPG objects: