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

"405 Method Not Allowed" error message shows when try to restore delete assets #11452

Closed
2 tasks done
YBVS opened this issue Jul 2, 2022 · 2 comments · Fixed by #11453
Closed
2 tasks done

"405 Method Not Allowed" error message shows when try to restore delete assets #11452

YBVS opened this issue Jul 2, 2022 · 2 comments · Fixed by #11453

Comments

@YBVS
Copy link

YBVS commented Jul 2, 2022

Debug mode

Describe the bug

Show follow info when try to restore deleted asssets (snipe-it version v6.0.6 build 8300 (gdf1e2687d), PHP Version8.0.20, this same problem even happens on the demo on snipe-it official site. https://demo.snipeitapp.com/hardware/1088/restore

Oops! An Error Occurred
The server returned a "405 Method Not Allowed".
Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.

Reproduction steps

  1. deleted a asset
  2. go to "report" >"Activity Report Search"
  3. Click to go into a deleted asset
  4. Click "Resotre" button
    ...

Expected behavior

It should be able to restore instead of showing a error message

Screenshots

image

Snipe-IT Version

v6.0.6 build 8300 (gdf1e2687d)

Operating System

Rocky Linux 8.6

Web Server

Apache

PHP Version

8.0.20

Operating System

Windows, Mac

Browser

Chrome, Safari, EDGE

Version

103.0.5060.66

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

Oops! An Error Occurred
The server returned a "405 Method Not Allowed".
Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.

Additional context

No response

@welcome
Copy link

welcome bot commented Jul 2, 2022

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

@YBVS
Copy link
Author

YBVS commented Jul 2, 2022

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant