Strategy for learning to use Views in modules
I started learning views with the tutorials and the great api docs. I decided to follow the strategy suggested in a post that suggests using the user interface to create and then export the views structure. My problem is that I want to create a table view including data from one of my added tables.
These data do not show up in the list of fields to add. That makes sense since there is no place to add my table into the graphical UI. So I tried this strategy:
-
Create a base view with only node fields (nid, title).
-
Export this view.
Creating a Filter for a derived value
Ok,
First off, sorry if this is the wrong place to post this question. But this is the one time so far that i have really struggled with Drupal and Im seeking help.
I am struggling with how to develop a views intergration with my Content Recommendation Engine [http://groups.drupal.org]. And the simple reason is that my table holds really no new information. It holds content_id's of two different content type and the sum and count of all votes made on this. (ACK! i know makes little sense....)
My scoring is done by taking this data and derving the score. Here is the db query for top function
Read moreForm structure from Views?
We've talked about future CCK tie-ins to the form builder, and are keeping this in mind as a future add-on.
What about Views?
Views module provides a code-accessible representation of tables, fields, etc. Presumably, on this basis we could pre-populate a draft form array, or provide a data reference for the form builder (default values for fields, etc.).
Read more- « first
- ‹ previous
- 1
- 2
- 3
