-
Notifications
You must be signed in to change notification settings - Fork 602
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
Comments
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. |
I also experienced a similar problem. Although there was no problem when using version 0.19, I think this error has occurred due to the following change in version 0.20. |
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. |
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"
The text was updated successfully, but these errors were encountered: