CVS messages
CVS (Concurrent Versions System) is a code management system used by developers to collaborate and track modifications of code.
April 11, 2009
- Commit #195530 by Allie Micka at 04:34Bio: /modules/bio/bio.install 1.1.2.7 @ DRUPAL-5
Bio: /modules/bio/bio.module 1.2.2.29 @ DRUPAL-5
Bio: /modules/bio/bio_panels.inc 1.1.2.4 @ DRUPAL-5
Bio: /modules/bio/bio_views.inc 1.1.2.8 @ DRUPAL-5Backporting from HEAD
- Commit #195496 by Allie Micka at 01:32
Adding bio_panels.inc and bio_views.inc from D5 branch
March 19, 2008
-
#236181 by dww: Exposed many fields from the {users} table to views. This only works on views of bio nodes themselves. Currently, the username, email, account status, picture, signature, access time, creation time, and login time are exposed as fields. No arguments, filters, or sorts are defined, but they would be easy to add.
January 30, 2008
-
#190745: Fix error in bio_views.inc
January 25, 2008
-
Bio: /modules/bio/bio.module 1.2.2.20 @ DRUPAL-5
Bio: /modules/bio/bio_panels.inc 1.1.2.3 @ DRUPAL-5
Bio: /modules/bio/bio_views.inc 1.1.2.5 @ DRUPAL-5#214063: Add API function for getting bio node type.
January 23, 2008
-
Bio: /modules/bio/bio_panels.inc 1.1.2.2 @ DRUPAL-5
Bio: /modules/bio/bio_views.inc 1.1.2.4 @ DRUPAL-5#213217: Clean up views and panels integration.
January 15, 2008
-
#183652 by Rob Loach: Fix PHP warning in Views integration.
September 25, 2007
- Commit #82268 by mfredrickson at 20:58
#171551 -- Removing a views filter bio needed now that it is in views.
May 26, 2007
- Commit #68577 by mfredrickson at 00:16Bio: /modules/bio/bio.module 1.2.2.11 @ DRUPAL-5
Bio: /modules/bio/bio_views.inc 1.1.2.1 @ DRUPAL-5
Bio: /modules/bio/README.txt 1.2.6.2 @ DRUPAL-5With the views patches in RTBC state, pre-emptively checking in bio's new views support. See also: #142746 From the recently updated README: The bio module now boasts integration with the views module. This integration takes two forms: 1. Custom filters: Bio has two useful filters, Node: Type is bio and Bio: Author has bio node - Node: Type is bio node -- This is useful for shipping premade views that rely on bio, but are not tied to a particular type of node acting as the bio node (e.g. on one site it might be "Biography" on another "profile"). - Bio: Author has bio node -- This is useful for only returning results where the author has created a bio node. That way, if you are exposing bio fields (e.g. the "interests" taxonomy), you can be sure that a bio node exists for every other node returned in the query. 2. Duplicating existing views tables, fields, filters, and sorts: Bio "steals" the views definitions of every other module and makes them its own. For example, the node module exposes the "Node: Title" field and filters. Bio steals these and creates the "Bio: Node: Title". Using these fields you can create a view that returns a list of blog nodes with the author's bio node title. Don't worry, it sounds complicated at first, but you'll get the hang of it in no time.
