-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
Build issue in Azure DevOps with latest (0.63.1) Hugo executable #6802
Comments
Thanks for the report, but as we have tested this to work, it must be something "special" with your site. And that is not possible to debug without seeing the source. Could you provide a link to the site's source? |
Your point is valid and I expected it - I'll see what I can do, the site is
not open-source at this time.
…On Sun, Jan 26, 2020 at 5:22 AM Bjørn Erik Pedersen < ***@***.***> wrote:
Thanks for the report, but as we have tested this to work, it must be
something "special" with your site. And that is not possible to debug
without seeing the source. Could you provide a link to the site's source?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6802?email_source=notifications&email_token=AAMLLI65KU4XXILWU544S4DQ7VXARA5CNFSM4KLS4MP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ5RQDY#issuecomment-578492431>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMLLI5BK7BII6KCVJWR5XDQ7VXARANCNFSM4KLS4MPQ>
.
|
@bep I found the issue by trial and error - the taxonomies templates I use (e.g. /categories/list.html) have a Hugo comment outside the
|
See #6816 |
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
)?Does this issue reproduce with the latest release?
Yes
I use Azure Pipelines to deploy site automatically after each commit using latest version of Hugo (Windows 2019 environment). I noticed the tags and categories pages did not render any more - I checked and noticed new 0.63.1 version was in use, versus the 0.62.2 I use locally. I reverted the pipeline to 0.62.2 and that fixed problem, indicating an issue with 0.63.1.
In the attached screenshot you can see the difference in results after 24 hours (1/23 vs. 1/24).
The text was updated successfully, but these errors were encountered: