Build Process failure related to GoogleAnalytics.AnonymizeIP config

[Aman-Aalam]

Hi Folks,

I am using the Hinode theme to power a developer blog and I have recently started hitting an error, perhaps because of a hugo upgrade:

stacktrace:

execute of template failed: template: partials/footer/scripts.html:42:18: 
executing "partials/footer/scripts.html" at <$js.Content>: error calling Content: EXECUTE-AS-TEMPLATE: 
failed to transform "/js/main.bundle.js" (text/javascript): 
template: /js/main.bundle.js:43:67: 
executing "/js/main.bundle.js" at <$pc.AnonymizeIP>: can't evaluate field AnonymizeIP in type privacy.GoogleAnalytics

This tells me the build process is not able to resolve the anonymizeIP values from config files, and that js.Content is failing as well.

Here's the section of my hugo.toml which mentions Google Analytics options:

[privacy]
  [privacy.googleAnalytics]
    disabled = 'false'
    respectDoNotTrack = 'true'
    anonymizeIP = 'true'
    useSessionStorage = 'true'

Any idea what I am missing, please?

Hinode version: v0.22.5
Hugo version: hugo v0.134.2+extended darwin/arm64 BuildDate=2024-09-10T10:46:33Z VendorInfo=brew

[markdumay]

Try upgrading your Hinode version. This issue has been fixed in Hinode v0.23.8, see #882.

[Aman-Aalam]

Thank you, updating it resolved this specific issue, but now when I am on hinode v0.27.12 and hugo v0.139.4 I get the following a bunch of errors all related to $base-url variable, and a warning:

WARN  Unsupported module parameter: core

ERROR "hugo_cache/modules/filecache/modules/pkg/mod/github.com
/gethinode/hinode@v0.27.12/assets/scss/common/_variables.scss:8:33": 
Undefined variable: "$base-url".

Error: error copying static files: open ..../public/fonts/fa-solid-900.ttf: permission denied

Is this the baseUrl defined in hugo.toml ?
I have a _default and a production version of hugo.toml, the default one doesn't have baseUrl defined.

Here's the structure of my config directory:

config
├── _default
│   ├── hugo.toml
│   ├── languages.toml
│   ├── menus
│   │   └── menus.en.toml
│   └── params.toml
└── production
    └── hugo.toml

Along with that's, here's how [modules] are defined in params.toml that I am also getting the warning about:

    [modules]
        core = ["bootstrap", "flexsearch", "fontawesome"]

Any help on what might be going on here, please?

[Aman-Aalam]

@anoduck Thanks a lot!

I made sure I have baseURL defined in default and production both, but the error with $base-url still exists:

ERROR "hugo_cache/modules/filecache/modules/pkg/mod/github.com
/gethinode/hinode@v0.27.12/assets/scss/common/_variables.scss:8:33": 
Undefined variable: "$base-url".

config/_default/hugo.toml

baseURL = "/"

config/production/hugo.toml

baseURL = "/blog/"

[Aman-Aalam]

I think I have stumbled upon the root cause of this issue.

I was looking at when $base-url was introduced and found this commit

It showed me that the variable $base-url was being set by different layout files, and I had overridden those files in my setup, and in my version the $base-url variable was not being set.

I think if I updated my layout files to their latest versions and then made my changes, this will resolve.

Thanks a lot, @anoduck

[anoduck]

@Aman-Aalam AH! That makes sense... I knew you would tinker around and eventually find the answer. Glad you got it going.

You can @mention me anytime, I am no @markdumay, not even close. But, the Open Source community has helped me so much through the years, it is good to give back what little I can.

[markdumay]

Thanks for your support @anoduck! And I agree with your comment about the open source community.

@Aman-Aalam, in general I would advise to use the Hinode template as a starting point for your site. It abstracts away many of the implementation details and will greatly simplify (future) Hinode upgrades. It's a strategy I use for my own Hinode-powered sites too, which seems to pay off so far. But off course, you're free to use the theme in any way you want. ;-)

[Aman-Aalam]

@markdumay I totally agree. I just had to apply some branding elements that the default theme didn't support via configuration, hence the issues :)

[Aman-Aalam]

Sorry for the buzz @markdumay , would you know what's going on here?