Fix layouts of lists and content

[sergobot]

Hugo v0.17 was giving errors like this:
ERROR: 2016/11/05 20:32:30 template.go:132: template: theme/partials/content.html:8:40: executing "theme/partials/content.html" at <.Site.Params.dateFor...>: invalid value; expected string in theme/partials/content.html

Now there are no errors and hugo-goa-demo works properly after this commit. Also, it seems to be solution for #4.

[shenoydotme]

Thank you @sergobot

[shenoydotme]

@sergobot, this has not fixed the issue. When I tested it locally, the string .SITE.PARAMS.DATEFORMAT replaces the date. The issue is most probably something with the users config. I'd have to revert this change for now since it is breaking my site. I'll ask the user for more info before applying this patch.

[shenoydotme]

@sergobot The user was missing .dateFormat within their config.toml.

[sergobot]

@shenoybr,
Seems quite strange to me, as hugo-goa-demo has the following in its config.toml:

dateFormat = "Jan 2, 2006"

but it didn't work fine before my fix. I have uploaded my screenshots to imgur.

By the way, without the fix hugo v0.17 gives errors like the one I copied to PR. And current master branch of hugo says your templates are incorrect:

ERROR: 2016/11/08 06:46:54 general.go:236: theme/partials/li.html is an incomplete or empty template
ERROR: 2016/11/08 06:46:54 general.go:236: theme/partials/content.html is an incomplete or empty template

[shenoydotme]

Could you tell me which version of Golang you are using? I tested this on both go 1.6, 1.7.1 and hugo v0.16 and v0.17.

The fix you made is incorrect, because it doesn't display the date, and rather displays the string .SITE.PARAMS.DATEFORMAT. The objective is to display the date in the format 'Jan 2, 2006', or other.

Would there be anything else in the config.toml that is missing? I tested hugo-goa-demo on various platforms, it also works on themes.hugo.io as in here.

[sergobot]

@shenoybr
Thank you, now I got it. I didn't notice that .SITE.PARAMS.DATEFORMAT date when making this PR, sorry. But, at least, my fix made hugo-goa-demo working (more on that below).

$ go version
go version go1.7.3 linux/amd64

I have tested hugo-goa-demo with some different hugo versions and here are the results. Really weird results...

Without fix

• hugo v0.16, self-built
  
• hugo v0.17, self-built
  
• hugo v0.18-DEV (master), self-built
  

With fix

• hugo v0.16, self-built
  
• hugo v0.17, self-built
  
• hugo v0.18-DEV (master), self-built
  

The weird thing

Disappointed by these results, I have also tried building the site with pre-compiled hugo from https://github.com/spf13/hugo/releases. Screenshots going below are made without my fix, since the fix doesn't make any difference compared to self-built versions of hugo.

• hugo v0.16, release
  
• hugo v0.17, self-built
  

So, actual explanation seems to be one of
a) Something wrong with my environment
b) Hugo requires some additional flags when built
c) Bug in go 1.7.3 (Not sure, since I didn't try build hugo with 1.7.1, for example)

[sergobot]

Now I have tried building hugo v0.17 with go 1.7.1 and there is no difference

Also, I noticed that Erlich's photo isn't shown when running self-built hugo, and, obviously, is shown when running pre-built hugo.

[shenoydotme]

@sergobot Thank you for this detailed investigation into the issue. I agree that it does look like it might have something to do with self-built hugo or the environment it is running in. I'll try and run it this weekend to understand why it could happen.

[sergobot]

@shenoybr Hi, how is your investigation going?

[sergobot]

Okay, I have fixed it. Check out #10