Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interface Display Template for Repeater doesn't show configured values #9587

Closed
3 tasks done
minyan-gu opened this issue Nov 8, 2021 · 1 comment · Fixed by #9588
Closed
3 tasks done

Interface Display Template for Repeater doesn't show configured values #9587

minyan-gu opened this issue Nov 8, 2021 · 1 comment · Fixed by #9588
Assignees
Labels

Comments

@minyan-gu
Copy link

Preflight Checklist

Describe the Bug

The template for Repeater field type seems stops render on item details page after Directus version update from 9.0.0-rc.99 to 9.0.0

checked on 9.0.0-rc.100 as well, appears this is already broken, but works on 9.0.0-rc.99

To Reproduce

  1. Create a field as Repeater type, create two sub-fields wagering_requirement and conversion_rate, in the template field, I want to display as this: Wagering Requirement: {{wagering_requirement}}, Conversion Rate: {{conversion_rate}}
    image

  2. In version 9.0.0-rc.100 and above, I see the UI is not rendering the template anymore, it only display the first sub-field value:
    image

However in 9.0.0-rc.99, it shows up as expected
image

Errors Shown

No response

What version of Directus are you using?

9.0.0

What version of Node.js are you using?

16.13.0

What database are you using?

Postgres 13

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying Directus?

Docker

@azrikahar
Copy link
Contributor

@minyangu-bgl thanks for the detailed description, especially pinpointing which exact version did it started to not work! This helps a ton in finding out what was the regression introduced in rc.100.

Opened a PR to fix this 👍

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants