Problem/Motivation
The change merged in #3589931: Fatal error: Markup::settingsForm() signature must be compatible with FieldGroupFormatterBase updated a function signature to work with Field Group 4.1.x (currently alpha). That change breaks compatibility with Field Group 4.0.x—the stable, recommended release.
Using Field Group Markup 1.0.4 with Field Group 4.0.0 yields the same/similar message as the other issue:
Fatal error: Declaration of Drupal\field_group_markup\Plugin\field_group\FieldGroupFormatter\Markup::settingsForm(array $form, Drupal\Core\Form\FormStateInterface $form_state) must be compatible with Drupal\field_group\FieldGroupFormatterBase::settingsForm() in /var/www/html/docroot/modules/contrib/field_group_markup/src/Plugin/field_group/FieldGroupFormatter/Markup.php on line 64
Steps to reproduce
- On a site using Field Group 4.0.0, update Field Group Markup to 1.0.4
- Visit any form with a Field Group Markup field OR
Visit the Manage Form Display for an entity and attempt to add a Field Group Markup field - Observe the error above
Proposed resolution
Something like:
- Revert the change from #3589931: Fatal error: Markup::settingsForm() signature must be compatible with FieldGroupFormatterBase
- Tag and release 1.0.5 to restore compatibility with Field Group 4.0.x
- Create 1.1.x branch and reapply the change there
- Tag and release 1.1.0 with compatibility for Field Group 4.1.x
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 3612052-04.patch | 645 bytes | ayrmax |
Issue fork field_group_markup-3612052
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
justcaldwellSetting to Needs Review, as this is more about branch/tag changes than code updates.
Comment #4
ayrmax commentedI have created a patch to fix the issue.
Comment #6
dieuweI've gone with a variation of the proposed solution to try and keep 4.0 and 4.1 support in one branch - this module is simple enough to be able to support all major field_group version, I hope.
New release will come when some test coverage to avoid regressions like this is ready.
Comment #7
dieuwe