Releases for Views

Bugs fixed

• #419226 by kelvincool: Respect admin theme during views ajax operations.
• #419270 by voxpelli: set_where_group() could fail if no previous groups.
• #422054 by yhahn: Protect exports from impropertly indenting multiline strings.
• #437070 by mikeryan: Base table formerly limited to 32 characters.
• #317271 by quicksketch: ensure_my_table() limited to one relationship per table.
• #441520 by jonathan1055: Allow the "time ago" date format to work on future dates as well.
• #445398 by casey: reduce_value_options() using wrong value array.
• #451370 by skwashd: base.js had some DOS line endings.
• #454754 by dww: Fix PGSQL related errors with comment author filtering.
• #384286 by dww: Make it possible to expose the filter for "Node: Has new content"

Bugs fixed:

• #363817 by thePanz: Empty fields in table could still trigger separators.
• #388952 by nikita@protsenko.com: Ensure taxonomy term validator sets the validated title when available.
• #392176: Trim on word boundary would stop at newlines.
• #415706 by dww: Fix broken relationship in search that caused SQL error.
• #428742 by fralenuvol: Fix broken relationship causing sql error with multiple taxonomy term arguments.
• #428102 with help from deviantintegral: Broken option_definition() causes warnings.

Other changes:

• #379382 by neochief: Add option to strip tags during advanced rendering.
• #400914 by joachim: Add a link field to get to comments for a node that works just like the normal links.
• #402650 by drewish: Bulk export views alphabetically by view name.

Bugs fixed

• #349739: Fix arguments not getting transmitted to attachment displays properly.
• #354707: Display attachment happened too early preventing default arguments from passing to the attachment.
• #277321 by nedjo: Use AJAX properly supports summaries in attachments.
• #291292 by sammys (reroll by jaydub): Proper use of DISTINCT on summary views on pgsql.
• #291079 by sammys (reroll by jaydub): Fix use of GROUP BY on pgsql.
• #295246 by webchick: Wrong table type on views object cache caused truncation of cached data and mysterious errors on large views.
• #315007 by Garrett Albright, Paul Kishimoto and catch: Take into account page count when using comment new link.
• #317562 by ingaro: Wrong date format for PGSQL.
• #327604 by mr.baileys: Fix improper use of multibyte library when mb library unavailable.

Unfortunately necessary bug fix release to remove debug code I accidentally committed just prior to releasing 2.0.

Changes since DRUPAL-6--2-0:

• #322862: Accidentally 1.0037 committed debug code.
• #322908: README.txt update.
• #323014 by yched: Typo in exposed filter text.
• #323033: Using empty/is not empty in string/numeric filters caused notices.
• #322874 by yched: Errors in summary for some filters.
• #323282: Taxonomy term default choice handled incorrectly.
• #323318: Exposed taxonomy term failed if not set force single.

More bug fixes from RC4; please remember that if you're upgrading from prior to RC2, some modules may stop working! Please read the RC2 release notes for details.

Changes since DRUPAL-6--2-0-RC4:

This release fixes a couple of critical bugs in RC2.

Changes since DRUPAL-6--2-0-RC2:

• Typo was preventing "search" row type from showing up.
• #306832: "parent" incorrectly defined for views_plugin_argument_validate_taxonomy
• Default style renderer could not handle styles that did not use a row plugin; merged views_plugin_style_table::render() into views_plugin_style::render() to address this.
• #292395 by KarenS: Do not crash on view list page if a view has an invalid display.
• #303862: Array addition problems caused failures when using "Node: type" filter twice.
• #308137: Filters were incorrectly checking for current user permissions on header/footer/empty text.
• #309317: invalid HTML in help file

1. There are a couple of bugs in Drupal 6.2 that are fixed in Drupal 6.x-dev that make it very important that Drupal 6.3 is used (or, since that is not currently available, Drupal 6.x-dev).
2. If you find yourself having troubles with the javascript (there are a few people who report problems that we can't figure out yet) the javascript part can be completely turned off and the UI largely works without javascript, though a couple of places (arguments, in particular) may be a little rough.
3. The upgrade path from 1 to 2 is going to take some manual work to convert your Views to the new format. Views2 contains a Views1 conversion tool, but existing views will likely need some additional work to function in Views2
4. Urgent request! We need some help with the documentation, both editing the existing pages, finishing some of the TODO items, and fleshing it out more so that it is more cohesive!

Changes since DRUPAL-6--2-0-BETA4:

This beta release includes a few forgotten features or features I didn't have time for, or features submitted by users that were too good to pass up. Plus, a lot more of the help files are written, if badly.

Specifically: comment RSS, major updates to exposed filters, a bunch of new default views, important fixes for node language filter, taxonomy term with depth argument, argument defaults to try and get 'node' and 'user' ids automatically from the URL, and a whole bunch more I have forgotten.

In case you think I haven't been busy:

Changes since DRUPAL-6--2-0-BETA2:

New features:

• argument defaults and validation; pluggable. This will greatly ease some of the problems with argument discovery. We need to get a few more basic plugins written for this, but basically with a little bit of code you can do all kinds of cool stuff with arguments not there or not matching what you want.
• Quick links on the edit page; hover links on the view view page.
• A weak but expandable view analyzer tool
• Revamped view list page, plus the first advanced help file!
• #248999: (by eaton) Grid style that uses a simple table to display a grid in X columns.
• A theme information tool to give you all the information you need to theme your views.
• Integration with advanced help module. http://drupal.org/project/advanced_help

The Views 1 conversion process is still a little (a lot) rough -- expect to have to do a lot of work to update Views 1 views to Views 2. Still, it does enough that the update isn't awful, and it's a good idea to really rethink the views anyway, since Views 2 operates so much differently.