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

403 error page upon deleting a resource #6069

Closed
ekmillard opened this issue Nov 28, 2023 · 6 comments
Closed

403 error page upon deleting a resource #6069

ekmillard opened this issue Nov 28, 2023 · 6 comments
Labels
needs more info More information is required

Comments

@ekmillard
Copy link

Description:

I just put our companies Laravel nova project on a new server, and I have never had an issue like this, but when I try and delete a resource it throws a 403 error page. I can create and edit just fine. It seems to be just deleting.

Detailed steps to reproduce the issue on a fresh Nova installation:

Create a resource, and attempt to delete the resource.
image
image
image

@crynobone
Copy link
Member

Unable to reproduce the issue, please provide full reproducing repository based on fresh installation as suggested in the bug report template (or you can refer to https://github.com/nova-issues for example)

@crynobone crynobone added the needs more info More information is required label Nov 28, 2023
@ekmillard
Copy link
Author

ekmillard commented Nov 28, 2023

@crynobone
Here is the what is happening, this is a brand new set up.

image
image

@ekmillard
Copy link
Author

Is there any specific apache configurations that need to be enabled/disabled for nova to delete a resource?

@ekmillard
Copy link
Author

ekmillard commented Nov 28, 2023

image

Here is the policy I have set for the resource.

@crynobone
Copy link
Member

Unable to reproduce the issue, please provide full reproducing repository based on fresh installation as suggested in the bug report template (or you can refer to https://github.com/nova-issues for example)

@crynobone
Copy link
Member

Hi there, this issue has been marked as fixed and done based on above description, reproducing code and test done on our side. If you still have a problem please create a New Issue with full description on how to reproduce the issue based on your use case.

@crynobone crynobone closed this as not planned Won't fix, can't repro, duplicate, stale Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs more info More information is required
Projects
None yet
Development

No branches or pull requests

2 participants