TOC not displaying in starter

[Hrovatin]

Checklist

• I have read and accepted the contributing guidelines.

How did you create the site?

Generated from chirpy-starter

Description

I am building my page locally and TOC is not shown.

Is this expected and does it mean that it will show up once page is published on github? - Since I did not manage to run npm due to missing files in starter.

Operations you have already tried

• Updated to 7.2.1
• Unsuccessfully tried to run npm, but seems to be not intended on starter as per https://github.com/cotes2020/jekyll-theme-chirpy/wiki/Upgrade-Guide#upgrade-the-fork

Anything else?

No response

[SoumyaK4]

@Hrovatin have you tried clearing all jekyll cache before rebuilding?

[kungfux]

does it mean that it will show up once page is published on github?

TOC should work on local build.

I would suggest to check _config.yml to make sure TOC is enabled globally which is by default but still.

# boolean type, the global switch for TOC in posts.
toc: true

defaults:
  - scope:
      path: "" # An empty string here means all files in the project
      type: posts
    values:
      layout: post
      comments: true # Enable comments in posts.
      toc: true # Display TOC column in posts.

Then, make sure you have no errors in browser console when you open the post.

[Hrovatin]

Hi,

Tyank you very much for the quick response. I checked that toc is set to true in both cases in _config.yml and I also tried to set it true within individual posts.

I attempted to re-build which should have cleared the cache if I am not mistaken.

bundle exec jekyll b                 
logger was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.5.0.
You can add logger to your Gemfile or gemspec to silence this warning.
csv was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.4.0.
You can add csv to your Gemfile or gemspec to silence this warning.
/Users/karin.hrovatin/.gem/ruby/3.3.5/gems/safe_yaml-1.0.5/lib/safe_yaml/load.rb:22: warning: base64 was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.4.0.
You can add base64 to your Gemfile or gemspec to silence this warning.
Configuration file: /Users/karin.hrovatin/Documents/GitHub/website/Hrovatin.github.io/_config.yml
            Source: /Users/karin.hrovatin/Documents/GitHub/website/Hrovatin.github.io
       Destination: /Users/karin.hrovatin/Documents/GitHub/website/Hrovatin.github.io/_site
 Incremental build: disabled. Enable with --incremental
      Generating... 
                    done in 0.363 seconds.
 Auto-regeneration: disabled. Use --watch to enable.

There are no errors in my terminal or browser console.

bundle exec jekyll serve --livereload
logger was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.5.0.
You can add logger to your Gemfile or gemspec to silence this warning.
csv was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.4.0.
You can add csv to your Gemfile or gemspec to silence this warning.
/Users/karin.hrovatin/.gem/ruby/3.3.5/gems/safe_yaml-1.0.5/lib/safe_yaml/load.rb:22: warning: base64 was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.4.0.
You can add base64 to your Gemfile or gemspec to silence this warning.
Configuration file: /Users/karin.hrovatin/Documents/GitHub/website/Hrovatin.github.io/_config.yml
            Source: /Users/karin.hrovatin/Documents/GitHub/website/Hrovatin.github.io
       Destination: /Users/karin.hrovatin/Documents/GitHub/website/Hrovatin.github.io/_site
 Incremental build: disabled. Enable with --incremental
      Generating... 
                    done in 0.328 seconds.

[cotes2020]

... Since I did not manage to run npm due to missing files in starter.

If you are using the Starter, the upgrade method should be as described in the Upgrading from Starter. And you don't need to run npm.

Based on the limited information you’ve provided, you may consider providing the repo URL to help the community assist you better.

[Hrovatin]

If you are using the Starter, the upgrade method should be as described in the Upgrading from Starter. And you don't need to run npm.

Yes, I used that upgrade tutorial but since that did not help I tried the npm command as well as I have seen another thread suggesting that.

The blog is not yet public, but I made the repository public now. You can see an example post on test branch.

[Hrovatin]

I found out that this occurs only on Firefox but not Chrome.

[cotes2020]

The blog is not yet public, ...

When you want to protect your privacy, you can consider temporarily creating a copy of the repository, then delete sensitive data and reset all git commit history before providing it to the community for troubleshooting.

Back to the topic, from your repository, the post can correctly generate the TOC in Chrome/Firefox. So I think you might be interfered by the local browser cache. Try accessing the webpage in the browser's incognito mode.

If you still have the same issue, please provide the specific operating system, browser type, and version number. Thank you.

[Hrovatin]

Thank you, it seems it was only the cache