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 is a BREAKING update for users of jQuery UI and jQuery Accordion renderers. You must enable the new submodules to continue to use those renderers. Then it would be a good idea to edit each Quick Tabs instance and check and save your settings. As this is an alpha to alpha release, breaking changes can happen on the way to a full version. Alas, there are still key outstanding issues that are not letting me move this to even a beta stage at this point. I have made a number of updates recently though that deserve this release.
This is not the beta that I had hoped to get done. There are some of the issues in my beta to release plan that have not been finished. However, there have been quite a few fixes since the last release, so I figured that this should be released.
Fixed a bug with the accordion js where the history stuff was firing even without the history option being enabled
Should be using element_children when grabbing the tablinks as under certain circumstance there are other array properties like #array_parents that get included by mistake
Fixed a bug that caused the core version of jquery to get loaded via ajax if jquery update was enabled, overriding the newer version #668698: Tabs translation
The 3.x branch of Quicktabs introduces ctools-based exportability of Quicktabs instances. This meant changing from serial IDs to machine names, and so upgrading an existing site from the 6.x-2.x branch to the 6.x-3.x branch means generating machine names for any existing instances. However, since block placements for Quicktabs blocks went originally by the qtid, any block placements will have to be redone.
This release represents a major overhaul of the Quicktabs API such that, while the basic functionality and UI haven't changed all that much, the code is much more extensible and the functionality can be extended in several ways. An explanation of the main ways for developers to extend Quicktabs can be found in the README.txt file but below is a list of the most important changes:
Now has a pluggable OO architecture, using Ctools to manage plugins. There are two types of plugins - renderers and content plugins.
The module ships with 3 renderer plugins: classic Quicktabs, jQuery UI Tabs and jQuery UI Accordion.
The content plugins available are block, node, view and qtabs, which are the same types of things that could previously be loaded in Quicktabs tabs but developers can now write plugins to enable the loading of other types of content into tabs.
There is now a separate Tabstyles module providing style options for the classic Quicktabs renderer. The same styles are still available.
The 2.x branch of Quicktabs for Drupal 7 aims to continue the same functionality that was provided in 6.x-2.x with the exception of the addition of exportables.
#343246 by quicksketch, add1sun - Views style plugin to display list of nodes as quicktabs
#640598 by killes - hiding empty views tabs when they don't have exposed filters
Implementing merlinofchaos's solution to the problem of adding additional css/js files and js settings to ajax-loaded content, as per the CTools AJAX framework
#908740: Adding note in README.txt re private cck fields
This branch of Quicktabs represents a departure from previous versions in that it uses the jQuery UI Tabs plugin for its tabs functionality, following #553070: Merge with tabs module for D7?. It also leverages the new AJAX framework for ajax loading of content. It still requires a lot of work.
Enhancements including:
- ability to hide empty tabs
- ability to set the default tab, both through the UI and programmatically
- addition of hook_quicktabs_alter to allow other modules to modify quicktabs before rendering
This release includes a total refactoring of the quicktabs.js file and the introduction of the progress bar for ajax-loading tabs, as well as some minor bug fixes.
changes since QT 1.x:
1. AJAX-enabled Quicktabs. There are now two types of QT block you can create: the normal one, as per QT 1.x, where all content gets loaded and there's just show/hide functionality when you click on the tabs; and the AJAX version, where only the content of the active tab gets loaded initially, content for other tabs being loaded via ajax on tab click.
2. Block, node, view and quicktab can be used as a tabpage.
3. Different styles can be selected for different quicktabs.
This release contains one important bug fix - a missing t() which caused havoc for localised versions (see http://drupal.org/node/264820). It also includes a new theme function for output of the tabs.
This release includes some fairly big changes to the admin interface, including the ability to add and remove tabs and rearrange the order of tabs. It also adds a jQuery effects feature and fixes some minor bugs such as the css which prevented the settings radio buttons from showing up in IE6.
Added two new configuration settings:
- Option to hide the titles of blocks within QT blocks
- Option to choose whether your views should be built as 'embed', 'page', or 'block'
Development snapshot of quicktabs for Drupal 6. New Features include AHAH functionality for adding new tabs and DRAG and DROP functionality for re-arranging tabs.
Fixed the bug that was causing blocks to show up without proper css classes or ids, as per issue #235580 from duvien.
Also re-implemented the patch from blackdog regarding issue #229738, which had somehow gotten overwritten before the 1.0 release.