-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Some issues introduced by the recent CLI/config rewrite #10953
Comments
This is what i got from your last changes @bep
|
Works fine here. Mac OSX Ventura 13.3.1. Brave (latest) |
I use the In hugo v0.111.3+extended this will set
But in hugo v0.112.0-DEV-1155bbca9d4cdf42e9b4a2d0351fd5be0aa8ec08+extended darwin/amd64 BuildDate=2023-05-17T21:35:43Z you need to explicitly set it to false/empty.
This might be more correct but it is a change from how it used to work. I use it like this:
|
Got an new error on an other site. ... the usual WARN about my params. No pb.
line 15 is : list.htmlDetails
|
Oh, forgot but this site works fine in latest official version. No "execute of template failed"
|
@divinerites the {{ range first 1 .Params.images }} issue isn't obvious to me without additional context; you get that error if |
You have the template code in the previous comment. I can give you access to the repo if you need more context.
Well, there is no error in v0.111.3, so to me this is new in this release. But the weird thing is :
So the error in hugo dev reference an unused template ??? |
@divinerites I don't doubt that, but it's just that I need to understand the what to be able to understand how fix it. My recent change set was pretty big (a rewrite of core parts of Hugo), so even if the test coverage in Hugo is pretty good, I was pretty sure that I would accidentally break some glass (which is why we're having this discussion, and I appreciate all the test help I'm getting here). I'm not releasing anything until earliest mid next week I guess. If you could share the broken Site source with me somehow, could look at it (there's an email address on my GitHub profile, or you can PM me on the forum). |
Invite sent. Let me know if i can test further ? |
@divinerites OK, I see it now.
|
Confirmed working with Stiil wondering why an unused template is parsed and make an error ... I guess it is hugo internal workflow. Thanks A LOT for your hard work. |
Just FYI, I have an other site with this "old" syntax. But it pass fine. No error. |
No, that looks fishy ... I added it to my list above (something with the
Sure, the error was just a side-effect. The template code in question is buggy and needs an update (but that's not ... my problem). |
And now with tests. Updates gohugoio#10953
And now with tests. Updates gohugoio#10953
And now with tests. Updates gohugoio#10953
Now, all my sites pass fine without any warn:error, and your last work on different --options works fine 🎆 |
By wrapping all use of the shared config in a lock. Updates gohugoio#10953
By wrapping all use of the shared config in a lock. Updates gohugoio#10953
By wrapping all use of the shared config in a lock. Updates gohugoio#10953
By wrapping all use of the shared config in a lock. Updates #10953
Per comment on #10892, I expected (perhaps incorrectly) this to work:
|
And it ... didn't? The goal was that the above should work, so I will check what happens. |
It works if I also define an empty table:
|
@jmooring good catch, that would have been annoying ... I have pushed a fix. |
Re : |
@divinerites yes, that was a little bit deliberate. I (or someone) need to revisit that |
Also, always include the CSV header. Updates #10953
@divinerites see #10977 |
Great. I'll test it & report when merge is done. Thanks. |
Also, always include the CSV header. Updates #10953
Also, always include the CSV header. Updates #10953
Works as previous here. 👍 |
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. |
List them and fix them here as I (we) find them:
publishDir
vs-d
disableKinds
(e.g.taxonomyTerm
)description
has been a site config option.The text was updated successfully, but these errors were encountered: