.Page.Scratch not reset on re-render of different page

support
1

I am using the ‘hugo-notice’ shortcode to render a ‘notice’ admonition. This shortcode uses .Page.Scratch to include the required CSS only on the first instance per page. It checks if a special variable is set in .Page.Scratch. If not, it renders the CSS and sets the variable.

I noticed that when running in server mode and I change a different page, the shortcode is re-rendered, but the .Page.Scratch is not reset, so the CSS is not included (and so the notice appears unstyled). However, if I modify the current page, it clears the .Page.Scratch and re-renders the shortcode correctly.

Is this the correct behavior of .Page.Scratch? Is there a way to have a scratchpad that will be reset when the page is rebuilt (even if it is another file that is modified)?

(Edit: I also tried with .Page.Store and it has the same behavior)

2

cc @martignoni

2 Likes
3

I don’t know enough about .Page.Scratch to answer the question directly, but perhaps it’s possible to do without it in the shortcode. I’ll see what’s possible as soon as I have time :slight_smile:

If anyone has any suggestions, please let us know.

See Get rid of `scratch` · Issue #47 · martignoni/hugo-notice · GitHub

4

Try this also Hugo-admonitions: A simple way to add beautiful Callouts to hugo site

5

I could not reproduce your issue.

Anyway, I’ve replaced $.Page.Scratch with .Page.Store in Hugo Notice. Hopefully, it will fix your issue.

6

store or scratch should not make a difference these days. would have to search for the exact version where they have been merged

in fact for me it’s a litte unclear how to reproduce with these differnt edits…

maybe some other things like list pages partials… play a role

a replayable example repo might help

1 Like
7

Hi everyone, thanks for the responses. There is no difference for me between Scratch and Store. When creating a reproducer, I noticed that this looks like it is an interaction between hugo-book and hugo-notice.

Here is a minimal reproducer: GitHub - pazner/hugo-notice-problem

To reproduce the problem:

  1. Run hugo serve
  2. Open the main page (index.md) in the browser
  3. Edit and save the second page (page.md), causing a rebuild of the site
  4. At this point, the CSS for the notice should be gone from the first page
8

I would start by raising an issue with the author of the hugo-book theme, because I can reproduce the problem using their “mermaid” and “katex” shortcodes, both of which use a similar mechanism to include js/css.

1 Like
9

The problem is triggered by this:
https://github.com/pazner/hugo-notice-problem/blob/master/hugo.toml#L8

1 Like
10

Yeah, it looks like it’s hugo-book specific rather than hugo-notice. I created an issue there: Shortcode CSS doesn't load on refresh · Issue #700 · alex-shpak/hugo-book · GitHub

11

As others already pointed out, the behavior of the scratchpad has been altered to be this way, so yes, it is working as intended (unfortunately IMHO).

There is an open feature request to add the ability to detect when a page is being rebuild. This way one could achieve the old behavior with some custom logic.