-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Module conflict with Taxonomies #8866
Comments
Specifically, none of the taxonomy sections are rendered in the publish directory. |
I'm not sure if any work has been done on this issue since the last comment, but it looks like the upstream module I'm pretty sure the issue has to do with this commit, which is included in the v0.84.0 release and changes the way module configuration is merged into a Hugo project's configuration (release notes). I haven't dug into the commit at all, but I have some time this weekend to start work on a possible PR. |
Forgot to note: @cromozooom to fix your issue now, add |
Thank you Paul
best regards Razvan Nicu
+44 07783363309
www.solopx.com - Please consider the environment before printing this email
…On Sat, Aug 21, 2021 at 7:19 PM Paul Gottschling ***@***.***> wrote:
Forgot to note: @cromozooom <https://github.com/cromozooom> to fix your
issue now, add disableKinds = [] to your config. This will preempt the
disableKinds setting for upstream modules.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8866 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAWFWOEDJXSQJ73NUSRD3KTT57U2FANCNFSM5BXWBJUQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
for the twbs/bootstrap module solves this. |
By default, that setting should not be merged in from upstream modules, but it may look like that is what happens ... |
Unless the merge strategy is set up to do so. For `disableKinds` the current workaround is to make sure the project config has an entry, even if is empty: ``` disableKinds = [] ``` Note that this issue only touches root, non-map config-values that either is not set in project config or in Hugo's defaults. Fixes gohugoio#8866
Unless the merge strategy is set up to do so. For `disableKinds` the current workaround is to make sure the project config has an entry, even if is empty: ``` disableKinds = [] ``` Note that this issue only touches root, non-map config-values that either is not set in project config or in Hugo's defaults. Fixes gohugoio#8866
Unless the merge strategy is set up to do so. For `disableKinds` the current workaround is to make sure the project config has an entry, even if is empty: ``` disableKinds = [] ``` Note that this issue only touches root, non-map config-values that either is not set in project config or in Hugo's defaults. Fixes #8866
That is not the problem (specifically in this case with Bootstrap). Have a look at Bootstrap's config.yml. They do some weird stuff with module imports recursive to their own repo. Disabling the import of their config completely does the trick. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What version of Hugo are you using (
hugo version
)?0.87.0
Does this issue reproduce with the latest release?
Yes
Adding Modules in config makes Taxonomies usless:
This was reported first time here and It looks like the problem was introduced with v0.84.0.
No problems with v0.83.1.
The text was updated successfully, but these errors were encountered: