mirror of
https://github.com/gohugoio/hugo.git
synced 2024-11-14 20:37:55 -05:00
d2b1030060
0fd7b4169 Fix typo: pygmentsUseClasses -> pygmentsUseClassic 9a3e1c19a Clarify that lower weight gets higher precedence 820d8b581 Clarify the true behavior of hrefTargetBlank #blackfriday eb3aa5e46 Fix typo 9aedb9269 Add examples for removing default taxonomies 772a26f84 Fix source link on maintainance 975c215ae Minor edits. 2bdb1a150 Fix invalid iink 991d2e139 Fix misspelling 60af8dfb0 Update eSolia link d7426b76e Release 0.40.3 4977bd9cf Merge branch 'release-0.40.3' 9946f7108 releaser: Prepare repository for 0.41-DEV beef16b01 releaser: Add release notes to /docs for release of 0.40.3 80c51c55a releaser: Bump versions for release of 0.40.3 21e2934c5 rename `taxonomies.html` to `taxonomy.html` 34a02c289 Add release notes from Hugo 0.7 to 0.15 for completeness b593f512e Update related.md 7c2bf528b Fix the "edit this page" link e8fbc163e Add warning about cond ae15a8831 Add link to Markdown Guide e077dfd65 Added documentation for a new migration tool: BlogMl2Hugo 957bfb6a8 Add Talkayrd, a new commenting system, & fix txtpen link 86acea7f8 Tomango showcase 3c2fc32f1 Fix snap classic command in installing.md 9a76f1737 Merge commit '83bef6955e014d40c0f00db9cebe09113154e999' a4b71fb84 Fix typo git-subtree-dir: docs git-subtree-split: 0fd7b416997bf76cd99e3ae2dfae406cb8b6724a
12 lines
683 B
Markdown
12 lines
683 B
Markdown
|
|
---
|
|
date: 2018-05-09
|
|
title: "Hugo 0.40.3: One Bug Fix"
|
|
description: "Fixes a rare, but possible Content truncation issue."
|
|
categories: ["Releases"]
|
|
images:
|
|
- images/blog/hugo-bug-poster.png
|
|
|
|
---
|
|
|
|
Hugo `0.40.3` fixes a possible `.Content` truncation issue introduced in `0.40.1` [90d0d830](https://github.com/gohugoio/hugo/commit/90d0d83097a20a3f521ffc1f5a54a2fbfaf14ce2) [@bep](https://github.com/bep) [#4706](https://github.com/gohugoio/hugo/issues/4706). This should be very rare. It has been reported by only one user on a synthetic site. We have tested a number of big sites that does not show this problem with `0.40.2`, but this is serious enough to warrant a patch release.
|