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
WARNING: calling IsSet with unsupported type "invalid" (<nil>) will always return false.
Not very useful, so I added some more logging to track down the caller in gohugoio/hugo#8668, which yields:
WARNING: calling (isset %!q(<nil>) "taxonomycloud") with unsupported collection type "invalid" (<nil>) will always return false.
WARNING: calling (isset %!q(<nil>) "taxonomypageheader") with unsupported collection type "invalid" (<nil>) will always return false.
a few other places calling {{ if isset .Site.Params.Taxonomy "taxonomypageheader" }}
This isn't an error in the output: if taxonomy isn't set in the config.toml, then no taxonomy is output, as expected. But it is a bit of warning noise for older users upgrading, or new users who deleted the taxonomy section.
How about we check if .Site.Params.Taxonomy is defined before looking to see if it has values set inside it?
The text was updated successfully, but these errors were encountered:
After updating Graphviz's Docsy (https://gitlab.com/graphviz/graphviz.gitlab.io) to the latest Docsy version, I get this error when running:
Not very useful, so I added some more logging to track down the caller in gohugoio/hugo#8668, which yields:
The culprits:
{{ if isset .Site.Params.Taxonomy "taxonomycloud" }}
{{ if isset .Site.Params.Taxonomy "taxonomypageheader" }}
This isn't an error in the output: if taxonomy isn't set in the
config.toml
, then no taxonomy is output, as expected. But it is a bit of warning noise for older users upgrading, or new users who deleted the taxonomy section.How about we check if
.Site.Params.Taxonomy
is defined before looking to see if it has values set inside it?The text was updated successfully, but these errors were encountered: