Hugo 0.18 Release Scheduled for Mon 19th December, please help test, test, test!


#1

Mon 19th December is the scheduled date for a Hugo 0.18 release.

This release contains an unusual amount of structural changes – they are backwards compatible and is tested on the border of Paranoia, but I’m still a little bit surprised I haven’t seen more “my site is broken” – so I would appreciate if those who could would take it for a spin, and report back with any problems.


#2

It builds without any error on v0.18-DEV ( Hugo Static Site Generator v0.18-DEV BuildDate: 2016-12-02T18:15:12-05:00 ), except:

  • A lot more pages are created now… 3x the # of pages compared to v0.17 (It says so, but I cannot find those extra pages :slightly_smiling:)
  • Getting a helpful warning like “.Page’s RSSlink is deprecated” (now fixed)

With v0.18-DEV

> hugo
Started building sites ...
WARNING: .Page's RSSlink is deprecated and will be removed in a future release. Use RSSLink instead.
Built site for language en:
0 draft content
0 future content
0 expired content
105 pages created
0 non-page files copied
4 paginator pages created
67 categories created
total in 313 ms

With v0.17

> hugo
Started building sites ...
Built site for language en:
0 draft content
0 future content
0 expired content
35 pages created
0 non-page files copied
4 paginator pages created
67 categories created
total in 482 ms

[Source]


#3

About the “105 pages created”, is there a bug in that calculation?

I did tree -a in both public/ dirs (for 0.17 and 0.18), and that shows the exact file count in both: 114 directories and 211 files.


#4

I have created https://github.com/spf13/hugo/issues/2757

Not sure what it is, but the definition of page has changed somewhat …

I notice a considerable speedup of your site, too …


#5
Hugo Static Site Generator v0.18-DEV-15622C8 BuildDate: 2016-12-02T12:14:41-06:00
$ hugo 
Started building sites ...
WARNING: .Page's RSSlink is deprecated and will be removed in a future release. Use RSSLink instead.
Built site for language en:
0 draft content
0 future content
0 expired content
29 pages created
0 non-page files copied
0 paginator pages created
9 tags created
5 topics created
total in 35 ms

That 29 pages matches the count of

  • 1 home
  • 9 content
  • 3 sections (post + project + presentation)
  • 9 tags
  • 1 at tag root
  • 5 topics
  • 1 at topic root

#6

Just tested with a build from master branch 15622c80eec. Works correctly for most purposes. Built my current, 0.17-based site without issues. There’s only an issue with refreshing data for sections with server.

I adjusted my template to use the following in layouts/index.html:

{{ range (where .Site.AllPages "Kind" "section").Reverse }}
    {{ .Title }}
    {{ .Params.teaser }}
{{ end }}

where teaser is set in the front matter of a section, of course, ie. content/foo/_index.md:

---
title: Some Title
teaser: Coming soon!
---

Now when I’m running hugo server, when I change anything in content/foo/_index.md, hugo correctly notices it, refreshes the page in my browser, but the values on the page stay the same. I have to restart hugo server to see the effect.

Interestingly, this works correctly on section pages, ie. when I browse to http://localhost:1313/foo/, the values would be refreshed.


#7

Just a note to the above: AllPages returns ALL pages for ALL sites (if you have only one language it does not matter of course). This may be what you want, but just wanted to point out. .Site.Pages returns the current site’s page collection (oh, and I have added the maybe undocumented .SIte.RegularPages as a shortcut to exclude the home page etc.)


#8

Based on above, the count of 29 already includes the “9 tags” and “5 topics” pages, whereas those counts are printed independently too.

I found the “content page count” as a very useful feedback. Actually that was the main number I paid attention to when publishing.

@bep So while the total count of 29 is kept, can the content page count be re-added as well?


#9

That’s right, after that, I have noticed that the publishing speed is consistently faster too :slightly_smiling:


#10

On a side note, I have now started publishing using the 0.18-DEV version on Gitlab Pages. Works great!


#11

See https://github.com/spf13/hugo/commit/ba8a00a6f98650340457d79927352dc542001bba


#12

I notice this on the GitLab build:

Built site for language en:
0 draft content
0 future content
0 expired content
105 pages created
0 non-page files copied
4 paginator pages created
67 categories created
total in 4288 ms

Is the GitLab servers so slow?


#13

That’s doing what I’d expect:

Hugo Static Site Generator v0.18-DEV-BA8A00A BuildDate: 2016-12-03T10:54:19-06:00
INFO: 2016/12/03 10:54:33 hugo.go:349: Using config file: /Users/mdhender/Software/git/nixon/config.toml
WARN: 2016/12/03 10:54:33 hugo.go:469: No theme set
INFO: 2016/12/03 10:54:33 hugo.go:493: /Users/mdhender/Software/git/nixon/static/ is the only static directory available to sync from
INFO: 2016/12/03 10:54:33 hugo.go:532: syncing static files to /
Started building sites ...
INFO: 2016/12/03 10:54:33 site.go:1482: found taxonomies: map[string]string{"tag":"tags", "topic":"topics"}
WARN: 2016/12/03 10:54:33 site.go:1804: Unable to locate layout for 404 page: [404.html]
WARN: 2016/12/03 10:54:33 site.go:1772: 404.html is rendered empty
Built site for language en:
0 draft content
0 future content
0 expired content
9 regular pages created
20 other pages created
0 non-page files copied
0 paginator pages created
9 tags created
5 topics created
total in 23 ms

Aside: it seems odd that server --verbose doesn’t throw out the version information. It’s a nit.


#14

How are you getting the commit hash in hugo version?

hugo version gives me just

Hugo Static Site Generator v0.18-DEV BuildDate: 2016-12-03T11:56:48-05:00


#15

I’m doing a pull, govendor sync, then make check && make install.


#16

Thanks. I do just go get -u -v --ldflags '-extldflags "-static"' github.com/spf13/hugo, and probably so I get a different version string.


#17

No issues with a slightly bigger site. I don’t have anything using i18n, so can’t compare that to 0.17.

Hugo Static Site Generator v0.18-DEV-BA8A00A BuildDate: 2016-12-03T10:54:19-06:00
Started building sites ...
Built site for language en:
0 of 12 drafts rendered
0 future content
0 expired content
151 regular pages created
301 other pages created
0 non-page files copied
0 paginator pages created
22 topics created
273 tags created
total in 180 ms

#18

Nothing too surprising building Hugo Docs. I don’t recall the GitInfo error happening before…

Hugo Static Site Generator v0.18-DEV-BA8A00A BuildDate: 2016-12-03T10:54:19-06:00
Started building sites ...
ERROR: 2016/12/03 13:50:36 gitinfo.go:63: Failed to find GitInfo for "Users/mdhender/Software/go/src/github.com/spf13/hugo/docs/content/troubleshooting/strange-eof-error.md"
Built site for language en:
0 draft content
0 future content
0 expired content
205 regular pages created
72 other pages created
0 non-page files copied
0 paginator pages created
58 tags created
0 groups created
total in 611 ms
Watching for changes in /Users/mdhender/Software/go/src/github.com/spf13/hugo/docs/{data,content,layouts,static}
Serving pages from memory

#19

#20

I rebuilt my site with the latest code in master and didn’t see any regressions. So thank you! :tada:

I do see some slight differences in the generated index.xmls for different sections, e.g. the following

diff -ur public-new/photos/index.xml public-old/photos/index.xml
--- public-new/photos/index.xml	2016-12-03 23:25:12.000000000 +0000
+++ public-old/photos/index.xml	2016-12-03 23:24:58.000000000 +0000
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="utf-8" standalone="yes" ?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
-    <title>Photos on Harish Narayanan</title>
+    <title>Photos-rss on Harish Narayanan</title>
     <link>https://harishnarayanan.org/photos/index.xml</link>
-    <description>Recent content in Photos on Harish Narayanan</description>
+    <description>Recent content in Photos-rss on Harish Narayanan</description>
     
     <language>en-gb</language>
     <lastBuildDate>Tue, 21 Oct 2014 00:00:00 +0000</lastBuildDate>

But these are minor and completely unrelated to the major recent changes.