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

[BUG] Field with same name as other one inside repeater overwrites config of the first one #7496

Closed
JarJak opened this issue May 23, 2018 · 3 comments
Assignees

Comments

@JarJak
Copy link
Member

JarJak commented May 23, 2018

Bug summary

If field in repeater has the same name as other field outside of this repeater, then the first one takes configuration from the second. Configuration of field in repeater is overwritten.

Details

  • Relevant Bolt Version: 3.5.1

Reproduction

Content type config:

articles:
    name: Articles
    fields:
        details:
            type: repeater
            label: Details
            fields:
                value:
                    type: html
                    label: Details information
                type:
                    type: select
                    label: Detail type
                    values:
                        important: Important!
                        normal: Normal one
        type:
            label: Article type
            type: select
            values: 
                news: News
                other: Other article

With this config, enter Article edit page and you can notice that Detail type select has values taken from Article type.

Expected result

Detail type select should have options: Important!, Normal one.

Actual result

Detail type select has options: News, Other article.

@bobdenotter
Copy link
Member

I think this is a duplicate of an existing issue.

@JarJak JarJak changed the title [BUG] Field with same name as other one inside repeater overwrites config of the other [BUG] Field with same name as other one inside repeater overwrites config of the first one May 23, 2018
@JarJak
Copy link
Member Author

JarJak commented May 23, 2018

Probably related to #7461 but not the same. Both cases should be tested after fix.

@rossriley rossriley self-assigned this May 31, 2018
@rossriley
Copy link
Contributor

Different Bug confirmed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants