• Resolved lwbaqueros

    (@lwbaqueros)


    Moin Oliver,

    The plugin is not capturing any xAPI statement. I have an error message from the Javascript console: admin-ajax.php 500 (Internal Server Error). It seems this problem is due to my one of the WP configuration file: admin-ajax.php, according to this.

    I record a video if you need a little more information about it, in here

    Can you confirm if that error is not related with the Plugin?

    MFG

    Luis

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author otacke

    (@otacke)

    @lwbaqueros
    Unfortunately, a 500 can have tons of reasons and is just a general message – kind of the server saying “Something went south (but I don’t know what and where).” Typically, admins would check the server logs (e.g. the PHP log) for more details and potentially increase the log level. You can in fact look at and modify all the plugin files and the database tables from the WordPress backend, but that won’t really help or be feasible without access to the log files.

    The problem seems to be triggered by the plugin, yes, but it’s hard to say what on the server is failing. It could be related to the execution time (if it is set very low and/or the server is very slow) or the memory available as you point out, but it could also be something completely different. It could even be a different plugin interfering. Have you already tried to deactivate those? Sorry, I don’t think I can help here.

    Thread Starter lwbaqueros

    (@lwbaqueros)

    Hi, So far, I have tried many things, including disabling all the plugins, changing the PHP memory limit, execution time, and theme. I will request access to the PHP server logs to look for further clues.

    Plugin Author otacke

    (@otacke)

    @lwbaqueros Have you been able to access to the PHP error logs? I don’t think your problem is related to the one I just resolved, but it was PHP related – so maybe updating to the latest version that I just released will fix your issue.

    Thread Starter lwbaqueros

    (@lwbaqueros)

    @otacke I confirm the last version has solved this issue. I did not read the server logs. Thanks for solving that bug.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘500 (Internal Server Error)’ is closed to new replies.