-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Dashboard broken after recent upgrade #15063
Comments
Did you actually do the thing the debugbar is telling you to do though? |
Also, if you're seeing PHP in the dashboard, this is not a Snipe-IT level issue, this is the web server not knowing to parse PHP pages as PHP, which is always a web server configuration problem. Please check your Windows server configs and make sure PHP is running properly. |
Yes, but it did not help. |
That you can access other urls within the system is a bit unusual - feels like maybe somebody on your end added a rule that prevents your Apache from parsing the dashboard as PHP. The demo runs off of master, and it clearly works, so I'd bet there's some weird rule within your apache configs that is overriding the PHP directives. |
I have no idea what really was the cause. Upon removing dashboard.blade.php and running upgrade.php, everything has returned back to normal. Thanks for the assistance. |
Debug mode
Describe the bug
After the most recent upgrade, our dashboard has started to look like a website made in the 2000's:
The upgrade was succesfully completed without error. we can still access other pages by using different URLS and these all look normal (we can even see by the version number that the upgrade was succesful). Debug mode still seems to work:
Any tips would be much appreciated.
Reproduction steps
Ruin the dashboard by upgrading?
Expected behavior
The dashboard should load with it's graphical elements.
Screenshots
No response
Snipe-IT Version
7.0.8
Operating System
Debian 12
Web Server
Apache2
PHP Version
8.3.9
Operating System
Windows 10
Browser
Chrome and Edge
Version
Chrome: 126.0.6478.127 and Edge: 126.0.2592.87
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: