Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
This release resolves some regressions in the last release, and some other long-standing bugs. Thanks to everyone who collaborated to fix the bugs, it's greatly appreciated.
This release brings PHP 8.0 compatibility to the Views world, which will help a lot of other modules pass their PHP 8 tests because of dependencies. Also included are a number of small bug fixes. Updating is recommended for all sites, but as always please test on a copy of each site and not directly on production. Huge thank you to everyone who contributed in some way to this release!
This includes a few minor changes since rc1. As always, a huge thanks to everyone for collaborating on this release, we hope it proves stable for all sites.
As with all releases, please test on a copy of your site(s) before uploading it to production, just to make sure that there aren't any unexpected changes.
This is a release candidate for the 7.x-3.24 stable release, hopefully there won't be any more bugs found in the next week-or-so and we'll release this as 7.x-3.24. Please help test it against your sites (not a production copy, just to be sure!) and report any bugs you find immediately. Thank you.
Also, a huge thank you for everyone who has contributed to this release, there are a load of bug fixes and small additions, the Views-D7 maintainers and I truly appreciate all of your efforts!
This contains a single fix for PHP 5.3 compatibility that was causing problems for some sites and automated test integration for other contributed modules. Sites which use newer versions of PHP do not need to worry about updating to this release and should wait for the forthcoming 7.x-3.23 release.
This fixes a critical bug in the last release, updating is recommended for all sites.
I am sincerely sorry for the oversight with renaming the hook - I did not think many modules would be using it, because of what it did, but I neglected to double-check my hypothesis before committing the change. Had I checked I would have realized that many critical modules used it - Features, Authcache, Webform, even the drupal.org custom code.
PLEASE NOTE: This release includes a critical regression that was fixed in 7.x-3.20, please install that version instead.
This release includes a wealth of small fixes and improvements. Updating is suggested for all sites. Please open new issues for any regressions that are discovered. As always, a huge thank you to all of the contributors who made this release possible!
This release fixes a number of bugs, several of them regressions from previous releases. No security-related bugs are included in this release, but updating is still recommended. Please see the issue queue to identify other known regressions.
Thanks as always to our many contributors, and a special thanks to MustangGB for spending a lot of time triaging the issue queue.
This is a rather major bug fix release. It is strongly recommended to thoroughly test this release before uploading to a production site in case there are any regressions. There are two changes since 7.x-3.15 which affect how CSS classes are generated, so please pay particular attention to the themed output. Please report regressions immediately so that we can rectify them in a future release.
A sincere thank you to everyone who has helped with this release.
This release is focused primarily on fixing bugs and regressions, plus some minor tweaks that should not affect sites. Presuming there are no regressions from this, this will be released as v7.x-3.16 in two weeks.
The security issue in views is caused by various places in the views UI where a string is not sanitized,
because it has been assumed to be static and by commiters, though you can change some of these strings using other administrative permissions. SA-CONTRIB-2013-035 - Views - Cross Site Scripting (XSS)
Other commits:
#82088 by grisendo: Add sanitation in various places in the views UI
#1920690 by jnettik: Added Allow for inline to be configured for jump menus.
#1551534 by bcn: Added Allow a button in an exposed forms to trigger ajax.
#1914024 by peximo | heyyo: Fixed Title-overriden term name not translated on a taxonomy overriden views page.
#1889198 by Pedro Lozano: Fixed Performance problem in _views_fetch_data(), multiple unnecessary cache rebuilds.
#1496418 by dawehner, hass, webflo: Fixed Views: Don't change capitalization of translatable strings with CSS.
#1852116 by Les Lim, Chris Burge: Added Backport from D8: Customizable true/false Views output for booleans.
WARNING: Maintainers are working to fix a bug that was found after the 7.x-3.4 release that causes some Views pages, blocks, attachments and feeds to disappear after upgrading from 3.3 to 3.4. Stay informed of progress at the following link: 7.x-3.4 Upgrade is cancelling boolean operator settings. It is recommended to wait to upgrade until this bug has been fixed.
After the final release of 7.x-3.0 here comes 6.x-3.x
If you want to update from 6.x-2.x please consider that 6.x-2.16 is still the main stable version for drupal6, so
as always do your backups etc.
Thanks for all contributors on views3, especially dagmar.
If you want to get the new features of views3 look at previous changelogs/drupal watchdog or some presentations on drupalcamps/drupalcons. It's too much to describe here.
Hopefully this will be more or less the last big step before a release.
Not this release fixes a security problem, which can be seen as critical
The Views module is useful for creating lists of items in Drupal sites. Some filters incorrectly used Drupal's built-in database api, so they didn't escaped some arguments correctly. This vulnerability is mitigated by the fact that a site must have a view with this filter to be enabled in order to be exploited.
This version of views fixes some upcoming bugs which were caused by the latest update to 6.x-3.0-rc2
Most important to mention is the replacement-patterns bug, which caused problems if you used flag for example.
This version of views fixes some upcoming bugs which were caused by the latest update to 6.x-2.14.
Most important to mention is the replacement-patterns bug, which caused problems if you used flag for example.
IMPORTANT: 2.15 is 2.13 just with a fix for replacement-patterns. This might have affected you if you use flag, for example. So no new features since 2.11 is in this version. If you want new features or currently use 2.14, please use 6.x-2.16
This release is the same as 6.x-2.12 beside one security change.
Note that this means that this is also 6.x-2.11 so no changes regarding bugs/features since 2.11 are in this release. See SA-CONTRIB-2011-052 .
This release of Views includes many improvements over beta3. Please note that you must update to the latest release of CTools. Also note that Drupal 7.2 contains a bug that will cause update.php to break your system. Please update to the latest Drupal 7.x-dev before running update.php.
Lightning fast update from beta1, as I screwed up one of my last commits and it didn't make it out.
THIS STILL APPLIES: If you're having trouble with Views' menu items appears or views acting really really off, clear cache twice and force a menu rebuild. drush cc all if using drush, or the cache clear button on the performance page if not.
The long awaited beta release of Views for 7.x is here.
The list of features, updates and changes is entirely too numerous to enumerate here.
This release includes the new UI.
This release requires CTools 7.x-1.0-alpha4.
This release will probably require you to force a menu rebuild at least once and sometimes twice.
The upgrade path is rocky for CCK fields to field API but seems to be pretty solid for most core fields.
Please note that Views for Drupal 7 now requires CTools!
KNOWN ISSUES
===========
There is NO upgrade path yet. There is a patch but it is very unstable.
The search filter is completely broken and will not work.
Sometimes AJAX does not bind to the preview and it opens in a new page.
Probably lots of other little things.