Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong breadcrumbs order for nested navigation items #2143

Closed
Silthus opened this issue Jul 7, 2020 · 1 comment · Fixed by #2179
Closed

Wrong breadcrumbs order for nested navigation items #2143

Silthus opened this issue Jul 7, 2020 · 1 comment · Fixed by #2179

Comments

@Silthus
Copy link

Silthus commented Jul 7, 2020

Originally posted on rtd: readthedocs/readthedocs.org#7263

Details

Expected Result

The breadcrumbs on the top of the page should be ordered according to the navigation tree.
The breadcrumbs should show Docs >> Server Admins >> ART Syntax >> Requirements instead.

Actual Result

The breadcrumbs are switched when going beyond three levels deep into the navigation.

image

This is my config:

site_name: ART-Framework
site_description: 'Home of the documentation for the ART-Framework.'
site_author: 'Michael Reichenbach'
docs_dir: docs/
repo_url: 'https://github.com/art-framework/art-framework'
nav:
  - Home: index.md
  - 'Server Admins':
    - 'Quickstart': 'admin/quickstart.md'
    - 'Installation': 'admin/installation.md'
    - 'ART Syntax':
      - 'General Syntax': 'admin/syntax.md'
      - 'Actions': 'admin/actions.md'
      - 'Requirements': 'admin/requirements.md'
      - 'Trigger': 'admin/trigger.md'
  - 'Developers':
    - 'Quickstart': 'developer/quickstart.md'
    - 'Creating ART':
      - 'Actions': 'developer/actions.md'
      - 'Requirements': 'developer/requirements.md'
      - 'Trigger': 'developer/trigger.md'
  - 'Issue Tracker': 'https://github.com/art-framework/art-framework/issues'
  - 'About': 'about.md'
theme:
  name: 'readthedocs'
jkozera added a commit to jkozera/mkdocs that referenced this issue Sep 3, 2020
@jkozera
Copy link
Contributor

jkozera commented Sep 3, 2020

Reversing the ancestors property before rendering seems to fix the issue for me - see the just-submitted PR #2179.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants