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

Empty knowledge pages #6415

Closed
frapuks opened this issue Mar 22, 2024 · 1 comment · Fixed by #6419
Closed

Empty knowledge pages #6415

frapuks opened this issue Mar 22, 2024 · 1 comment · Fixed by #6419
Assignees
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@frapuks
Copy link
Member

frapuks commented Mar 22, 2024

Description

4 pages are empty (you can try on testing) :

In Root files, this routes dosn't exist.

Expected Output

2 ways :

  • remove buttons on right bar if it's an error
  • implement routes if we want to make it accessible

Actual Output

  • empty pages
@frapuks frapuks added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 22, 2024
@frapuks frapuks self-assigned this Mar 22, 2024
@SamuelHassine SamuelHassine added critical use to identify critical bug to fix ASAP and removed needs triage use to identify issue needing triage from Filigran Product team labels Mar 22, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.8 milestone Mar 22, 2024
@nino-filigran
Copy link

nino-filigran commented Mar 22, 2024

@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants