You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Ajax-Endpoint is the endpoint that the Editor uses to load and save data from the server. Instead of providing different endpoints the H5P-Team used one endpoint which can be configured via the ajaxPath-field in the Editor-Integration-Object
I hope this makes it a little bit clearer and helps you understand how the H5P-Editor works. There might be other mechanisms that I am not aware of, so please feel free to contribute and share your knowledge about the H5P-Structure.
The text was updated successfully, but these errors were encountered:
The Ajax-Endpoint is the endpoint that the Editor uses to load and save data from the server. Instead of providing different endpoints the H5P-Team used one endpoint which can be configured via the
ajaxPath
-field in the Editor-Integration-ObjectAs far as my research goes, it works like this:
GET or POST /ajaxPath?action=
1. Get Content-Type-Cache
See #5
Method:
GET /ajaxPath?action=content-type-cache
Response:
Example
2. Get Libraries
See #6
Method:
GET /ajaxPath?action=libraries?machineName=<machine_name>&majorVersion=<major_version>&minorVersion=<minor_version>
Response:
3. Post Libraries
See #7
Method:
POST /ajaxPath?action=libraries
Body:
Example:
["H5P.AdvancedText 1.1", "H5P.AppearIn 1.0"]
Response:
4. Post files
See #8
Method:
POST /ajaxPath?action=files
Body: file
Response:
I hope this makes it a little bit clearer and helps you understand how the H5P-Editor works. There might be other mechanisms that I am not aware of, so please feel free to contribute and share your knowledge about the H5P-Structure.
The text was updated successfully, but these errors were encountered: