-
Notifications
You must be signed in to change notification settings - Fork 107
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
exampleSite content references non existent tweet #8
Comments
This will fix the theme's demo. Also see: bjacquemet/personal-web#8
Hi @onedrawingperday |
Right. So this ERROR is due to recent Hugo updates. The external demo is generated with Your theme's demo has been broken since last October. Hugo 0.59.0 introduced support for typed bool, int and float values in shortcode params. Also see: gohugoio/hugo#6376 Upon closer inspection the request generated by the tweet shortcode that is used in your theme points to a non-existent URL:
This part in particular: - %!s(int=1120412132036706305) - The tweet ID is outputted as an int due to the way that the tweet-single parameter is entered ie. To fix the ERROR you will need to either change the shortcode input so that the tweet ID is a string by wrapping it in quotes like so: OR I think it is preferable to do this directly within the shortcode by changing line 6 of
Once you issue a fix feel free to close this issue. |
Thanks a lot. Fixed in the last commit |
Hello @bjacquemet
I am one of the maintainers of Hugo Themes.
There is a reference to a non existent tweet in the content files of your theme's exampleSite.
This results in a broken demo on the Hugo Themes website.
I tried to make your theme inherit its content from the hugoBasicExample repo, so that the demo generates.
However this resulted in an empty homepage since your theme has a custom portfolio section and even though you are using Hugo's internal
mainSections
you have hardcoded the section whose content is displayed on the index page.To fix the demo you need to remove the reference to the non-existent tweet.
Also note that as stated in the Hugo Themes README:
The text was updated successfully, but these errors were encountered: