-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
collections repeated #2289
Comments
You have the same file for every entry, `src/intl/en.json’. Sent with GitHawk |
Hi @erquhart, yes I have the same file to each entry, 'src/intl/en.json' |
Sorry should have been more clear: that's the problem, you can only have one file per entry. |
Thanks, do you have any solution for this? Or even can I create like separators in the left menu? To create something like this: ENHome ESHome FRHome Or if you have another idea would me great, thanks! |
Check #716 for some ways folks are handling this. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi,
When i try to see in /admin my collections are displayed with the same name, this is my config
collections:
label: "EN"
files:
name: "header"
file: "src/intl/en.json"
label: "Header section"
fields:
name: "Header Section"
file: "src/intl/en.json"
label: "Section One"
fields:
- { label: Title, name: section-one.title, widget: string }
name: "Header Section"
file: "src/intl/en.json"
label: "Section Two"
fields:
- { label: Titulo, name: section-two.title, widget: string }
A solution that I've to make is create it separated like this:
collections:
name: "header"
label: "Header"
files:
file: "src/intl/en.json"
label: "Header section"
fields:
name: "sec1"
label: "Section One"
files:
file: "src/intl/en.json"
label: "Sec One"
fields:
I'm creating different sections because I'm creating a multi lang page with Gatsby and I need to separate it in sections like: 'EN', 'ES'..
Any ideas?
Thanks!
The text was updated successfully, but these errors were encountered: