Gap in design from 0.145 to 0.146.3

support
1

hi,
4 days ago, my website desgn was ok in 0.145, no it is a mess in 0.146.3 , mainly the index.html (homepage) page with a homepage.yml file

  • Can you please explain us what exactly has been changes to correct our templates ?
  • can we limit the built to a specific version (here 0.145)? in order to have the time in production to test and remake the design ?

in layout, my index.html is :

{{ define "main" }}

  {{- partial "banner.html" . }}

  {{- partial "features.html" . }}

  {{- partial "promo.html" . }}

  {{- partial "about-product.html" . }}

  {{- partial "products.html" . }}

  {{- partial "subscription.html" . }}

  {{- partial "testimonials.html" . }}

{{ end }}

I think that causes the new problem in 0.146.3

2

Are you auto-updating the version when you build your site? Please explain.

3

yes in linux , with snap, the upgrade has been for 2 years in auto
I do not care: I just type “hugo server” and the new version is loaded and starts

4

this is in dev station, but when I deploy on Render, I do not know what will append !

5

before :

Capture d’écran_2025-04-14_17-32-11
Capture d’écran_2025-04-14_17-32-111485×597 458 KB

after (0.146.3):

Capture d’écran_2025-04-14_17-32-32
Capture d’écran_2025-04-14_17-32-321412×562 112 KB

6

render.com does not allow you to easily specify the version to use when building your site. That’s a huge problem. If I were you I would use a different provider.

But if you really want to use render.com, read through this thread:
https://community.render.com/t/how-to-define-hugo-version/390/7

If you need additional support configuring render.com, use their forum.

For your local version, since you have not pinned the snap to a specific version, uninstall the snap then install one of the pre-built binaries.

If you want help modifying your site to be compatible with v0.146.0 and later, please post a link to the public repository for your site.

1 Like
7

That looks kind of like raw HTML to me, also known as, issues bringing in assets like css files and images.

It would be helpful to right click and then click view source, compare both versions. I’d concentrate on the src and href attributes of your assets.

When using third-party renderers, sometimes the assets get mixed up. Had it happen with my sites using Github Pages and such. I’ve had tons better luck with rendering it on my own computer, then just rsyncing it to the webhost.

8

To clarify, the OP can’t update their site to be compatible with v0.164.0 or later because render.com uses an earlier Hugo version, and they don’t provide a simple way to use any version.

1 Like
9

Hi, (I do not understand “OP” , and 0.164 version)

I removed Hugo snap version and installed pre-built binaries of v 0.145 : all works well .
So the cause is the new version (snap was still on 0.146.3)
my site is not on a public repo and has a tailwind css , but yes I can give you a collaborator access @jmooring ( Productivix site-prx-hugo ) i made a special branch named “0.146” - thanks

10

OP is an acronym for Original Poster, for example: the person who started a thread.

Snaps automatically update a few times a day. Which can be a good or bad thing, I guess a bad thing in your case, at least for this one instance.

I think jmooring may have had a typo, and switched the 6 and 4 around. It is the 146 version(s).

There was a bit of a rough spot in the releases lately, as can happen for any software package. 146.0 was the primary release. 146.1-4 was mainly to correct some of the issues with layout lookups, there may have/be other issues about too.

render dot com maybe waiting for code contributors to ride out some of the issues in the release before migrating to 146. Either way, it’ll likely be more time efficient for you to match their version instead of trying to upgrade it on their end.

11

hi, thks for explanations. I develop on React JS / Native and for that I prefer to master the versions I have in dev and prod . No I will not go over the Render version and push mine .

The problem I mention is only on index page, not on the others that have more simple templates.

The main thing is that we do not have any error messages at all to help to point out the difference.

12

test with v 146.4 : still the same website broken on index page .(picture of “after (0.146.3)”), no error message

13

thanks for your help all , with some commands , I have been able to switch from 0.145 and 0.146.4 : and I found that a file home.html under theme/layout/default was unused and putting the mess in 0.146 (and not in 0.145) .

14

Good to know.

I think the lookup order of templates changed a bit in 0.146.x.

One of the things I wish there was (unless I’m just not finding it in Docs) was a field that could be put in baseof to print out what template a page is using. Would be very helpful in diagnosing issues like this.

15

hi , yes would it be good, because I had index.html also and never know which one was useful (at beginning when I was unable to understand the code) .

16

Well… a page most likely uses many templates, for example:

layouts/baseof.html -> layouts/home.html -> layouts/_partials/footer.html -> etc.

You are probably interested in either template boundaries (enter/leave) or the template call stack. You can do both with the new templates.Current function. See examples.

17

hi , thank you @jmooring !
this is new in v0.146 , may be useful yes .

18

I played around with it some. It’s more useful to put it in the actual template files you’re trying to identify vs using it to figure out which templates are in the chain of each page.

Maybe a command line switch or build flag to list each page generated and its template chain would work better for this sort of thing. I may look at Hugo’s code, maybe it’s something I can figure out and contribute. But, at least currently, I’m more familiar with Python than Go.

19

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