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

upgrade from 1.14.5 to 1.15.0 not not loading javascript 404 #824

Closed
trefase opened this issue Jan 7, 2025 · 3 comments
Closed

upgrade from 1.14.5 to 1.15.0 not not loading javascript 404 #824

trefase opened this issue Jan 7, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@trefase
Copy link

trefase commented Jan 7, 2025

Bug Description:
After updating from version 1.14.5 to 1.15.0 on a Debian system, Part-DB no longer loads JavaScript resources, resulting in 404 errors for JavaScript files. The previous version, 1.14.5, functioned without issues. The upgrade was performed following the standard procedure outlined in the documentation.

Screenshots
If applicable, add screenshots to help explain your problem.
image
image

Server Side

  • Part-DB Version: [e.g. Part-DB 1.15.0]
  • PHP Version: [e.g. PHP 8.1.2-1ubuntu2.20 ]
  • Database Server [e.g. 10.6.18-MariaDB-0ubuntu0.22.04.1]

Cleared browser and server cache.
Verified configuration files and permissions.

There is no Information in the log files

@trefase trefase added the bug Something isn't working label Jan 7, 2025
@jbtronics
Copy link
Member

Have you build the frontend assets? Do any error occurs during the yarn build process?
Have you cleared the Part-DB cache after the building of the frontend dependencies (so that Part-DB recognizes the new pathes)?

@jbtronics
Copy link
Member

Are you serving Part-DB under a prefix (e.g. something like /partdb)?
Then there was indeed a bug, which prevented the proper resolution of assets path then. This should be fixed with the latest commits.

@trefase
Copy link
Author

trefase commented Jan 7, 2025

I am indeed serving Part-DB under a prefix(via reverse proxy)

After pulling the latest commits it now works! Good work!

@trefase trefase closed this as completed Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants