- Some error messages refer to `get_taxonomy_term_by_name` instead of
`get_taxonomy_term`
- If a term cannot be found in a taxonomy, the error message
erroneously pretends that the taxonomy itself is unknown instead of
the term.
* Add feature to disable robots.txt and sitemap.xml from the config file.
Addresses feature request #2248
* Add documentation for no_sitemap & no_robots
* Rename no_robots and no_sitemap into generate_robots_txt and generate_sitemap (default to true)
* fix rustfmt issues
* Change documentation to show defaults
* Update documentation for the fields generate_sitemaps (resp. robots_txt), now that the default is true and false is needed to disable
* Refine YAML date regex
This commit does a few changes:
- Introduce a new regex
- it is a bit off-spec (it allows one-digit months and days in date-only mode)
- uses named groups
- avoids group duplication
- parses offset once
Fixes#2538
* Fix nanosecond parsing
* Rename variables for brewity
* Add tests
* Metainfo: Add 0.19.1
* Metainfo: Fix date for 0.19.0
I entered the wrong date originally.
Fixes 7d612c69db
* Update zola.metainfo.xml
---------
Co-authored-by: Vincent Prouillet <balthek@gmail.com>
For unknown reasons, it seems some environments emit a `DataChange::Any` event,
rather than specifying content or size, when a file is edited. As an example:
[src/fs_utils.rs:72:9] &event = DebouncedEvent {
event: Event {
kind: Modify(
Data(
Any,
),
),
paths: [
"/home/redacted/content/blog/2024-06-23_example.md",
],
attr:tracker: None,
attr:flag: None,
attr:info: None,
attr:source: None,
},
time: Instant {
tv_sec: 78544,
tv_nsec: 936740729,
},
}
Consequently, because this isn't treated by Zola as a modification, the
site is not rebuilt, which regresses on previous behavior.
This patch fixes this particular case by treating any data modification
events as a modification.
Closes: https://github.com/getzola/zola/issues/2536
Otherwise appstream-compose fails on this:
Running: appstreamcli compose --no-partial-urls --prefix=/ --origin=org.getzola.zola --media-baseurl=https://dl.flathub.org/media --media-dir=/srv/buildbot/worker/build-x86_64/build/.flatpak-builder/rofiles/rofiles-6Fx4YU/files/share/app-info/media --result-root=/srv/buildbot/worker/build-x86_64/build/.flatpak-builder/rofiles/rofiles-6Fx4YU/files --data-dir=/srv/buildbot/worker/build-x86_64/build/.flatpak-builder/rofiles/rofiles-6Fx4YU/files/share/app-info/xmls --icons-dir=/srv/buildbot/worker/build-x86_64/build/.flatpak-builder/rofiles/rofiles-6Fx4YU/files/share/app-info/icons/flatpak '--components=org.getzola.zola,org.getzola.zola.desktop' /srv/buildbot/worker/build-x86_64/build/.flatpak-builder/rofiles/rofiles-6Fx4YU/files
Only accepting components: org.getzola.zola, org.getzola.zola.desktop
Processing directory: /srv/buildbot/worker/build-x86_64/build/.flatpak-builder/rofiles/rofiles-6Fx4YU/files
Composing metadata...
Run failed, some data was ignored.
Errors were raised during this compose run:
org.getzola.zola
E: no-stock-icon
And we don't really need an icon since Zola is a CLI app.
