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.

Sign up for GitHub

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

Jump to bottom

No catalogue display for several pages #1765

Closed
Icarus9913 opened this issue Apr 24, 2024 · 5 comments
Closed

No catalogue display for several pages #1765

Icarus9913 opened this issue Apr 24, 2024 · 5 comments
Labels
kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it triage/not-reproducible Couldn't reproduce this issue. If you add information remove this label and reopen the issue

Comments

@Icarus9913
Copy link
Contributor

What happened?

The normal case: there's a catalogue path when I open one page.
WeChat72a8f19c49c9f381106298eb36e993a8

But for some pages just like: no catalogue path
https://kuma.io/docs/2.7.x/reference/kuma-cp/
https://kuma.io/docs/2.7.x/policies/targetref/

WeChatc9983004d67aef4a8756f1ab23bd60b0
WeChatd1fcfe47d96752f3c0fc71139081c2d2
@Icarus9913 Icarus9913 added kind/bug A bug triage/pending This issue will be looked at on the next triage meeting labels Apr 24, 2024
@jakubdyszkiewicz jakubdyszkiewicz added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Apr 29, 2024
@lahabana
Copy link
Contributor

@lahabana to add context and pointers on where the issue is likely

@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jul 30, 2024
@lobkovilya lobkovilya removed the triage/stale Inactive for some time. It will be triaged again label Aug 5, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Nov 4, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Nov 4, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label Nov 12, 2024
@lahabana lahabana added the triage/not-reproducible Couldn't reproduce this issue. If you add information remove this label and reopen the issue label Nov 19, 2024
@lahabana
Copy link
Contributor

It works for me

@github-actions GitHub Actions
Copy link
Contributor

Automatically closing the issue due to having one of the "closed state label".

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it triage/not-reproducible Couldn't reproduce this issue. If you add information remove this label and reopen the issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@lahabana @jakubdyszkiewicz @lobkovilya @lukidzi @Icarus9913