Components
- Code
- Documentation
- Miscellaneous
- User interface
Images
Licence
https://www.gnu.org/licenses/old-licenses/gpl-2.0.htmlpermet quand on rajoute un champ sur une entitée d'updater tout le contenu existant avec une valeur par défaut
Release
Alpha releases are not covered by Drupal security advisories.
Release type : Bug fixes Release type : New features
Covered by Drupal's security advisory policy
Release type : Bug fixes
Covered by Drupal's security advisory policy
Release type : Bug fixes
Description
Field Defaults allows batch updating of default field values to existing content. When adding a new field to an entity you can update all existing content with the default value or when editing an existing field you can choose to also update all existing content with the new value.
Drupal 10/11 Version
- Supports not updating changed date of entity
- Configure if existing content is overwritten with the new value.
- Supports any fieldable entity type
- Supports Translations
- Drush support
2.1.x
This branch is a refactor of the existing functionality with plans to allow extension to add support for any potential field widget. All new features/functions will go into this branch.
*NOTE: Due to the nature of the module, it is highly recommended you backup your database prior to updating defaults on existing content or perform updates first in a development environment to confirm results.
Difference between other Bulk operation modules
Other modules such as VBO have similar functionality.
The difference is that with Field Defaults you have the option to only edit the field if it didn't have a value (which is a condition that you could copy in a VBO action only with custom code, or by using eca_vbo module). You also benefit from not having to filter and select the entities to update. You can automatically update all the entities that have that field, directly from the field settings form.
Toutes les informations proviennent du site drupal.org