The existing endpoint will be retired and removed on November 23, 2021. References: - https://twittercommunity.com/t/consolidating-the-oembed-functionality/154690 - https://developer.twitter.com/en/docs/twitter-for-websites/oembed-api#Embedded This is a backward compatible change. The existing endpoint requires a single parameter: the id of the tweet. The new endpoint requires two parameters: the id of the tweet, and the user with whom it is associated. For the moment, if you supply the wrong user, the request will be redirected (with a small delay) to the correct user/id pair. This behavior is undocumented, but we will take advantage of it as Hugo site authors transition to the new syntax. {{< tweet 1453110110599868418 >}} --> works, throws warning, deprecate at some point {{< tweet user="SanDiegoZoo" id="1453110110599868418" >}} --> new syntax Fixes #8130
2.8 KiB
title | linktitle | description | date | categories | menu | keywords | weight | toc | aliases | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Frequently Asked Questions | FAQ | Solutions to some common Hugo problems. | 2018-02-10 |
|
|
|
2 | true |
|
{{% note %}} Note: The answers/solutions presented below are short, and may not be enough to solve your problem. Visit Hugo Discourse and use the search. It that does not help, start a new topic and ask your questions. {{% /note %}}
I can't see my content!
Is your markdown file in draft mode? When testing, run hugo server
with the -D
or --buildDrafts
switch.
Can I set configuration variables via OS environment?
Yes you can! See Configure with Environment Variables.
How do I schedule posts?
- Set
publishDate
in the page Front Matter to a datetime in the future. If you want the creation and publication datetime to be the same, it's also sufficient to only setdate
1. - Build and publish at intervals.
How to automate the "publish at intervals" part depends on your situation:
- If you deploy from your own PC/server, you can automate with Cron or similar.
- If your site is hosted on a service similar to Netlify you can use a service such as ifttt to schedule the updates.
Also see this Twitter thread:
{{< tweet user="ChrisShort" id="962380712027590657" >}}
Can I use the latest Hugo version on Netlify?
Yes you can! Read this.
I get "TOCSS ... this feature is not available in your current Hugo version"
If you process SCSS
or SASS
to CSS
in your Hugo project, you need the Hugo extended
version, or else you may see this error message:
error: failed to transform resource: TOCSS: failed to transform "scss/main.scss" (text/x-scss): this feature is not available in your current Hugo version
We release two set of binaries for technical reasons. The extended version is not what you get by default for some installation methods. On the release page, look for archives with extended
in the name. To build hugo-extended
, use go install --tags extended
To confirm, run hugo version
and look for the word extended
.
-
See Configure Dates for the order in which the different date variables are complemented by each other when not explicitly set. ↩︎