mirror of
https://github.com/go-shiori/shiori.git
synced 2026-04-25 22:45:55 +03:00
[GH-ISSUE #962] Wrong application path for asset/eventBus.js #424
Labels
No labels
component:backend
component:builds
component:builds
component:extension
component:frontend
component:readability
database
database:mysql
database:postgres
database:sqlite
feature:ebooks
github_actions
good first issue
hacktoberfest
note:duplicate?
note:fixed?
note:out-of-scope?
os:windows
priority:high
priority:low
pull-request
resolution:as-intended
resolution:cant-reproduce
resolution:duplicate
resolution:fixed
resolution:wontfix
tag:TBD
tag:big-task
tag:help-wanted
tag:huge-data
tag:meta
tag:more-info
tag:next
tag:no-stale
tag:requires-migrations
tag:research
tag:security 🛡️
tag:stale
tag:waiting-for-assignee
type:bug
type:documentation
type:enhancement
type:meta
type:ux
user:cli
user:web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shiori#424
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nakal on GitHub (Aug 10, 2024).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/962
Data
Describe the bug / actual behavior
Shiori server is running with Nginx in the subpath
/shiori. Most assets are loaded properly excepteventBus.js. The relevant piece shows that the asset url might be wrong:In the last import you can see "../".
Expected behavior
The asset should probably be loaded from the correct webroot.
To Reproduce
Steps to reproduce the behavior:
@isamert commented on GitHub (Aug 17, 2024):
I am also experiencing this, as a workaround I use the following in my nginx configuration for shiori:
@Monirzadeh commented on GitHub (Aug 17, 2024):
@fmartingr do I miss something in #916?
@fmartingr commented on GitHub (Aug 27, 2024):
I think this is the issue: #971