Now, when I add new post with a date hugo new content/en/post/2025-01-27-postgresql-unknown-type-during-database-restore-p2/index.md I don’t see it it latest posts page, but all older posts are displayed.
So by experimenting, I found out, that pages with date in filename or in front matter are not labeled as section=post, but if I remove date the section is assigned and I see post, but with wrong date.
И дальше контент на стандартном языке будет обычным названием content/post.md и в той же папке перевод будет content/post.de.md
а на сайте site.com/post/ - на английском, site.com/de/post/ - на немецком.
Мне кажется такой подход удобнее, не придется держать 2 структуры файлов под разные языки…
Возможно, еще кеш не обновился попробуйте запускать так
hugo server --disableFastRender
Hello!) For multiple languages, I use this setup in hugo.toml, configured according to the documentation from here Multilingual mode
And the content in the default language will have a regular name content/post.md and the translation will be in the same folder as content/post.de.md On the site, site.com/post/ will be in English, site.com/de/post/ will be in German.
I think this approach is more convenient, you don’t have to keep two file structures for different languages…
Maybe the cache hasn’t been updated yet, try running it like this
translation by filename or folder structure are both convenient. It just depends on personal preference. I would not consider that as part of a solution here.
I suppose your frontmatter is empty for the newly created site, try to use --kind post which at least for the core theme will bring up a valid frontmatter and list the page.
hugo new --kind post content/en/post/2025-01-27-postgresql-unknown-type-during-database-restore-p2/index.md
havent checked in detail, but there’s a rather old issue about that archetype stuff which is still open… (may have been fixed, but as I
BUT: the theme originally has no multilanguge setup and your code is not contained in the theme - so it’s custom to your setup - with maybe more things.
it does not make much sense to try to replicate your setup, so you’ll have to share your repo.
p.s. i tested with the example site, so without multilang - ther’s a rather old issue #5233 in github.
i don’t consider that as part of your problem but
your config file .toml is malformed. Toplevel single entries have to be before the first array value when using TOML.
there are some of that, that will just be appended to the last open array.
example one enableRobotsTXT = true (there are others) check this with hugo config and see where it ends
if you use this theme https://github.com/Tazeg/hugo-blog-jeffprod.git
yes - that’s what I got when cloning your repo - I just said that this ios NOT a fork from somewhere else that is updated my a third person, but an older fork of the original theme updated BY you to match your needs.
regarding Hugo it’s still outdated (won’t compile with recent hugo
please post the rsult of hugo version so I test with the same version than yours.
I don’t understand, what you are trying to tell me. looks like we both non-native speakers have a problem here. maybe don’t write that short and/or visualize things.
with this frontmatter your page in question is shown on the second paginated page on your English site including tags. And it displays in the Archives for 2024:
---
layout: post
title: PostgreSQL. Fixing "type does not exist" error during restoring database.
draft: false
archives: "2024"
tags: [gcp, certification]
tocEnabled: false
---
they all had the archives param
and number of posts was less than page size.
btw. if there is no special requirement you could also collect the containers by .Date or filename or folder from permalink. no need to have a param here
