After using sections, the original article directory is messed up

[chuycy]

After using sections, my directory groups are mixed together, and the original Chinese title becomes an English title.

Q1 Add sections, some directory groups are invalid.
For example: the directory "我是一" has expired, and all the articles contained in it are displayed without grouping.

Q2 If my secondary directory is a folder, after adding sections, the Chinese title of the original secondary directory becomes the English title, and the order of the directories is also disrupted.

mkdocs.yml

Looking forward to your reply ! Thanks !

[squidfunk]

In order to look into this, I need you to provide a self-contained reproducible example without the awesome-pages-plugin and attach it here as a zip file. It might either be related to the plugin or to Material for MkDocs, which is the first thing we need to understand.

[squidfunk]

Again, this is not a minimal example. For comparison, this is your MkDocs config:

site_name: test-with-sections
docs_dir: "./docs/zh"
site_dir: "./site/zh"

theme:
  palette:
    primary: white
  name: material
  custom_dir: overrides/
  favicon: assets/images/favicon.ico
  logo: assets/images/logo.png
  language: zh
  features:
    - navigation.instant
    - navigation.sections
    - navigation.top
    - search.suggest
    - toc.follow
    - content.tabs.link

markdown_extensions:
  tables: {}
  footnotes: {}
  attr_list: {}
  md_in_html: {}
  toc:
      permalink: True
  meta: {}
  pymdownx.caret: {}
  pymdownx.mark: {}
  pymdownx.tilde: {}
  pymdownx.betterem: {}
  pymdownx.critic: {}
  pymdownx.keys: {}
  pymdownx.snippets: {}
  pymdownx.details: {}
  pymdownx.tabbed:
      alternate_style: true
  pymdownx.highlight:
      anchor_linenums: true
      auto_title: false
      linenums: false
  pymdownx.inlinehilite: {}
  pymdownx.superfences: {}
  pymdownx.emoji:
      emoji_index: !!python/name:materialx.emoji.twemoji
      emoji_generator: !!python/name:materialx.emoji.to_svg
      options:
        custom_icons:
          - overrides/.icons


  # 暂时不开放语言切换入口
  # alternate:
  #   - name: 中文
  #     link: /
  #     lang: zh
  #   - name: English
  #     link: /en/
  #     lang: en

plugins:
  awesome-pages: {}
  section-index: {}
  git-authors: {}
  git-revision-date-localized:
    type: custom
    custom_format: '%Y-%m-%d'
    enable_creation_date: true
    fallback_to_build_date: true
  search:
    separator: '[\s\u200b\-]'

extra_css:
  - assets/stylesheets/extra.css

I'm afraid with this big of an example, I'm unable to look into it. Please remove all plugins that are not native to Material for MkDocs, all pages that are not necessary, etc. Then, I'm happy to look into it. The reason is that the error can come from anywhere, and I suspect it has to do with the awesome pages plugin, but there's no way to be sure without a minimal example. Thank you.

[chuycy]

I'm so sorry.I have cleared unnecessary settings as you suggested.

This is the new mkdocs.yml I submitted this time.Do you see if it is ok?

Thanks a lot! : )

question of sections.zip

site_name: test-with-sections

theme:
  name: material
  language: zh
  features:
    - navigation.instant
    - navigation.sections

plugins:
  awesome-pages: {}
  section-index: {}

[chuycy]

Without the awesome-pages-plugin , navigation.sections seem to be invalid.
question of sections-without awesome pages.zip

site_name: test-with-sections

theme:
  name: material
  language: zh
  features:
    - navigation.instant
    - navigation.sections

plugins:
  section-index: {}

What I effect is:

But now, with navigation.sections and awesome-pages-plugin, it is:

But now, with navigation.sections and without awesome-pages-plugin, it is:(navigation.sections seem to be invalid)

[squidfunk]

Please remove all plugins and see if the issue persists. We cannot provide support for third party plugins. It might also be relted to the section-index plugin. Also, I'm so sorry but I can't read Chinese. Could you please use English to build an example? Spotting the differences in those characters makes my life super hard.

In short: the error must be reproducible with configuration that you can find on our documentation site. If it isn't, it's either related to some of your customizations, or to a third party plugin. In any case, we cannot offer support here.

[chuycy]

We used other alternatives, thank you very much!