Contrib.social

Changing the sub formatter within a UI patterns field formatter doesn't work as expected

Open on Drupal.org →
Created on 16 February 2023, almost 2 years ago
Updated 6 June 2023, over 1 year ago

Problem/Motivation

When I change the sub formatter within the UI patterns field formatter, the difference in formatter doesn't seem to matter. The rendered output stays to same, independent from the chosen sub formatter.

Steps to reproduce

  • on a field (link field in this example), choose "Pattern (one for all)" as field formatter
  • within the setting form from this field formatter, choose url only as sub formatter (see screenshot)
  • when rendering the page, the field will always be rendered as a link and won't make use of the selected url only field formatter

I did test this with the use of a custom field formatter as well, I can perfectly select the custom field formatter as sub formatter. However, when debugging, I never get to actually breaking onto the custom formatter but keep going to the link formatter.

Proposed resolution

Make it possible after changing the sub formatter within UI patterns field formatter to reflect this change when rendering the field.

Remaining tasks

Discuss why this behaviour is like this.
Create and review the patch.

User interface changes

/

API changes

/

Data model changes

/

🐛 Bug report
Status

Postponed: needs info

Version

2.0

Component

Code

Created by

🇧🇪Belgium økse

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @økse
  • Comment almost 2 years ago →
    🇧🇪Belgium økse

    I did debug this a bit further.

    It looks like the difference in sub formatter within the Pattern (one for all) field formatter doesn't matter because the Pattern (one for all) field formatter doesn't make use of any configured sub formatter.

    Ideally this functionally could be integrated.

  • Status changed to Postponed: needs info over 1 year ago
  • Comment over 1 year ago →
    🇫🇷France duaelfr Montpellier, France

    Hi!
    I don't know where your issue comes from. This is supposed to be working.
    In 2.x if you want your formatted values to be used, you have to set their pattern field to anything else than "- Hidden -". The only reason you could have the behavior you describe is if you didn't.
    If your "Formatted values" source is already mapped to a pattern field then we have a real problem!

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024