Skip to content
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.

Sign up for GitHub

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

Jump to bottom

404 error with latest Wordpress and H5P: "Unable to save result data" #9

Open
Sire opened this issue Nov 15, 2017 · 1 comment
Open

404 error with latest Wordpress and H5P: "Unable to save result data" #9

Sire opened this issue Nov 15, 2017 · 1 comment

Comments

@Sire
Copy link

Sire commented Nov 15, 2017

Wordpress v4.8.2
H5P v1.9.4

I'm using wp-h5p-xapi logging towards wp-xapi-lrs (which I see you also built).
Settings are correct, I've verified by surfing to the endpoint with correct user/pw.

Any activity causes the following alert box:

Unable to save result data.
WP_H4P_XAPI_STATEMENT_URL=http://site.com/wp-content/plugins/wp-h5p-xapi/process-xapi-statement.php
WP_H5P_XAPI_CONTEXTACTIVITY=null

Diving into wp-h5p-xapi.js, the ajax post to process-xapi-statement.php fails with the following response:

code: 404
message: "<!DOCTYPE html>.... almost entire html"
textStatus: "success"

So the 404 indicates a nonexisting page, but surfing to process-xapi-statement.php works fine.
Also textStatus success seems strange.

Any ideas? I know the plugins haven't been updated in a while, so it's likely a problem with newer versions of Wordpress or H5P.
@Sire Sire changed the title 302 error with latest Wordpress and H5P 404 error with latest Wordpress and H5P: Unable to save result data Nov 15, 2017
@Sire Sire changed the title 404 error with latest Wordpress and H5P: Unable to save result data 404 error with latest Wordpress and H5P: "Unable to save result data" Nov 15, 2017
@limikael
Copy link
Contributor

Hm... Well...

So it would seem that the failure is somewhere inside process-xapi-statement.php ... Because as you say, the page exists but fails... And there shouldn't be a complete html page inside the message field, it should just be a short message... So the way to debug it would be to trace the source of that html and see where it is generated and why...

I think this is doable and I think it would be possible to solve the problem...

However... At this moment I'm a bit tied up with other things and fixing issues here are not in line with my personal interest to the point where I would chip in work "just to be nice" if you see what I mean?

Would you be willing to put this issue on e.g. Bountysource and chip in a little bit of a contribution? If so it will be easier for me to motivate to myself personally to fix it... And... I hop I don't come across as greedy by saying this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Sire @limikael