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

Search plugin uses wrong endpoint path for redindexing #10245

Closed
cbratschi opened this issue Dec 30, 2024 · 2 comments · Fixed by #10258
Closed

Search plugin uses wrong endpoint path for redindexing #10245

cbratschi opened this issue Dec 30, 2024 · 2 comments · Fixed by #10258
Assignees

Comments

@cbratschi
Copy link

Describe the Bug

The fetch call here uses a hardcoded endpoint name:

https://github.com/payloadcms/payload/blob/main/packages/plugin-search/src/Search/ui/ReindexButton/index.client.tsx#L49

Which results in a call to:

http://localhost:3000/api/search/reindex?locale=de

But our defined endpoint is /cms/api. The search plugin should use the correct endpoint.

PS: the error handling swallowed the 404 error only available on the JavaScript console. Errors throws by fetch() should be displayed as toasts too.

Link to the code that reproduces this issue

https://github.com/cbratschi/payload

Reproduction Steps

Use a different API endpoint path than /api. Try reindexing and nothing happens.

Which area(s) are affected? (Select all that apply)

plugin: search

Environment Info

Binaries:
  Node: 22.12.0
  npm: 10.9.0
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  payload: 3.12.0
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:05:23 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6031
  Available memory (MB): 65536
  Available CPU cores: 16
Copy link
Contributor

github-actions bot commented Jan 1, 2025

This issue has been automatically locked.
Please open a new issue if this issue persists with any additional detail.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 1, 2025
@github-actions github-actions bot unlocked this conversation Jan 2, 2025
Copy link
Contributor

github-actions bot commented Jan 2, 2025

🚀 This is included in version v3.13.0

@github-actions github-actions bot locked and limited conversation to collaborators Jan 2, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants