Ref shortcodes to taxonomy pages now throwing "REF_NOT_FOUND" after Hugo update

support
, ,
1

EDIT: For some reason, Hugo is no longer rendering pages with their correct template. It seems that something has changed with case sensitivity?

I recently updated Hugo to 0.123.7[1] and now several of my shortcode ref taxonomy-name commands are throwing “REF_NOT_FOUND” errors when I try to launch hugo server. I haven’t run the server in maybe one or two Hugo updates. What changed? And what do I need to change in my code? Does this have something to do with the difference between a page’s path and logic (whatever that means)? In my case, the “taxonomy-name” refers to a neighborhood, e.g., “hochelaga” (Hochelaga | MTL Electronic Music)

EDIT: I figured out a solution: I had to prefix the ref name with its hyper-taxonomy. For example, I had to write ref "hoods/hochelaga". Before, I didn’t have to include “hoods” but now I do—why?

EDIT2: Something with the taxonomies or code of Hugo has changed significantly, as now when I successfully get hugo server to run, my site is nearly broken. All the stuff that used to work great, no longer does. My theme’s single and list pages are no longer rendering for some of my content (e.g., /Artists).

I have no idea what happened here…

  1. I find this numbering scheme to be unusual. Did this change at some point to? It gives the impression that Hugo hasn’t hit a 1.0 release, but I guess I’m just out of the loop on version numbering schemes. ↩︎

2

Please post a link to the public repository for your project.

See Requesting Help.

Let us see your code

Include a link to the source code repository of your project, because we really need the context of seeing your templates and partials to be able to help you. It is trivial to do a quick git clone on your repo, then run hugo server in your project, to help you out. On the other hand, recreating your code from screenshots, or sort of guessing at it, is not.

If you can’t share your repository for whatever reason, consider creating a dummy repo that you can share, which reproduces the problem you’re experiencing.

3

I’ve changed Artists to artists… there seems to have been a change in how Hugo deals with case?

Now I am having a more challenging problem getting the site deployed on Netlify. It throws errors when it try to render the artist single page. I’m not really sure what’s going on. Thank you for any help you might be able to provide me.

1 Like
4

I haven’t looked at your repo yet, but there was an intentional breaking change in v0.123.0 that affects, in some cases, how one accesses page resources and content (including taxonomy and term pages).

Hugo v0.123.0 introduced the concept of a logical path:

A page or page resource identifier derived from the file path, excluding its extension and language identifier. This value is neither a file path nor a URL. Starting with a file path relative to the content directory, Hugo determines the logical path by stripping the file extension and language identifier, converting to lower case, then replacing spaces with hyphens. See examples.

Let me have a look at your site, and I should be able to explain (a) why didn’t work before 9bd04cf154b289de0ece1fdc44c08854048c1a77, and (b) why Netlify is having a problem and how to fix it.

5

Thank you kindly! I greatly appreciate your help.

I will look into the implications of the logical path. This change seems to be pretty major alteration in how Hugo works, at least for my site… I guess it brings some advantages that I don’t yet know about.

6

Oh yeah. The change was technically necessary to make lots of other things possible: user roles, pages from data, partial rebuilds based on section, etc.

I’m sorry we temporarily broke your site, but the required changes on your site should be minor.

7

I understand. I really do appreciate any help you might be able to offer me! Your support is very laudable.

8

I was able to deploy your site to Netlify at https://main--mtlelectronicmusic.netlify.app/. I will remove this after we’ve settled this.

What I did with your repository:

1) Updated the site configuration (the number of processed images was causing a timeout with the default value)

timeout = '600s'

2) Updated the .gitignore file

.DS_Store
.hugo_build.lock
_In_Process
public/

3) Removed the public directory from the repository

git rm -rf public

4) Refreshed the cache

rm -rf resources
hugo

5) Commited the changes and pushed

Netlify build log 
9:31:48 AM: Netlify Build                                                 
9:31:48 AM: ────────────────────────────────────────────────────────────────
9:31:48 AM: ​
9:31:48 AM: ❯ Version
9:31:48 AM:   @netlify/build 29.36.0
9:31:48 AM: ​
9:31:48 AM: ❯ Flags
9:31:48 AM:   baseRelDir: true
9:31:48 AM:   buildId: 65e756cec2449c39a4b2d4bf
9:31:48 AM:   deployId: 65e756cec2449c39a4b2d4c1
9:31:48 AM: ​
9:31:48 AM: ❯ Current directory
9:31:48 AM:   /opt/build/repo
9:31:48 AM: ​
9:31:48 AM: ❯ Config file
9:31:48 AM:   /opt/build/repo/netlify.toml
9:31:48 AM: ​
9:31:48 AM: ❯ Context
9:31:48 AM:   production
9:31:48 AM: ​
9:31:48 AM: build.command from netlify.toml                               
9:31:48 AM: ────────────────────────────────────────────────────────────────
9:31:48 AM: ​
9:31:48 AM: $ hugo --gc
9:31:48 AM: Start building sites …
9:31:48 AM: hugo v0.123.7-312735366b20d64bd61bff8627f593749f86c964+extended linux/amd64 BuildDate=2024-03-01T16:16:06Z VendorInfo=gohugoio
9:31:49 AM:                    |  EN
9:31:49 AM: -------------------+-------
9:31:49 AM:   Pages            |  510
9:31:49 AM:   Paginator pages  |    0
9:31:49 AM:   Non-page files   |  541
9:31:49 AM:   Static files     |   45
9:31:49 AM:   Processed images | 1072
9:31:49 AM:   Aliases          |    0
9:31:49 AM:   Cleaned          |    0
9:31:49 AM: Total in 1102 ms
9:31:49 AM: ​
9:31:49 AM: (build.command completed in 1.1s)
9:31:49 AM: ​
9:31:55 AM: (Netlify Build completed in 7.3s)
9:32:18 AM: Section completed: building
9:32:47 AM: Finished processing build request in 1m41.735s
Deploying

My (updated) copy of your repository:
https://github.com/jmooring/mtlelectronicmusic/

9

Excellent. Thank you @jmooring ! These changes fixed it on my side and I have pushed the relevant changes. You have restored my site and can safely delete the cloned rep. I’m seriously impressed with how fast this got resolved—thank you.

1 Like
10

Netlify test site and my copy of the repo deleted.

1 Like
11

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.