-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
List items should not require a name
#596
Comments
So, just to clarify, you are wanting it to be like this: images:
- /img/1.jpg
- /img/2.jpg |
Yes :) |
Sorry, I missed that above. I almost wonder if this would be better as a separate Widget type completely. But right now we are setting the name to |
@tech4him1 yeah, that will solve this exact usecase and close this issue. |
Any updates on this matter? Unfortunately, this is the way Hugo sets Open Graph pictures. I tried taking a look at it but couldn't find a starting point. |
Totally forgot about this - it was never a real issue to begin with, just use # config
fields:
- name: images
widget: list
field: { name: image, widget: image }
# output
images:
- /img/1.jpg
- /img/2.jpg Sent with GitHawk |
- Do you want to request a feature or report a bug?
Question, maybe feature.
- What is the current behavior?
The way I define opengraph pictures on my site (using hugo) is to have an
images
array with values being path to pictures as string, not as an object.It should be output as this in the front matter:
So I set up these CMS fields:
However it seems
name
is always output, no matter what I tried:and so this is the current output:
- Question:
Is there any way currently to have multiple list items without any
name
?The text was updated successfully, but these errors were encountered: