You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately not much details in the stack trace:
The above error occurred in the <eval> component. It was handled by the <ReactDevOverlay> error boundary. Error Component Stack
at eval (index.js:3157:17)
at ReindexConfirmModal (index.js:14:3)
at div (<anonymous>)
at ReindexButtonClient (index.client.js:27:34)
Hey @cbratschi, I'll look into this one too. Strange as your error message seems to be about the reindex modal slug passed to the modal hook. I did not notice this error in 3.6.0, but maybe try latest in the meantime?
Just following up on this as promised! I can't reproduce this issue and haven't seen an instance of it since reindexing was introduced. As I mentioned above, the error you're seeing is related to the slug of the reindex modal so I'm thinking it might have something to do with the ui package modals. My recommendation would be to update to the latest or try reinstalling deps.
I tested against the monorepo using both mongodb and postgres. If you're still seeing this issue, then it'd be nice if I could see a valid repro or some more details about your environment.
Please can you share how you were able to run through the issue, and how you arrived at your solution. I am new to open-source contribution, and I found out about this issue on Tublian.
Can you please enlighten me in anyway, I am willing to learn.
Describe the Bug
Error while opening the search collection in the admin panel:
Happens while server-rendering this component.
Unfortunately not much details in the stack trace:
Link to the code that reproduces this issue
https://github.com/cbratschi/payload
Reproduction Steps
Use the search plugin. Open the search collection admin page. Error occurs while loading.
Which area(s) are affected? (Select all that apply)
plugin: search
Environment Info
The text was updated successfully, but these errors were encountered: