Voting starts in March for the Drupal Association Board election.
This module provides no direct functionality, so only download it if another module lists it as a dependency, or if you want to write your own module that uses its API.
Field UI and API are designed with the assumption that modules define field types, and administrators create fields and instantiate them within bundles. As part of this assumption, Field API automatically deletes fields when they're no longer in use by any bundles, and Field UI populates the add existing field dropdown only with fields that are in use by at least one bundle. This presents an annoyance for modules that want to define a field and make it available for adding to bundles, but without requiring any particular bundle to use it. ModuleField compensates for this: simply implement hook_modulefield_info() with your field definition and default instance definition, and ModuleField exposes this field within Field UI's add existing field dropdown even if the field has not yet been instantiated in any bundle.
If you're interested in seeing this capability added to Drupal 8 core, please see.
This module is used by TAC Redirect 403, so you can inspect that module's code for a real-world example. If you know of any other modules that use ModuleField, please submit an issue for that module to be referenced from here.
- Maintenance status: Seeking new maintainer
- Development status: Under active development
- Module categories: Developer, Fields
- Reported installs: 39 sites currently report using this module. View usage statistics.
- Downloads: 3,027
- Last modified: December 2, 2014
- This project is not covered by the security advisory policy.
It may have publicly disclosed vulnerabilities. Use at your own risk!