otacke

<p>PLEASE NOTE: I gave some of my free time to create this plugin. Using it and its source code is absolutely free. I don’t want any money from you. However, if you like this plugin, I kindly ask you to make a one-time donation of 2.50 EUR to the Rainforest Coalition (https://www.rainforestcoalition.org/donate) — or more if you can afford to.</p>
<p>H5P is a versatile plugin to add interactive content to your website. You may try to run it inside some fields that are created by other plugins, e.g. inside tabs, accordions, lightboxes, etc. And with some of them it seems that H5P doesn’t work although it is, but the content is set to a height of 0 pixels. That problem is described at https://h5p.org/manipulating-h5p-with-javascript.</p>
<p>The best solution would be to modify the plugin that’s including tabs, etc. to your WordPress site, but that’s not always possible. In some cases, this plugin may be a feasible workaround at least.</p>
<p>In “observer” mode, it will try to add a so called ResizeObserver to the container that holds the iframe with H5P content. That observer will send a resize pulse whenever the container changes in size, e.g. when it becomes visible. This should be a safe option just taking some extra resources.</p>
<p>In “interval” mode, it will trigger H5P to resize in regular intervals which should let it be displayed in many cases. However, if they appear too frequent, they may cause the browser to stall. Choose the time interval wisely! Also, some H5P content types may break that way. The only way around this is then the “selector” mode.</p>
<p>In “selector” mode, you need to determine a CSS selector that will identify all the elements that you interact with to display other contents, e.g. the tab buttons. If that selector is set in the plugin’s settings, it will trigger a resize pulse when that element is clicked. This way, you prevent stalling the browser or breaking H5P content types. Depending on how the other plugin was created, there may not ba a suitable CSS selector then.</p>
<p>If necessary, you can use the <em>manage_h5presizepulse_options</em> capability to control access to the plugin settings.</p>
<p>PLEASE NOTE: H5P IS A REGISTERED TRADEMARK OF H5P GROUP. THIS PLUGIN WAS NEITHER CREATED BY H5P GROUP NOR IS IT ENDORSED BY THEM.</p>


SNORDIAN's H5P Resize Pulse

Provides you with a potential workaround for H5P content that won't show in tabs, accordions, lightboxes, etc.

<p>This WordPress plugin is a simple solution to catch ’em all, those xAPI statements that have been sent by H5P (https://h5p.org) content types. It allows you to store (the most relevant) xAPI properties in the database of WordPress. It also allows you to view, filter and export these data as a CSV file for further processing.</p>
<p>Please cmp. https://www.olivertacke.de/labs/2017/12/27/gotta-catch-em-all/ and https://www.olivertacke.de/labs/2018/03/25/collecting-and-analyzing-data-with-h5p-and-opening-up-education-maybe/ for the ideas behind the plugin.</p>
<p>This plugin is NOT intended to work as a replacement for a decent Learning Record Store. It will work well for smaller platforms, but if you are expecting to track many xAPI statements, you will probably run into trouble with displaying all the data at some point.</p>
<p>This plugin is NOT intended to forward xAPI statements sent by H5P to a Learning Record Store. Please use https://github.com/tunapanda/wp-h5p-xapi if you need that functionality.</p>
<p>This plugin is NOT intended to replace the H5P plugin’s reporting or provide functionality for analysis, etc. There is no point in recreating what is already available in Learning Record Stores or what you can do yourself with a spreadsheet software, scikit-learn, etc.</p>
<p>If you need more, you should give Learning Locker (https://learninglocker.net/) a shot. It’s open, free and shiny.</p>
<p>PLEASE NOTE: H5P IS A REGISTERED TRADEMARK OF JOUBEL. THIS PLUGIN WAS NEITHER CREATED BY JOUBEL NOR IS IT ENDORSED BY THEM.</p>
<h3>GDPR</h3>
<p>Please note that as of May 25, 2018 you may have to comply with the General Data Privacy Regulation (GDPR, http://gdpr-info.eu/).</p>
<p>H5PxAPIkatchu supports the functions that WordPress offers to</p>
<ul>
<li>use suggestion for your privacy statement text,</li>
<li>export personal data of a user, and</li>
<li>delete personal data of a user.</li>
</ul>
<p>Background: If you’re using H5PxAPIkachu, by processing the xAPI statements you’re processing at least these personal data items according to art. 4 GDPR:</p>
<ul>
<li>xAPI statement: Actor/name (Full name of the Agent)</li>
<li>xAPI statement:Actor/Inverse Functional Identifier (email address, openID or account data within the host system)</li>
<li>WordPress user id (ID given by the WordPress host system)</li>
</ul>
<p>Please make sure to account for these items in your GDPR processes and documentation.</p>
<h3>Customization</h3>
<h3>Capabilities</h3>
<p>Some capabilities can be set for WordPress user roles in order to specify who<br />
should be allowed to do what:</p>
<ul>
<li>manage_h5pxapikatchu_options: Capability to change the plugin’s options</li>
<li>view_h5pxapikatchu_results: Capability to view results of content types that have been created by current user and that were stored by H5PxAPIkachu</li>
<li>view_others_h5pxapikatchu_results: Capability to view results of all content types that were stored by H5PxAPIkachu</li>
<li>download_h5pxapikatchu_results: Capability to download the results stored by H5PxAPIkachu and accessible to current user</li>
<li>delete_h5pxapikatchu_results: Capability to delete ALL data stored by H5PxAPIkachu</li>
</ul>
<h3>Hooks and filters</h3>
<p>H5PxAPIkachu provides some hooks and filters that developers can use to customize the behavior or to use H5PxAPIkachu as the basis of their own plugin.</p>
<h3>Actions</h3>
<ul>
<li>h5pxapikatchu_on_activation: Triggered on activation of H5PxAPIkachu</li>
<li>h5pxapikatchu_on_deactivation: Triggered on deactivation of H5PxAPIkachu</li>
<li>h5pxapikatchu_on_uninstall: Triggered on uninstall of H5PxAPIkachu</li>
<li>h5pxapikatchu_insert_data: Triggered when data are supposed to be inserted into the database</li>
<li>h5pxapikatchu_insert_data_pre_database: Triggered right before data will be inserted into the database</li>
<li>h5pxapikatchu_insert_data_post_database: Triggered right after data was inserted into the database, contains the new row’s id that was inserted to the main table</li>
<li>h5pxapikatchu_delete_data: Triggered when data are supposed to be deleted from the database</li>
</ul>
<h3>Filters</h3>
<ul>
<li>h5pxapikatchu_insert_data_actor: Allows to filter/retrieve the xAPI actor object when it is supposed to be inserted into the database</li>
<li>h5pxapikatchu_insert_data_verb: Allows to filter/retrieve the xAPI verb object when it is supposed to be inserted into the database</li>
<li>h5pxapikatchu_insert_data_object: Allows to filter/retrieve the xAPI object object when it is supposed to be inserted into the database</li>
<li>h5pxapikatchu_insert_data_result: Allows to filter/retrieve the xAPI result object when it is supposed to be inserted into the database</li>
<li>h5pxapikatchu_insert_data_xapi: Allows to filter/retrieve the complete xAPI statement string when it is supposed to be inserted into the database</li>
</ul>


SNORDIAN's H5PxAPIkatchu

Simple solution to catch 'em all, those xAPI statements that have been sent by H5P content types.

SNORDIAN's H5P Resize Pulse vs SNORDIAN's H5PxAPIkatchu