You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And this content files (optional but to generate atom.xml).
content/hello.md
+++
title = "Hola"
date = 2023-11-21
+++
Hola
content/hello.en.md
+++
title = "Hi"
date = 2023-11-21
+++
Hi
Running zola serve or zola build gives this warning:
Warning: config.toml contains both default language specific information at base and under section [languages.es], which may cause merge conflicts. Please use only one to specify language specific information
I know the culprit is defining generate_feedglobally outside the language blocks ([languages.es] and [languages.en]), but the problem is that if you don't define it there the feed is not generated.
Expected Behavior
In my view, if the generate_feed entry is to be defined in the [language.xx] sections, it should not be necessary to define it globally as well. Or at least, if it is necessary to do so then it should not give that warning.
The text was updated successfully, but these errors were encountered:
I know the culprit is defining generate_feed globally outside the language blocks ([languages.es] and [languages.en]), but the problem is that if you don't define it there the feed is not generated.
Hmm that sounds like a bug for the default language.
Bug Report
Environment
Zola version: 0.17.2
Current Behavior
Given this configuration.
config.toml
And this
content
files (optional but to generateatom.xml
).content/hello.md
content/hello.en.md
Running
zola serve
orzola build
gives this warning:I know the culprit is defining
generate_feed
globally outside the language blocks ([languages.es]
and[languages.en]
), but the problem is that if you don't define it there the feed is not generated.Expected Behavior
In my view, if the
generate_feed
entry is to be defined in the[language.xx]
sections, it should not be necessary to define it globally as well. Or at least, if it is necessary to do so then it should not give that warning.The text was updated successfully, but these errors were encountered: