Age | Commit message (Collapse) | Author |
|
Fixes #2509
|
|
Fix #2503
|
|
Fixes #2498
|
|
By making the err chan buffered so both go routines can return.
Also make sure that any errors are logged.
Fixes #2488
|
|
Fixes #2485
|
|
|
|
|
|
Fixes #2458
|
|
There were some breaking changes etc. that is too late to fix for 0.17.
Let us think this through and add proper author support for Hugo 0.18.
Fixes #2464
Revert "docs: Add documentation for author profiles"
This reverts commit b6673e5309685ae162fdef2dc39c3ce4385c6005.
Revert "Add First Class Author Support"
This reverts commit cf978c06496d99e76b08418422dda5797d90fed6.
|
|
|
|
We may add it again in the future, but let us try to keep the API as small as possible for now.
See #1850
|
|
Closes #1850
|
|
Fixes #2451
|
|
Fixes #2449
|
|
Fixes #2450
|
|
This avoids having to execute these expensive operations for sites not using these values.
This commit sums up a set of wordcounting and autosummary related performance improvements.
The effect of these kind of depends on what features your site use, but a benchmark from 4 Hugo sites in the wild shows promise:
```
benchmark old ns/op new ns/op delta
BenchmarkHugo-4 21293005843 20032857342 -5.92%
benchmark old allocs new allocs delta
BenchmarkHugo-4 65290922 65186032 -0.16%
benchmark old bytes new bytes delta
BenchmarkHugo-4 9771213416 9681866464 -0.91%
```
Closes #2378
|
|
It is obviously more efficient when we do not care about the actual words.
```
BenchmarkTotalWords-4 100000 18795 ns/op 0 B/op 0 allocs/op
BenchmarkTotalWordsOld-4 30000 46751 ns/op 6400 B/op 1 allocs/op
```
|
|
For people using autogenerated summaries, this is one of the hot spots in the memory department.
We don't need to split al the content into words to do proper summary truncation.
This is obviously more effective:
```
BenchmarkTestTruncateWordsToWholeSentence-4 300000 4720 ns/op 0 B/op 0 allocs/op
BenchmarkTestTruncateWordsToWholeSentenceOld-4 100000 17699 ns/op 3072 B/op 3 allocs/op
```
|
|
Fixes #2435
|
|
Fixes #2434
|
|
|
|
Fixes #2430
|
|
Hugo 0.16 announced support for symbolic links for the root folders, /content, /static etc., but this got broken pretty fast.
The main problem this commit tries to solve is the matching of file change events to "what changed".
An example:
ContentDir: /mysites/site/content where /mysites/site/content is a symlink to /mycontent
/mycontent:
/mypost1.md
/post/mypost2.md
* A change to mypost1.md (on OS X) will trigger a file change event with name "/mycontent/mypost1.md"
* A change to mypost2.md gives event with name "/mysites/site/content/mypost2.md"
The first change will not trigger a correct update of Hugo before this commit. This commit fixes this by doing a two-step check:
1. Check if "/mysites/site/content/mypost2.md" is within /mysites/site/content
2. Check if "/mysites/site/content/mypost2.md" is within the real path that /mysites/site/content points to
Fixes #2265
Closes #2273
|
|
|
|
Fixes #2422
|
|
Atomic operations with 64 bit values must be aligned for 64-bit on x86-32.
According to the spec:
"The first word in a global variable or in an allocated struct or slice can be relied upon to be 64-bit aligned."
The above wasn't enough for the `paginationPageCount` on `SiteInfo`, maybe due to how `SiteInfo` is embedded.
This commit adds a 4 byte padding before the `uint64` that creates the correct alignment.
Fixes #2415
|
|
This is the nth attempt to fix an issue by changing the placeholder token pattern, but
now we actually have tests for all the historic trouble cases.
Fixes #2223
|
|
Updates #2415
|
|
Also improve the error message on missing resource bundles.
|
|
|
|
Updates #2309
|
|
Updates #2309
|
|
Updates #2309
|
|
This commit also refines the partial rebuild logic, to make sure we do not do more work than needed.
Updates #2309
|
|
We should get rid of these globals, but that is another month.
|
|
After a visual inspection to make (pretty) sure it is correct re multiple languages.
Updates #2309
|
|
So the Permalink gets correct when listing translations.
I have also checked the other relevant places to make sure we do not overwrite node values we need later.
Pointers can be tricky, but lesson learned is: A copy is cheap.
Updates #2309
|
|
Updates #2309
|
|
Updates #2309
|
|
And some other minor fixes from code review.
Updates #2309
|
|
Updates #2309
|
|
In a multi-language setup, before this commit the Node's Translations() method
would return some "dummy nodes" that would point to the correct page (Permalink),
but would not be the same as the node it points to -- it would not have the translated
title etc.
The node creation is, however, so mingled with rendering, whihc is too early to have any global state,
so the nodes has to be split in a prepare and a render phase. This commits does that with as small
a change as possible. This implementation is a temp solution until we fix #2297.
Updates #2309
|
|
Makes the templates simpler.
See #2309
|
|
See #2312
|
|
Fixes #2312
|
|
And pull up common member vars like Tmpl and Multilinguage.
Or: the final multilingual TODO-fixes.
See #2309
|
|
Or: some more multilingual TODO-fixes.
See #2309
|
|
See #2309
|
|
See #2309
|
|
And clean up the test.
See #2309
|