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

[FlexFields] Doesn't work for content types that already exist #1366

Open
rdgh01 opened this issue Apr 2, 2024 · 2 comments
Open

[FlexFields] Doesn't work for content types that already exist #1366

rdgh01 opened this issue Apr 2, 2024 · 2 comments

Comments

@rdgh01
Copy link

rdgh01 commented Apr 2, 2024

Describe the bug
Apologies if I have missed something from the instructions but Flexfields doesn't work for me for content types that already existed before Flexfields was installed. I have tested on a test content type created after Flexfields was installed and it works fine. I would like to install Flexfields on a production site which has been running for a while so I would need it work on content types that already exist.

Steps to reproduce

  1. Install FlexFields to a production environment
  2. Add the FlexFields entry editor to a content type that existed before FlexFields was installed
  3. Look at a content entry and see that under the FlexFields entry editor there are no fields showing

Expected result
All the fields should show in the FlexFields entry editor

Screenshot
Screenshot 2024-04-02 161749

@rdgh01 rdgh01 changed the title [Flexfields] Doesn't work for content types that already exist [FlexFields] Doesn't work for content types that already exist Apr 2, 2024
@rdgh01
Copy link
Author

rdgh01 commented Apr 4, 2024

I think I have been able to narrow this down to content types that have a JSON field type. This happens regardless of whether you select a custom appearance APP or the default object. Hopefully that helps @vipulchadda @whitelisab ?

@vipulchadda
Copy link
Contributor

@rdgh01 Thanks for raising this issue and narrowing it down to JSON field type.
Looks like there was an issue raised for this in the default field editors repository related to JSON editor: contentful/field-editors#1458
@whitelisab @lilbitner would you be able to help with this?

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

2 participants