learningequality / learningequality/studio
Path difference with Kolibri in URL for preview of HTML5 apps
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Observed behavior
There seems to be an inconsistency with how the Studio HTML5 preview and the Kolibri HTML5 renderer link to content:
- Studio preview iframe: https://studio.learningequality.org/zipcontent/f4eecb1b4cba466a32a5444e5a546052.zip/
- Kolibri viewer iframe: https://studio.learningequality.org/content/zipcontent/ae532016cf49ef02f4e1bdf50bd8a758.zip/index.html
So, for example, that means the Kamkalima audio dependencies, which reference ..\..\content\storage\[path], work on Studio, but not on Kolibri.
Expected behavior
Since we can't retroactively control what Kolibri does, since old versions are in the wild, probably best to match its behavior in Studio.
User-facing consequences
Cheffed channels with content dependencies (like Kamkalima) may appear to work when previewed on Studio, but then not work once imported into Kolibri.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing how Studio preview and the Kolibri HTML5 renderer construct their iframe URLs, using the example URLs in the issue and reproducing the Kamkalima dependency path. Done means Studio uses the same path behavior as Kolibri and HTML5 content dependencies resolve correctly after import.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100