In a recent amr-users-plus update, a variety of new formatting options were added. This was prompted by a request to handle buddypress uploaded files, like resumes or images that are stored with a relative url.. In responding to this, the ability to choose a variety of formats for urls, telephone numbers, emails etc was added to amr-users-plus. See the buddypress user directory demo site for some examples. The wordpress dashicons font is used, enabling the icons to take on the colours of your theme. In addition, since it is possible for you to change the icons used as they are delivered using css.
As always I am happy to entertain requests for such features. I try to deliver them in ways that offer generic consistent use. Further updates are on the way to refresh other add-ons in line with a big refresh of the main amr-users plugin.
The amr-users and amr-users-plus* suite of programs enable websites to list their user data from the wordpress user database and related tables (eg CIMY user tables). See the individual addon plugin descriptions to see the tables they access. The plugins do not add or store any other personal user data – they are aimed at simplifying the development of lists or reports of user data.
The design of the user data and the decision to display the data in a user list generated by the plugins is the website’s responsibility. The base plugin currently caches user lists to simplify querying the website user data for the designed user list. The cache content is determined by the website – it is the user list content. These caches are temporary. They are stored in the wordpress database and are subject to the same protections as other website data in that websites wordpress database. If a user record is updated or deleted, the next cache run will delete all existing user data for that list and create a new cache.
Privacy and consent to the display of any personal data in a user list is the website’s responsibility. The base plugin offers a setting to determine whether a user list is can be shown publicly or not. The website is responsible for determining what goes into any such user list and whether these lists are made publicly available or simply run in admin by an appropriately authorised person.
The plugin offers the feature of a csv extract of a user list. If a list is public, the csv extract is stored as a file on the websites server. Security and safety of this file is the website’s responsibility. If the list is not public, the csv extract can be generated real time by a user who has the appropriate security capability.
When the plugin is deleted, the cache tables and plugin options are also deleted.
Many of the add-on plugins merely format the user data or offer searching, filtering and navigation features unrelated to the capture or tracking of the data. In some cases they are merely example plugins and it is the website’s responsibility as to how these plugins are modified and what they data they might then make it possible to store.
The above applies to the following user related plugins:
Changing the text in a plugin or theme without editing the plugin or theme files is surprisingly easy IF the plugin or theme has made the text translateable.
Using a plugin like https://wordpress.org/plugins/loco-translate/, ensure the language chosen matches your wordpress language, and choose a location for your files (loco translate helps) that
will be accessed by the plugin or theme (some help with this) and
will not be overwritten by updates – loco translates helps and some plugins/themes help too by offering another lookup location. The recommended custom language file location is /wp-content/languages/.
The amr-user plugin offers wordpress capability control of access to users lists. In wordpress roles have capabilities, and the capabilities determine what the users can do. User lists can also be tagged as ‘public’ so that a viewer with no role can see the list if used on the front end.
Summary of access control options:
public lists (ie lists ticked ‘public’ in the settings) can be viewed by anyone
non-public lists can only be viewed by people with ‘list_users’ capability
‘manage_options‘ or ‘manage_userlists‘ (custom capability) can create and edit user lists.
Tailoring access to the lists for roles:
If you want to isolate the ‘manage_userlists’ capability to a non-administrator and you don’t already have a plugin to do that for you, something like Justin Tadlock’s Members plugin is useful.