Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.This project is not covered by Drupal’s security advisory policy.
The default implementation for ordering fields in Drupal stores weights together with the field instance. This works well as long as you know that there is only one canonical source for these weights, but in reality this might not be true. Consider the following situation:
- The node module adds a body field by default for each content type
- You have a feature that adds two field instances to the same content type.
- You want to use the things below as a base, but you want to change the weights.
If you would want to change the weights, you would have to override the first feature, and put the field created by node module into a feature and put the whole field instance definition in features, even though you just wanted to change the field weights.
This module adds a variable for each entity, bundle and view mode with that stores an array with the current order. Since all the fields are in there, we have a proper ordering rather than having individual weights.
Usage
- Enable the module and Strongarm
- Order your weights as usual.
- Go into features, and add the variable with the proper weights. The variable is called field_order_[entity_type]_[bundle]_[form/display]
Project information
- Project categories: Developer tools, Site structure
21 sites report using this module- Created by fabsor on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
