Module conflict with Taxonomies

[cromozooom]

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:

baseURL = "/"
languageCode = "en-us"
title = "My New Hugo Site"
theme = "hugo"

[module]
[[module.imports]]
path = "github.com/cromozooom/gohugo-modules"

[taxonomies]
	category = "categories"
	tag = "tags"
	artwork = "artworks"
	support = "support"
	subject = "subject"

This was reported first time here and It looks like the problem was introduced with v0.84.0.

No problems with v0.83.1.

[jmooring]

Adding Modules in config makes Taxonomies useless:

Specifically, none of the taxonomy sections are rendered in the publish directory.

[ptgott]

I'm not sure if any work has been done on this issue since the last comment, but it looks like the upstream module github.com/twbs/bootstrap, listed in @cromozooom 's module config, includes taxonomy under disableKinds (https://github.com/twbs/bootstrap/blob/9e1d81a851cac268ca70e95d62c3e968e7293b41/config.yml#L21), which stops the taxonomy pages from rendering.

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.

[ptgott]

Forgot to note: @cromozooom to fix your issue now, add disableKinds = [] to your config. This will preempt the disableKinds setting for upstream modules.

[cromozooom]

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> .

[davidsneighbour]

[[imports]]
path = "github.com/twbs/bootstrap"
disable = false
ignoreConfig = true
ignoreImports = true

for the twbs/bootstrap module solves this.

[bep]

disableKinds = [] to your config. This will preempt the disableKinds setting for upstream modules.

By default, that setting should not be merged in from upstream modules, but it may look like that is what happens ...

[davidsneighbour]

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.