TOPIC:

Hmmm... cannot attach PHP files.

Let's try a zip.

Hi Tom,

Thnx for the script file. Xerte is working over https now....
but xAPI is still not working!!
In Chrome Cconsole :
Access to XMLHttpRequest at 'https://www.[website]/xertetoolkits/xapi_proxy.php/statements' from origin 'https://[website]' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: Redirect is not allowed for a preflight request.

probably yet another problem with redirection??

Do you know the solution for this as well??

Thnx Joep

What version of xerte are you running?

And are the two websites different or the same in the (edited) error message above? And is the first one http?

It's probably still a http -> https issue.

Hi Tom,

Version is 3.7.12
The last message is gone now (my domain served pages without the www in front of the URL, whereas Xerte had the www.[website] format). Changed my website to only serve www. pages.

xAPI still not working though...

In workspace i can see the aph with usage of the LO (previously not visible, only the waiting icon loading16.gif) that's an improvement

In console while playing a LO: error in xapiwrapper:
GET https://www.[website]/xertetoolkits/modules/xerte/parent_templates/Nottingham/common_html5/logo.png 404

than a few lines about the LRS endpoint, username and password:
updating lrs object with new configuration xapiwrapper.min.js?version=X (git X-v3.7.12):2
endpoint : https://www.[website]/xertetoolkits/xapi_proxy.php/ xapiwrapper.min.js?version=X (git X-v3.7.12):2
user : xapiwrapper.min.js?version=X (git X-v3.7.12):2
password : xapiwrapper.min.js?version=X (git X-v3.7.12):2
strictCallbacks : true xapiwrapper.min.js?version=X (git X-v3.7.12):2
[1c33a706-df95-4ec3-8454-be79c6849892]: 200 -

Should the user name and password be empty?? In the LO-properties i filled in the correct LRS information, ....

Thnx Joep

This looks all OK. The logo cannot be found, if you do not put your own logo there.

And yes, here the username and password should be empty. So, how do you know that xAPI is not working?

xAPI is only working if you use the special link to play the LO.

Hi TOm,

OK, Settings are fine. Situation with your help has improved (https now working; the graph of LO history in workspace is back etc) , except for the sending of the statements to the LRS. As you stated, settings are fine this way, I'm sure LRS configuration is also OK. The problem is the LRS (ScormCloud) receives no statements, not from new LOs and not from old ones. LO's that worked fine last year, don't work anymore. My website hasn't changed, except from http to https
ScormCloud LRS Viewer only shows the statements that were send in January when I last edited my LO's... nothing newer...

I know I should use the xapi_lauch link....

I'm really confused about this problem....

Greetz Joep