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.A function 'addressfield_field_formatter_settings_form' is declared in 'addressfield' module.
It isn't intended to implement hook_field_formatter_settings_form in this module.
Therefore, when I use this module and addressfield module, an error is happen.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | formatter_field-error_message_on_format_switch-1393488-5.patch | 1.26 KB | zipymonkey |
| #4 | formatter_field-error_message_on_format_switch-1393488.patch | 598 bytes | zipymonkey |
Comments
Comment #1
zroger CreditAttribution: zroger commentedThis is an issue with addressfield accidentally implementing a hook. Moving to that issue queue.
Comment #2
helior CreditAttribution: helior commentedIt seems as though $items[$delta] in formatter_field_field_widget_form() references the *previously* selected "Field to be formatted", which I'm guessing is causing incorrect data getting passed into it, and thus PHP notices of missing array keys (often in the settings array). This can be tested with any field module that implements formatter settings.
Comment #3
helior CreditAttribution: helior commentedMoving issue back into Formatter Field.
Comment #4
zipymonkey CreditAttribution: zipymonkey commentedThanks for the feedback @helior. Here is a simple patch that grabs the default field formatter settings.
Comment #5
zipymonkey CreditAttribution: zipymonkey commentedThere is an issue with patch in #4 when creating new nodes. The patch found here seems to fix this: http://drupal.org/node/1762202#comment-6482248
There is a new patch that combines both.
Comment #5.0
zipymonkey CreditAttribution: zipymonkey commentedparticular in this module
Comment #6
vlad.dancerI've came from #1762202-2: Field value(s) reset when a field with unlimited values gets added a new value in the node edit form.. And it seems that http://drupal.org/node/1762202#comment-6482248 fixes bug. This patch doesn't allow save field settings for Default value setting, the setting alway still seted with default value, not with my.
There is one note for bug reproducing, in my case I had warnings only when creating bean, not on the edit form (also I have 7.x-1.0-beta3 version of the formatter_field).
Comment #7
Chris Matthews CreditAttribution: Chris Matthews commentedClosing this issue as a duplicate of #1762202: Field value(s) reset when a field with unlimited values gets added a new value in the node edit form., which was a duplicate of #1394566: The formatter setting doesn't work on node save or on node edit when changing the image that is fixed.