IndiEgg Studios

<p><strong>Nest Frontend Editor for H5P</strong> lets your users view, create, and edit H5P content without ever leaving the front end of your WordPress site.</p>
<p>Place the shortcodes on any pages you choose, configure permissions per role, and let the plugin handle the rest. Works seamlessly with <strong>Remix Manager for H5P</strong> when its Library Link Behavior settings point to Nest front-end pages.</p>
<p><strong>Shortcodes:</strong></p>
<ul>
<li><code>[nest_h5p_editor_view]</code> – Displays an H5P content item. Reads the item ID from the URL (<code>?h5p_id=X</code>).</li>
<li><code>[nest_h5p_editor_create]</code> – Displays the H5P content creation editor.</li>
<li><code>[nest_h5p_editor_edit]</code> – Displays the H5P content editor for an existing item. Reads the item ID from the URL (<code>?h5p_id=X</code>). Users may only edit content they own.</li>
<li><code>[nest_h5p_editor_results]</code> – Displays the H5P results page for an existing item. Reads the item ID from the URL (<code>?h5p_id=X</code>).</li>
<li><code>[nest_h5p_editor_link_view]</code> – Outputs a link to the front-end view page for the current H5P item. Accepts <code>text</code> and <code>class</code> attributes.</li>
<li><code>[nest_h5p_editor_link_edit]</code> – Outputs a link to the front-end edit page for the current H5P item. Only renders if the current user owns the content. Accepts <code>text</code> and <code>class</code> attributes.</li>
<li><code>[nest_h5p_editor_link_results]</code> – Outputs a link to the front-end results page for the current H5P item. Accepts <code>text</code> and <code>class</code> attributes.</li>
</ul>
<p><strong>Features:</strong></p>
<ul>
<li>Role-based permissions – all roles registered on the site are listed, including custom roles like Teacher or Instructor.</li>
<li>Configurable unauthorized redirect behavior per action – redirect to home, login, or a custom URL.</li>
<li>Logged-out users are always redirected to the login page.</li>
<li>Auto-resizing iframes that adjust to content height on load, on user interaction, and after content type selection on the create page.</li>
<li>Admin menu, admin bar, and footer are automatically hidden inside the iframe so users see a clean, focused experience with no WordPress admin UI visible.</li>
<li>Ownership enforcement for the Edit shortcode – users can only edit H5P content they own.</li>
<li>Results shortcode – display H5P results on the front end with role-based permission control.</li>
<li>Link shortcodes – generate styled links between view, edit, and results pages for the current H5P item.</li>
<li>Filter hooks (<code>rmh5p_view_url</code>, <code>rmh5p_edit_url</code>, <code>rmh5p_create_url</code>, <code>rmh5p_results_url</code>) integrate with Remix Manager for H5P when its Library Link Behavior settings point to Nest front-end pages.</li>
</ul>
<p>For full documentation visit <a href="https://indiegg.com/nest-frontend-editor-for-h5p/documentation" rel="nofollow ugc">indiegg.com/nest-frontend-editor-for-h5p/documentation</a>.</p>
<p><strong>Disclaimer:</strong></p>
<p>Nest Frontend Editor for H5P is an independent plugin and is not affiliated with, endorsed by, or sponsored by H5P or its developer, Joubel. H5P is a trademark of its respective owner.</p>
<h3>Usage</h3>
<h4>Setting up pages</h4>
<p>Create one page per action. Add the shortcode to each:</p>
<ul>
<li>View page: <code>[nest_h5p_editor_view]</code></li>
<li>Create page: <code>[nest_h5p_editor_create]</code></li>
<li>Edit page: <code>[nest_h5p_editor_edit]</code></li>
<li>Results page: <code>[nest_h5p_editor_results]</code></li>
</ul>
<p>Then go to <strong>Settings -> Nest Frontend Editor for H5P</strong> and select each page from the dropdowns.</p>
<h4>Permissions</h4>
<p>Under <strong>Role Permissions</strong>, check which roles can access each action. All roles on the site are listed automatically, including custom roles.</p>
<h4>Redirect behavior</h4>
<p>Under <strong>Unauthorized Redirect Behavior</strong>, choose what happens when a logged-in user without permission tries to access each page. Options are:</p>
<ul>
<li>Redirect to home page</li>
<li>Redirect to login page</li>
<li>Redirect to a custom URL</li>
</ul>
<p>Logged-out users are always sent to the login page regardless of this setting.</p>
<h4>Integration with Remix Manager for H5P</h4>
<p>When both plugins are active and pages are configured, the Remix Manager Library Link Behavior settings can point View, Edit, and Results links to the matching Nest Frontend Editor for H5P pages.</p>
<h4>Link shortcodes</h4>
<p>Place these shortcodes on your view, edit, or results pages to generate navigation links between pages for the same H5P item. All three read the current <code>h5p_id</code> from the URL automatically.</p>
<ul>
<li><code>[nest_h5p_editor_link_view]</code> – link to the view page</li>
<li><code>[nest_h5p_editor_link_edit]</code> – link to the edit page (only renders if the current user owns the content)</li>
<li><code>[nest_h5p_editor_link_results]</code> – link to the results page</li>
</ul>
<p>All three accept optional attributes:</p>
<ul>
<li><code>text</code> – the link label. Example: <code>[nest_h5p_editor_link_view text="Watch this activity"]</code></li>
<li><code>class</code> – additional CSS classes. Example: <code>[nest_h5p_editor_link_edit class="button button-primary"]</code></li>
</ul>
<p>Each link always includes the classes <code>nfeh5p-link</code> and a type-specific class (<code>nfeh5p-link-view</code>, <code>nfeh5p-link-edit</code>, <code>nfeh5p-link-results</code>) for styling in your theme CSS.</p>


Nest Frontend Editor for H5P

Provides front-end view, create, edit, and results pages for H5P content via shortcodes, with role-based permissions.

otacke

<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.

Nest Frontend Editor for H5P vs SNORDIAN's H5PxAPIkatchu