-
Notifications
You must be signed in to change notification settings - Fork 887
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
Latest netlify deploy has new warning message "calling IsSet with unsupported type" #901
Comments
I'm afraid, that its related to my changes from #895, because I've build in isset on 2 places. Sorry. I'll take a look. |
But the issue with isset rises only a warning and in the next line of the log it shows an error: 8:27:53 PM: Error: Error building site: POSTCSS: failed to transform "scss/main.css" (text/css). Check your PostCSS installation; install with "npm install postcss-cli". See https://gohugo.io/hugo-pipes/postcss/: this feature is not available in your current Hugo version, see https://goo.gl/YMrWcn for more information Look more like a problem with SCSS/CSS, I think. |
These are 2 different, unrelated issues:
For me, these are separate, independent issues, that's why a raised two separate issues (#900 / #901). |
The build failure was my bad, and has been fixed. Thanks for reporting those @deining. |
The warning is still there, for example, see the latest production log. |
OK, I'll take a look after official work ;-) |
I think, I know why you get the warning. But I can't figure out, why I DON'T get the warning on my system. Hugo is building the site without any warning. I'm using hugo v0.92.2+extended darwin/amd64 on a MAC. Have anyone an explanation for that? |
I'm using the same version of Hugo under macOS. Which command are you using to build? |
OK, I've found it. Was my fault: haven't build the userguide but my own site with dev content. |
Oh, there's a long story I'd completely forgotten.
The problem is, I want to control 3 different states with one parameter
The easiest way I see would be to set at least the parameter group
instead of Lines 231 to 234 in f03cba0
==> Would this be OK? Or have anybody any other solution? |
I would not force projects to set a field. I believe that use of |
Btw, I think that the problem is because you're testing whether a field of |
I've already thought about that possibility, but then I have to double the code for FALSE: {{ $context := . }}
{{ if isset .Site.Params "taxonomy" }}
{{ if isset .Site.Params.Taxonomy "taxonomycloud" }}
{{ range $index, $taxo := .Site.Params.Taxonomy.taxonomyCloud }}
{{ if isset $.Site.Params.Taxonomy "taxonomycloudtitle" }}
{{ $.Scratch.Set "title" (index $.Site.Params.Taxonomy.taxonomyCloudTitle $index) }}
{{ else }}
{{ $.Scratch.Set "title" (humanize $taxo) }}
{{ end }}
{{ partial "taxonomy_terms_cloud.html" (dict "context" $context "taxo" $taxo "title" ($.Scratch.Get "title")) }}
{{ end }}
{{ else }}
{{ range $taxo, $taxo_map := .Site.Taxonomies }}
{{ partial "taxonomy_terms_cloud.html" (dict "context" $context "taxo" $taxo "title" (humanize $taxo)) }}
{{ end }}
{{ end }}
{{ else }}
{{ range $taxo, $taxo_map := .Site.Taxonomies }}
{{ partial "taxonomy_terms_cloud.html" (dict "context" $context "taxo" $taxo "title" (humanize $taxo)) }}
{{ end }}
{{ end }} But for me it's OK. I'll prepare the PR. |
Closed by #909 |
With latest commit 66818eb in place, I now see a warning when serving the user guide.
This warning can be seen also in the netlify log for this commit (line 95).
@raum51: is this warning related to the changes you submitted with #895?
The text was updated successfully, but these errors were encountered: