Key Concepts
This tutorial demonstrates how to integrate custom Drupal 7 database tables with the Views module, enabling powerful querying and data presentation capabilities. We'll cover making Views aware of your module's table structure, defining field handlers for display, filtering, and sorting, and establishing relationships between tables using joins. The process leverages Views handlers – classes managing display, sorting, and filtering operations – allowing for customization beyond default functionality.
This guide focuses on tables not represented as Drupal entities. For entity integration with Views, please refer to other resources.
A sample module, "expose," is available (repository details omitted for brevity). The exposed
table (structure detailed below) will be used for demonstration. Sample data can be inserted using this MySQL command:
INSERT INTO `exposed` (`id`, `name`, `deadline`, `node_id`) VALUES (1, 'Danny', 1399477939, 1), (2, 'Peter', 1399477957, 2);
Integrating Your Table with Views
The integration involves two key steps: informing Views about your module and defining your table's structure.
Step 1: Informing Views about Your Module
Implement hook_views_api()
in your module's .module
file:
/** * Implements hook_views_api(). */ function expose_views_api() { return array( 'api' => 3, 'path' => drupal_get_path('module', 'expose') . '/includes/views', ); }
This specifies the Views API version and the location of your Views-related files.
Step 2: Defining Your Table's Structure
Create expose.views.inc
(in the directory specified above) and implement hook_views_data()
:
/** * Implements hook_views_data(). */ function expose_views_data() { $data = array(); $data['exposed']['table']['group'] = t('Exposed'); $data['exposed']['table']['base'] = array( 'title' => t('Exposed'), 'help' => t('Contains records exposed to Views.'), ); // Field definitions (see below) return $data; }
This code defines the table's group and designates it as a base table, making it available in the Views interface. The field definitions (detailed next) will be added here.
Step 3: Defining Fields
Within hook_views_data()
, add field definitions for each column:
// ... (previous code) ... // ID field $data['exposed']['id'] = array( 'title' => t('ID'), 'help' => t('Record ID'), 'field' => array('handler' => 'views_handler_field_numeric'), 'sort' => array('handler' => 'views_handler_sort'), 'filter' => array('handler' => 'views_handler_filter_numeric'), ); // Name field $data['exposed']['name'] = array( 'title' => t('Name'), 'help' => t('Record name'), 'field' => array('handler' => 'views_handler_field'), 'sort' => array('handler' => 'views_handler_sort'), 'filter' => array('handler' => 'views_handler_filter_string'), ); // Deadline field $data['exposed']['deadline'] = array( 'title' => t('Deadline'), 'help' => t('Record deadline'), 'field' => array('handler' => 'views_handler_field_date'), 'sort' => array('handler' => 'views_handler_sort_date'), 'filter' => array('handler' => 'views_handler_filter_date'), ); // ... (Node ID field and join definition - see below) ... return $data;
This specifies handlers for display (field
), sorting (sort
), and filtering (filter
) for each column. Appropriate handlers (e.g., numeric, string, date) are selected based on data types.
Step 4: Handling Relationships (Joins)
To join with the node
table using the node_id
column:
// ... (previous code) ... // Join definition $data['exposed']['table']['join'] = array( 'node' => array( 'left_field' => 'nid', 'field' => 'node_id', ), ); // Node ID field $data['exposed']['node_id'] = array( 'title' => t('Node ID'), 'help' => t('Node ID'), 'field' => array('handler' => 'views_handler_field_node'), 'sort' => array('handler' => 'views_handler_sort'), 'filter' => array('handler' => 'views_handler_filter_numeric'), 'relationship' => array( 'base' => 'node', 'field' => 'node_id', 'handler' => 'views_handler_relationship', 'label' => t('Node'), ), 'argument' => array( 'handler' => 'views_handler_argument_node_nid', 'numeric' => TRUE, 'validate type' => 'nid', ), ); return $data;
This defines the join and specifies the views_handler_field_node
handler for display, enabling access to node-related fields. A relationship and argument are also defined for filtering and contextual filtering based on node ID.
After implementing these steps, clear Drupal's cache. Your custom table should now be accessible within the Views interface.
Conclusion
This detailed explanation provides a comprehensive guide to integrating custom tables with Drupal 7's Views module. Remember to tailor handler selections to your specific data types and leverage the flexibility of custom handlers for advanced functionality. The FAQs section from the original input has been omitted as it's largely covered within this refined response.
The above is the detailed content of Exposing Tables to Views in Drupal 7. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

TosecurelyhandleauthenticationandauthorizationinPHP,followthesesteps:1.Alwayshashpasswordswithpassword_hash()andverifyusingpassword_verify(),usepreparedstatementstopreventSQLinjection,andstoreuserdatain$_SESSIONafterlogin.2.Implementrole-basedaccessc

TostaycurrentwithPHPdevelopmentsandbestpractices,followkeynewssourceslikePHP.netandPHPWeekly,engagewithcommunitiesonforumsandconferences,keeptoolingupdatedandgraduallyadoptnewfeatures,andreadorcontributetoopensourceprojects.First,followreliablesource

PHPbecamepopularforwebdevelopmentduetoitseaseoflearning,seamlessintegrationwithHTML,widespreadhostingsupport,andalargeecosystemincludingframeworkslikeLaravelandCMSplatformslikeWordPress.Itexcelsinhandlingformsubmissions,managingusersessions,interacti

TosettherighttimezoneinPHP,usedate_default_timezone_set()functionatthestartofyourscriptwithavalididentifiersuchas'America/New_York'.1.Usedate_default_timezone_set()beforeanydate/timefunctions.2.Alternatively,configurethephp.inifilebysettingdate.timez

The method of installing PHP varies from operating system to operating system. The following are the specific steps: 1. Windows users can use XAMPP to install packages or manually configure them, download XAMPP and install them, select PHP components or add PHP to environment variables; 2. macOS users can install PHP through Homebrew, run the corresponding command to install and configure the Apache server; 3. Linux users (Ubuntu/Debian) can use the APT package manager to update the source and install PHP and common extensions, and verify whether the installation is successful by creating a test file.

TovalidateuserinputinPHP,usebuilt-invalidationfunctionslikefilter_var()andfilter_input(),applyregularexpressionsforcustomformatssuchasusernamesorphonenumbers,checkdatatypesfornumericvalueslikeageorprice,setlengthlimitsandtrimwhitespacetopreventlayout

To completely destroy a session in PHP, you must first call session_start() to start the session, and then call session_destroy() to delete all session data. 1. First use session_start() to ensure that the session has started; 2. Then call session_destroy() to clear the session data; 3. Optional but recommended: manually unset$_SESSION array to clear global variables; 4. At the same time, delete session cookies to prevent the user from retaining the session state; 5. Finally, pay attention to redirecting the user after destruction, and avoid reusing the session variables immediately, otherwise the session needs to be restarted. Doing this will ensure that the user completely exits the system without leaving any residual information.

The key to writing clean and easy-to-maintain PHP code lies in clear naming, following standards, reasonable structure, making good use of comments and testability. 1. Use clear variables, functions and class names, such as $userData and calculateTotalPrice(); 2. Follow the PSR-12 standard unified code style; 3. Split the code structure according to responsibilities, and organize it using MVC or Laravel-style catalogs; 4. Avoid noodles-style code and split the logic into small functions with a single responsibility; 5. Add comments at key points and write interface documents to clarify parameters, return values ??and exceptions; 6. Improve testability, adopt dependency injection, reduce global state and static methods. These practices improve code quality, collaboration efficiency and post-maintenance ease.
