Views Developers

Hi,

Updated: http://drupal.org/project/ReferencedByFilter

the guys in gizra.com (not yet launched) have written a module that filters the content by what is referenced from a specific node reference field (i.e. back link).
I've attached a ZIP of the module, so people go over it, enjoy it and give some feedback.

After enabling the module, there will be added in the Views> Argument> Referenced by a certain field.

An older version of this module included a patch for the views, but this is no longer needed.

Cheers,
Amitai

Since there is no UI, you need to build Views 'by hand'. This is doable. This is a test module I'm using which, I hope, demonstrates how views can be created, saved, loaded, built, executed and rendered.

Because g.d.o has a markdown syntax that totally interferes, the snippet is here: http://www.angrydonuts.com/node/150

I just added a new slideshow mode to the Views Slideshow module. You can see a demo at Drupal Hub. It uses JQuery and views, so any type of view could be made into a slideshow. The current modes are single frame, as seen in the left sidebar of the demo page, and with 'thumbnails' as shown on the content of that page.

I also revamped the themes for it, making it easier to theme specific elements of the slideshow.

Hi. I'd like to document some links to Views2 UI mockups here. Links to the files have been bouncing around in IRC, maybe this can be a place for further thoughts on how Views2 could best present it's functionality to the user. I'll be updating any new screens here.

These all concern the "create new view" part of the UI, looking for ways to present all the available settings in a more compact layout.

first:
- views2-merlinsmockup.png

Now that Drupal 6 is out, getting the project* family of modules ported to D6 is going to become an urgent task. We want to ensure that by the time the final release candidates are out, we're ready to upgrade drupal.org to D6 (which must happen before the official 6.0 release is possible). That's going to take a lot of effort, and hunmonk and I have some very specific plans for how it should all happen. This page will be the place to keep track of what has to get done, in what order, so that anyone who wants to help knows where to put their efforts. It's obviously a work-in-progress, so feel free to help keep it updated, add issue links where appropriate, cross off things that are completed, or add other steps that need to happen.

I'm cross-posting this to a lot of groups since: a) converting project* to use views is a big part of this effort (so we have significantly less code to support in project* and port to newer versions of core), b) since we need lots of volunteers/help, and c) in case anyone is able to help sponsor some of this work to ensure that everything is completed well before the core maintainers would like to ship 6.0. Thanks!

So Drupal 6 has been the first release cycle I've been involved with on any level, did a few reviews and submitted some very small patches, and followed a lot more as they went in or didn't. The overriding feeling I've got from it is that the division in core between api and cms-type modules is causing problems that are increasingly hard to deal with.

Here is a video of how CCK and Views like data management could be done.

http://dabbledb.com/explore/7minutedemo/

They take a different approach starting with the view and live previews. Aside from the slick demo, what are the interesting ideas, what could we

(also posted at http://drupal.org/node/169955, but I realized this is a better place to ask)

Is there an easy way to generate a clean list of taxonomy terms used in the most recently created nodes?

Playing with views, I could create a list of terms used, but not a list with duplicates removed, multiple terms split apart (ie no commas), etc.

I'm thinking along the lines of 'Recent Topics Discussed', so I don't want the cruft of doubles/etc, just a way for someone to see XYZ was discussed, and a single link (via taxonomy) to items using that term.

I just committed a new devel for D5 which adds several tabs when you display a View. You can see the $view object at load time, then again just before it runs its queries, and then again after the queries (i.e. with the matching nodes).

Hi - setting up a large ecommerce site with Views handling the catalog pages (about 12,000 skus). Last item remaining... I need to maintain breadcrumb/menu active state when users click from a view page to a node. Can modify these in the product.module, if I can get the referring view - this is what I'm trying at the moment (in Drupal 5.2):

First Attempt:
<?php
$last_page = substr(referer_uri(), 29); //trimming off the domain, whats left is the views path

if ( preg_match("/store/", $last_page) ) { //match if coming from a view page, they all start with store...

Here is a list of javascript widgets that need to be written for views 2:

<

ol>

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.

Hi Everyone,
I just wanted to let you know about a new views related module, Dynamic Views. (http://drupal.org/project/dynamic_views) It allows you to dynamically update the main content area (no page reload) when you click a node link in a view block. It also allows you to change dynamically update a view using a filter at the top. You can combine it with some elements of the jquery interface library for some pretty cool effects. (see http://warnerbrosrecords.com/artists)

Hi there,

I need some help to update the event_views module to the rewritten version of the event module aka "event 5.2". I am not too familiar with views.

The main change is the change of storage format for dates. All previous versions of event used "seconds since 1970" as storage mode, 5.2 uses actual SQL dates.

Please let met know if you are interested in helping out, I'd hate to release event 5.2 without views support.

Cheers,
Gerhard

This patch to the Formtweaker module, modifies views filters, so they render as checkboxes and radio buttons, instead of select boxes and drop down menus.

Currently there is no way for a user to choose between rendering a filter as checkboxes/radio buttons, or as the default select menus.

How is it done?
How do I add this condition (as a checkbox in the exposed filter section I guess) to the views ui?

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.

Hi.
For the 6.x version of my module linktocontent I plan to use views for the result listings.
Unfortuantely I did not know how to achieve the following listings with views.

HI

I'm about to finish writing a module allows to refine current view results by taxonomy terms, displayed in a separate block. Something like exposed filters does but with links instead of select and number of items after each link. To calculate a number of items that will be returned when user clicks on some term I'm using views_build_view function

I'm also want to handle arguments here and pass it to the code below as third argument.

I love Views and using filters, however what's the ability to filter without having a reset feature to go back to the full data set ... hence this piece of code that you can add to your Theme's template.php file to add a themed "Reset" button capability.

http://drupal.org/node/99370

Many thanks to mshaver for his guidance.

If I'm posting this in the wrong area please let me know and I apologize in advance.

I seem to have come across a problem with using views to grab a random image and post it in a block. The site cn be seen at:
http://mdg.loesje.org/admin/build/block
you'll note the large poster image on the right most collumn which is a block view:

• Fields: Image: Display Image, option; preview
• Filter: Node: Type: 'is one of': 'Image;
• Filter: Taxonomy: Terms for Image Galleries: 'si all of': 'E-Cards'
  and thats about it