In the previous post, I discussed the importance of Actor information in xAPI statements. In this post I will describe how I have implemented this for the xAPI LearnPress Project.
Most companies have ways to set up SSO and security protocols for sites. However, if you are creating a project on your own with little technical knowledge, this may be beyond your scope. At this point in my project, it is beyond mine. But there are tools to collect user information in WordPress.
Any Membership plug-in will probably work to collect this information.
Some plug-ins allowed the login gate to be set at the post rather than on your WordPress site. I decided to use WP-Members. This offered 2 benefits.
- The dreaded pain of a login screen will not derail people from accessing my site, you will still be able to view my posts without having to remember ANOTHER password!
- It gives me ultimate control over which portions of the post get a login screen.
How I set it up:
- There is a nice quick set-up guide on the site for installation.
- Since I only wanted to use the login for my xAPI content, I changed the default post restriction, to not blocked.
- When I create a post, I can choose to add the login with a simple check.
- Then I use wp-members login in tags to create the ‘blocked content’. The user won’t see it until they login.
- I chose to embed the H5P created content to be the only thing that was invisible until you login.
If you would like to test the set-up, visit my initial H5P post; All Content Types are Not Created Equally