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

Searching content with the search form requires login. #17276

Closed
gaojianzhuang opened this issue Dec 23, 2024 · 4 comments
Closed

Searching content with the search form requires login. #17276

gaojianzhuang opened this issue Dec 23, 2024 · 4 comments

Comments

@gaojianzhuang
Copy link

Describe the bug

  1. Enable the search related features and configured some setting for the search index.
  2. Enable the search form in the frontend layout.
  3. When the user is anonymous and input the search string then click the search button, the page will redirect the admin login page.
  4. When the user is logged, the search feature will works well

Orchard Core version

OrchardCore: 2.1.3

To Reproduce

  1. Enable the search related features and configured some setting for the search index.
  2. Enable the search form in the frontend layout.
  3. When the user is anonymous and input the search string then click the search button, the page will redirect the admin login page.
  4. When the user is logged, the search feature will works well

Expected behavior

The frontend search form should not need the user login.

Logs and screenshots

The frontend search form should not need the user login.

@Piedone
Copy link
Member

Piedone commented Dec 26, 2024

Please provide a screen recording of what exactly you do under steps 1 and 2, because it works fine for me on main: I tried the Blog recipe, ran the "Blog - Lucene Search" recipe, and searching on the frontend (e.g. https://localhost:44300/search?Terms=explore) works as an anonymous user.

@gwonen
Copy link

gwonen commented Dec 27, 2024

Note that the anonymous role needs to be given explicit permission to query any index.

Copy link
Contributor

It seems that this issue didn't really move for quite a while despite us asking the author for further feedback. Is this something you'd like to revisit any time soon or should we close? Please reply.

@github-actions github-actions bot added the stale label Jan 11, 2025
Copy link
Contributor

Closing this issue because it didn't receive further feedback from the author for very long. If you think this is still relevant, feel free to reopen it with the requested details.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants