Skip to content
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

error calling isset: unsupported type "invalid" #32

Closed
2Dou opened this issue Mar 14, 2017 · 3 comments
Closed

error calling isset: unsupported type "invalid" #32

2Dou opened this issue Mar 14, 2017 · 3 comments
Labels

Comments

@2Dou
Copy link

2Dou commented Mar 14, 2017

ERROR 2017/03/14 16:06:38 theme/partials/head.html template: theme/partials/head.html:56:13: executing "theme/partials/head.html" at <isset .Params.bigimg...>: error calling isset: unsupported type "invalid"
ERROR 2017/03/14 16:06:38 theme/partials/header_wp.html template: theme/partials/header_wp.html:13:8: executing "theme/partials/header_wp.html" at <isset $bigimg 0>: error calling isset: unsupported type "invalid"

@2Dou 2Dou closed this as completed Mar 14, 2017
@2Dou 2Dou reopened this Mar 14, 2017
@halogenica
Copy link
Owner

Can you please explain this? What did you do that caused this? How can I reproduce it? to me it looks like it could have been caused by setting an invalid image name in the config.toml file. Can you delete all the [[Params.bigimg]] fields and tell me if the problem still occurs? The bigimg's seem to work correctly on the example website as-is.

@tamanugi
Copy link

I also experienced a similar problem.

Although there was no problem when using version 0.19,
A similar error occurred when version 0.20dev was used.

I think this error has occurred due to the following change in version 0.20.
gohugoio/hugo#3092

@halogenica halogenica reopened this Mar 19, 2017
@halogenica halogenica added the bug label Mar 28, 2017
@halogenica
Copy link
Owner

I think this is fixed now. Please feel free to give it a shot and let me know if it's not fixed. I tested with 0.20. I was looking for the particular change that I thought would have fixed it (I made it a while ago but couldn't test for sure because I wasn't able to reproduce the error at the time); but I couldn't find the exact commit that fixed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants