-
-
Notifications
You must be signed in to change notification settings - Fork 757
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
Dashboard Items Not Clickable Despite Sidebar Navigation Functionality #1003
Comments
@palisadoes , Please assign me this issue. |
@rishav-jha-mech is working on completing the Admin redesign by the end of the month. Your input will be helpful in creating issues after that in accordance with our design guide that will soon be published. At that time we'll create smaller issues that will encourage greater participation. |
@palisadoes |
@rishav-jha-mech Should we proceed with this? |
@palisadoes, it's an feature request and it is doable so i think we can go ahead with this. |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
Issue Description:
There are several items shown in the dashboard like members admins posts events etc. These items are not clickable and do not redirects to respective pages like the sidebar.
Issues Identified:
Non-Clickable Dashboard Items:
The dashboard items (e.g., "Posts," "Members," "Admins") are not responsive to clicks, rendering them non-functional. Users are unable to access the associated content directly from the dashboard.
Expected Behavior:
Clicking on a dashboard item should lead to the relevant section or content within the dashboard.
Steps to Reproduce:
Navigate to the dashboard.
Observe that the dashboard items (e.g., "Posts," "Members," "Admins") are not clickable.
Attempt to click on any dashboard item to access its corresponding content.
The dashboard items should be functional like the sidebar items.
The text was updated successfully, but these errors were encountered: