bug: Search functionality not working

[Rutwik187]

Describe the bug
When a user types a topic name in the search bar, relevant suggestions appear correctly. However, clicking on any of the suggested topics redirects the user to the home page instead of the corresponding course page.

To Reproduce
Steps to reproduce the behavior:

1. Navigate to the search bar on the home page or the /courses page.
2. Enter a topic name (e.g., WebRTC).
3. Click on one of the suggested topics.

Expected behavior
Clicking on a suggestion should open the corresponding course page related to the selected topic.

Actual Behavior
Instead of navigating to the course page, the user is redirected back to the home page.

Screenshots or GIFs

Info (please complete the following information):

• Browser chrome
• Version 132

[Rutwik187]

Search works on local environment but fails on deployed production environment 🤔
@devsargam any thoughts ?

[gcbibek3353]

@Rutwik187
It's not like working in local environment and not working in production environment..
The problem is :
It redirects to home page for some suggested topics
and redirects to the actual corse for some topics

100xdevs_issue.webm

[Pruthvik-P]

@gcbibek3353
it redirects you to the homepage only if you don't have access to the content
for eg. If you are a Cohort 2 student trying to search for a cohort 3 content. It shows you the content but does not give you the access to see it.

[Rutwik187]

Ohh. got the issue. thanks @Pruthvik-P .

I think improvement can be done where proper error message can be displayed that you do not have access to the content instead of just redirecting to home page.
Or we can have a check that only displays the topics that are accessible to the user. (but it will reduce the search speed 🤔)

[Pruthvik-P]

Ohh. got the issue. thanks @Pruthvik-P .

I think improvement can be done where proper error message can be displayed that you do not have access to the content instead of just redirecting to home page. Or we can have a check that only displays the topics that are accessible to the user. (but it will reduce the search speed 🤔)

No I think those should not be shown at all