I’m using Hugo v0.49.2/extended darwin/amd64 BuildDate: unknown.
I have some problem on my tag setting. I’m writing hugo blog for my Japanese blog.
On local, hugo server, every single tag page showing correctly. But once I published, some of my Japanese tags returned 404 pages. Not all Japanese, but a few of them. I compared generated html by hugo, but it looks like completely same except url decoding part.
To solve this problem. which part should I start from?
Odd, are you seeing this same 404 phenomenon for other katakana tags? Conversely, are all the hiragana tags working? Is there a difference adding the trailing slash, or not?
Can you try deleting all the content on your server once and re-uploading? I had a problem like this before, where I was using rsync to upload, but I did not have it set to overwrite.
ok, can you make a github gist, include some of your files and share it? I want to see your config file, and the relevant templates. It’s hard to help if we cannot see what is actually going on.
Ok, one thing I noticed - in your config, you have baseurl but, in the docs it mentions baseURL. It’s best to err on the side of caution and spell it exactly like you see in the docs. I can’t say if this is just superstition or not, but it could have an impact.
First, I tried changing to baseURL, but nothing changed.
Second, draft was not set.
Third, I was not able to find any error with --verbose. Only I can see was some warn.
WARN 2018/10/29 08:34:37 No translation bundle found for default language “en”
WARN 2018/10/29 08:34:37 Translation func for language en not found, use default.
WARN 2018/10/29 08:34:37 i18n not initialized, check that you have language file (in i18n) that matches the site language or the default language.
I guess this is nothing to do with tags problem.
Only the cause of this tags problem came up to my mind through trouble shooting this time is “hugo version”. I updated hugo version before from 0.2x to 0.4x. I guess this cause problem. So I’ll compare the content file before updating and after updating.
Anyway, I appreciate this community:D
After comparing the content files, I’ll post update.
Thanks again.
Yeah, maybe so. A lot has happened from then to now. The Icarus theme might also be out of date in some respect - you might check with its author.
If you can’t make a repo, then you could zip up all your project files, and copy the zip to static in your project, and republish. That way, someone could download your zip, unzip, and run Hugo on the folder to test.
Hmm. For regular software you can get install history by option-clicking the apple menu, then going to Software, then picking Information. But for homebrew, it appears there’s no easy way to find the update history (hope i’m wrong). You might poke around in /usr/local/Cellar with ls to see if you can see any dates…
Great, I found it.
But by comparing two content files before updated and after updated. I can not find any difference.
I’ll contact theme creator next.
Could it be something about how you’re uploading? Assuming you can find the index file for the アンチパターン tag or other 404-ing tags, in public after you run hugo to generate, can you get a verbose log from whatever it is you’re using to upload? Maybe it is hanging on certain tags, for some reason…