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.
- Issue #3393564 by Shreya_th, joachim, mellowtothemax, paulrad, marcusx: Fixed warning when modules call getSetting() with an unknown setting name.
- Issue #3384055 by DieterHolvoet: Extracted UI to a submodule.
- Issue #3410696 by sidharth_soman, wxman: Fixed undeclared property.
- Issue #3383437 by La vague illuminee: Fixed image field type can't be used for computed fields.
- Issue #3372109 by joachim , gcb: Fixed fields using lazy builder causing crash in entity preview.
- Issue #3368642 by mrinalini9, arti_parmar, sidharth_soman: Fixed classes using \Drupal calls instead of dependency injection.
- Added details about core patches to README.
Computed fields defined in config were not being added to the field map, which means they weren't appearing in various places that were looking for field definitions, such as Layout Builder's list of field blocks. This is now fixed for fields created with this release. For existing computed fields, doing a config export followed by a config import should update the field map.
The getFieldDefinitionSetting() method has been removed from ComputedFieldPluginInterface. Computed field plugins now need to implement getFieldDefinitionSettings().
To improve security, PHP code can no longer be entered from the front-end: If you've been implementing computed fields this way, you'll need to move the code from your configuration into a custom module.
As per #2888867: What are the hook parameters ?, it wasn't obvious how to implement the compute function in code. The in-line documentation in the field help text has been improved to fix this.
Just like in D7, it's now possible to place your compute code in one of your custom modules as a function. Enjoy the security of not having users enter code from the Web UI, and keep it revision controlled with Git.
I checked to see if there's anything in 1.x that needs to be ported to 2.x, and there isn't. As such, we can officially declare 1.x dead; it will no longer be supported.
Rolled back the patch from issue #414088 so that Computed Field does calculation on insert/update once again, rather then presave. This allows computed code to always have the nid of the node available.
A couple minor bug fixes, and computation moved to "presave" rather then "insert/update." Also compatibility with CCK multigroups. If no major bugs are reported this will be the last beta, and I'll release a long overdue official 1.0.
#349548 by markus_petrux - enables the use of Computed fields in multigroups.
#349548 by markus_petrux - Updating hook_content_is_empty()
#576334 - Added note about DB storage for Views and try to clean up $ tags
#414088 by matt2000 - Move computation to presave rather then insert/update
Updated Hungarian translation
The update to 5.0 is working with all of the examples in the readme. You'll probably need the cvs version of drupal for this to work, as CCK has issues with beta 1.
This release has also gotten rid of the old license, using LICENSE.txt instead.
The update to 5.0 is working with all of the examples in the readme. You'll probably need the cvs version of drupal for this to work, as CCK has issues with beta 1.