Fix translations.json fetch path for subfolder installations#54
Open
Fix translations.json fetch path for subfolder installations#54
Conversation
Agent-Logs-Url: https://github.com/FriendsOfREDAXO/vidstack/sessions/93f07086-a430-4d47-8f18-134557d34615 Co-authored-by: TobiasKrais <4131072+TobiasKrais@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix problem with subfolder installation errors
Fix translations.json fetch path for subfolder installations
May 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When REDAXO is installed in a subfolder, the hardcoded absolute path
/assets/addons/vidstack/translations.jsonresolves against the server root rather than the installation base, producing a 404.Change
Derive the
translations.jsonURL dynamically fromdocument.currentScript.srcat script parse time, using the standardURLconstructor to resolve the sibling file correctly regardless of install path:This naturally handles
?buster=…query strings on the script URL and falls back to the previous absolute path ifcurrentScriptis unavailable.