hugo scaffolding inconsistent with theme

[jonsgreene]

When publishing to the /docs directory there is an inconsitency in files changed.

To recreate:

• Add a markdown file in content directory
• Run hugo command
• Files changed in /docs director
• Commit changes
• Run hugo again
• Git shows new changes

Visually the navigation menu breaks when clicking through your folders and files.
I have to run hugo many times and recheck the menu by clicking each link and making sure the menu doesn't collapse.

I expect that when I run the hugo command for it to publish to the docs directory all files would be updated on one run. It seems like some files are missed. I have to run the hugo command about 3-4 times and then check the files structure locally before commiting.

Not sure if others are experiencing this issue. Can't tell if it is a theme issue or a hugo issue

[divinerites]

May be you can use Chrome in dev mode and do "reset all and relaod". Often the is some cache (css and al) involved

[Pilskalns]

Hi @jonsgreene,

Probably I can repeat it too. Can you let know exactly what version Hugo are you using?

And what is your dockdock theme version (checkout last commit)? Is it latest-latest?

[jonsgreene]

@Pilskalns Hugo version v0.49.2, docDock is the latest as well. @divinerites That may fix the navigation issue via chrome, but doesn't fix the git changes I see when running the hugo command again. I expect that if I commit my changes and run the hugo command that I should not see any files changed. It should look just like the remote. Sometimes I run the command and see 5 files changes, other times i'll see 3 files changed. So it seems like something that generates the files in the /docs folder is not making it all the way down the tree the first time.

[Pilskalns]

Hi @jonsgreene,

Currently, only unwanted behavior what can I repeat is if children shortcode is used on root _index.md file. If it is on sub-pages, then everything works correctly. (this I meant also in my comment above).

Could you list what kind of files are changing with each run? Maybe you have them in some commit publicly available?

[jonsgreene]

@Pilskalns This is not a public repo unfortunately. I have noticed that if I delete the browsers cache the navigation section will update and start to function. @divinerites also mentioned that it could be cache. Still haven't been able to figure out why git sees changes after running hugo after a fresh push. I'll keep testing, thanks for the help.

[jonsgreene]

So today I ran a few more test. I noticed that the while using the submodule it would only update to this sha b667496

I updated hugo to v0.52/extended
I then ran git submodule update --remote to be on your latest commit

It seems to have fixed the issue with the navigation problem. I do however notice that the changes when running hugo after a good commit changes this meta data on each page

-<meta name="revised" content="2018-12-05T12:15:11 EST">
+<meta name="revised" content="2018-12-05T12:17:20 EST">

This isn't a big deal. I'm going to keep poking around to see if the issue was resolved by recent updates.

[Pilskalns]

@jonsgreene great find!

Yes, revised tag was added around month ago. It is just the build time of the site.

If you need to completely the same output between two builds, you can add your custom head.html and remove that line.