Replies: 1 comment 4 replies
-
Thanks for your post! After some careful inspection, no breaking change is needed on DoIt side. The only option that's causing problem is the I have updated the config structure for the exampleSite, and I expect current users can upgrade their Hugo version safely without much trouble. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The story started from gohugoio/hugo#10620
Before 0.112.0, if you have a group of configs, let's take the
[params.app]
as the example:DoIt/exampleSite/config/_default/params.en.toml
Lines 7 to 24 in 35323e4
And let's say we only want the
title
to be different in Chinese and English.What we need to do previously is to copy everything into the
params.en.toml
andparams.zh-cn.toml
, otherwise it won't work.Now, starting from 0.112.0, you can just copy the
title
into the correspondingparams.en.toml
andparams.zh-cn.toml
and leave the rest of the config inparams.toml
. The new merging behaviour will sort this out correctly.Thanks to this behaviour, setting up i18n config is significantly simplified.
But the behaviour changes also deprecate some config structure. If you run
hugo server
on theexampleSite
, it will show the warning⚠:Basically, https://gohugo.io/content-management/multilingual/#changes-in-hugo-01120 said that we should no longer read a parameter from a specific language code (like
languages.en.googleanalytics
in this example), this deprecation also happens if you haveauthor.toml
to be i18n.Now the real problem is, if we fix all these deprecations, do we have to force users to use Hugo 0.112.0? Should we fix these deprecations or not
Beta Was this translation helpful? Give feedback.
All reactions