WordPress plugin intelligence profile

Read and Understood

V2.3 Better sanitization of arguments coming in from POST and written to DB Better job using nonce. Uses relative address for plugin_url …

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 4.9
Current version2.4
WordPress coverageTested up to WordPress 4.9
Minimum stackWP 3.0 · PHP —
Directory statusactive
Last directory update11 Apr 20188y ago
Active installations30Adoption metric — not a quality score
WordPress.org rating4.3 / 5 from 6 ratings
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Read and Understood version 2.4 as active, updated 8y ago and tested up to WordPress 4.9.

Overview

About this plugin

Read-and-Understood is a solution to the “I didn’t get the memo” problem.

The Read and Understood (RnU) WordPress plugin offers readers the opportunity to record an acknowledgment that they have read a specific posting.

com

One common use of RnU is by employers to record that employees have read postings in a specific, private category such as ‘internal’ which may only be seen by authorized, logged-in users. By doing so, the employee may assume responsibility for understanding the content and following any instructions, procedures, or policies contained in it.

These acknowledgments may then be accessed by administrators via a CSV file containing records created in a given date range. The records are exported using an Export button on the plugin’s setting page. In addition to exportation, the records are accessible through any technique used to access a typical MySql database such as PHPadmin, linked ables, or custom programming.

The acknowledgments may also be purged (deleted) using the PURGE button also found on the plugin’s setting page.

Optionally, the plugin may be configured to accept acknowledgments from users who are not logged-in. In that case, the user may enter any username desired provided that it meets an administrator specified format as defined by a regular expression. The default format for such usernames, if allowed, is 1-10 capital letters.

An Export file is a comma-separated value (CSV) text file which is generated from the administrative Settings Page.

There is header column that contains the post_title of any acknowledgments found within the specified date range.

Each row contains the RNU_USERNAME which may represent:

1) The WP username of the logged in reader who made one or more acknowledgments 2) If so configured, the username entered by a person who is NOT logged in 3) If "all Users" is checked to export, the WP username with no acknowledgments

Each row contains the RNU_USER_ID which may represent:

1) The user_id of the logged-in user who acknowledged the posting(s). he ALL USERS option was selected)

Each row may contain an email address which corresponds to the non-zero RNU_USER_ID, regardless of whether any acknowledgments were made.

Also in each row, there may be a date/time in a cell in a column headed by a post_title. That date/time corresponds to when the user (row) acknowledged that post (column).

Note that username may NOT necessarily correspond to a unique user and may be repeated. In fact, if so configured, a person who is not logged in may enter the username of any person.

For this reason, the User_id is also given in each row; which, if zero, means that the acknowledgment was made by a person not logged in who entered that username.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • accountability
  • acknowledgement
  • acknowledgment
  • acknowlegement
  • mantos
Compatibility & maintenance

Compatibility & maintenance

Tested up to WordPress 4.9

Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 4.9.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to4.9
Minimum requirementsWordPress 3.0 · PHP not listed
Update activity11 Apr 20188y ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.