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

LifterLMS Navigation Link Block doesn't work properly when the default link is used #2465

Closed
4 tasks done
eri-trabiccolo opened this issue Jun 20, 2023 · 0 comments · Fixed by #2471
Closed
4 tasks done
Assignees
Labels
Severity: Normal Status: Has Alternative A workaround or alternative solution is available Status: Has PR This issue has an open pull request Type: Bug Bugs and errors

Comments

@eri-trabiccolo
Copy link
Collaborator

Reproduction Steps

  • using the Site Editor add a LifterLMS Link block to the menu
  • Do not modify the link selection: the Dashboard should be selected by default
  • Save and check the front-end

Expected Behavior

  • I would expect to see the Dashboard menu item

Actual Behavior

  • No Dashboard menu item

I think we can safely consider the attributes 'label' = 'Dashboard' and 'page' = 'dashboard' when they're not set (yet).
Workaround:
select any page, then select the Dashboard one and save.

Error Messages / Logs

[20-Jun-2023 06:58:33 UTC] PHP Warning:  Undefined array key "page" in /Users/rock/Dev/plugins/lifterlms/includes/class.llms.nav.menus.php on line 383

System and Environment Information

LifterLMS 7.2.1

This issue has be recreated:

  • Locally
  • On a staging site
  • On a production website
  • With only LifterLMS and a default theme

Browser, Device, and Operating System Information

n/a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Severity: Normal Status: Has Alternative A workaround or alternative solution is available Status: Has PR This issue has an open pull request Type: Bug Bugs and errors
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants