-
Notifications
You must be signed in to change notification settings - Fork 304
-
Notifications
You must be signed in to change notification settings - Fork 304
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
Questions are not completelly loaded #5129
Comments
Perhaps found the solution for this issue. |
Interesting @PASTJL, and thanks for taking the time to write good feedback! To summarize from your solution: The French content pack is missing assessment items that are in the English? @aronasorman will soon be addressing issues with the content packs, so I'm assigning him for now, |
For your question, you are right, in fr.zip no "khan" folder. |
This is intentional - the built assets are too big to distribute with every language pack, so we include them in English which should be bundled by default with all full installers. |
Ok. |
Hrm - seems like something is going wrong with the correct placement of the english language pack during install then! @cpauya Can you check out if this is an issue with the Windows installer in particular? |
It sounds like a problem with how system-wide folders are assumed to be intermixed with user directories. If the English content packs are placed in a system-wide location, but the user installed content packs depend on them, the mere existence of a user folder will shadow out all static content items from the system-wide location as it was originally designed... I can check this tomorrow. |
Copy @rtibbles, we will help check this out today. |
I can't replicate this using
On IE11 Windows7.
I'll continue testing this tomorrow using build from dungeon. |
I don't have Win10, but retested this on fresh 0.16.5 version on Win8 (the next closest thing to Win10), and could not replicate with French contentpack installed locally: It could have, as @benjaoming noted, something to do with the user installing the local contentpack... |
@radinamatic 's suggestion sounds like something worth investigating! |
@benjaoming & @radinamatic I can also reproduce this issue with @djallado comment above. |
Just to be sure that I understood correctly the scenario where you managed to replicate this:
If this is a case, we may have to amend the docs and stress the requirement that contentpacks MUST be installed by the same user as the base installation. |
I am the original poster. On my desktop there is only a user with administrator profile.But you have found another issue! |
That's exactly what we did @radinamatic to replicate the issue. We will update the docs then. |
@djallado thanks! sounds like a documentation fix is the way to go. You could potentially mirror the system-wide installation location of the Debian installer, but it might not be easy to achieve on windows with all sorts of permission issues lurking. Here's a suggestion, please adjust :)
|
Closing this as we now have a warning about installing and using KA Lite on different user accounts, seems like the best solution at present. |
Summary
KA Lite on my desktop Windows 10. Questions are incompletely loaded, missing JPG images
Branch or installer method
Installed from the Windows executable KALiteSetup-0.16.5.exe
I ran succefully
kalite manage retrievecontentpack local fr fr.zip
Traceback or relevant snippet from server.log
server.log no error tracked
With mozilla Inspector i got 2 HTT404 as shown below
GET http://localhost:8008/content/assessment/khan/6e6/6e68574abb61d2b4a12644d777006fcfa8a73cff.png [HTTP/1.1 404 Not Found 3 ms]
GET http://localhost:8008/content/assessment/khan/f7e/f7ee2b71e450c5867e6721d1e1a2f2301eaa4f46.jpg [HTTP/1.1 404 Not Found 2 ms]
When looking in content/assessment/khan folder, it is empty, so the 404 http error
How i can retrieve these JPG files ?
How to reproduce
See the screen shots in joined pdf
It seems like the issue #5119
KALiteBug.pdf
The text was updated successfully, but these errors were encountered: